-
Notifications
You must be signed in to change notification settings - Fork 23
Contributing to MUSCLE
Suggestions are welcome. Please check with me in advance to make sure that your idea is compatible with my idiosyncratic work habits and my plans for MUSCLE. If you'd like to contribute, please open an issue here on github or by all means send me an email -- you can find my contact info at https://drive5.com/about.html.
I am new to open-source collaboration. In the past, I've usually made source code publicly available as public domain or under an open-source license on my own web site where I've been solely responsible for documentation, new features, maintenance, bug fixes etc.
At the time of writing (late 2021) I'm trying to learn more about git, github, CI/CD, actions, workflows and so on; altogether there is surely a lot I don't know compared to developers who have been using these tools for a few years.
The area where I am most ignorant and could use the most help is ensuring that robust, validated updates to MUSCLE are delivered and distributed to the wider community via package repositories and tools such as Debian, Cygwin and so on.
Why am I telling you this stuff? Because the first release of MUSCLE v5 caused some problems (especially compiler errors) for people who wanted to re-build / re-package the software. Not good. Then, some of them posted pull requests with proposed fixes which conflicted with my ideas about how things should work. Even less good, frustration on both sides. In an attempt to address these issues, I'm working on updating build scripts to be more portable and writing wiki pages to explain the build design; see MUSCLE build design and Building MUSCLE