I've recently gotten started with Axoloti, and am playing around with my board and patcher at least occasionally giddy with excitement However, in the short time I've been able to use the system, I've noticed that there's a bit of rough edges here and there in the Patcher, f.e.
Trying to scratch my own itch, I went to have a look at the github repository. It's quite sizeable, and I wasn't able to orient myself particularly quickly.
Some Open Source projects (especially the larger ones) maintain something called a Contribution Guide, which usually contains informations for potential new developers regarding how to make code contributions, eg. which branches are used in the repository, formatting details, how to file issues etc. Another starting point is some documentation on how to get an environment set up for development, eg. git clone
, <run package manager>
, hack away, how to compile and use the changed code
. None of the above needs to be particularly verbose, just the minimum to get something set up or at least to point in the right direction.
Some questions off the top of my head:
- git branch usage, there's
master
, andexperimental
with more recent activity, and then a few more. Where am I supposed to find the latest code, make pull requests to etc? - what do I need to do to get a development environment set up? I haven't done desktop programming with native/java apps in years, mostly mobile, server & web, so I don't have an idea where to start. My immediate concern would be to fix some issues with the Patcher UI.
- code organisation, there's a
doc
folder, but half of the content is in html and the markdown files don't seem to be particularly up to date. - roadmap? I saw a topic on this, there's a markdown file in the
doc
which hasn't been touched in a while, but there's stuff happening in theexperimental
branch which is difficult to correlate with anything. Is it just people working on their own stuff or is there some kind of coordinated effort, or at least an idea of what currently is being worked on or anything that would be scheduled for future releases.
And there's bound to be more stuff that could be covered, f.e. just by looking around at other OS projects and seeing if the content seems relevant. If someone has happened to get set up lately, I think it would be a great opportunity to write down some notes and contribute to some initial documentation.
I realise that all of the above sounds like a "heavy" activity and something difficult to maintain, but that's not really my intent or experience. Getting invested in the Axoloti means that I'm also invested in an active community, and helping people who can and want to develop just creates a positive feedback loop IME.