For an Open Source project, you feel awfully closed. Okay, your svn repository is openly readable, as is the issue tracker (though I remember it took me some time to find it!), but if I'm interested in the project, so far the best I can do is fill out the volunteer form--and that feels too much like I'm committing to something I don't know I'll have the time for, or lasting interest in, and I really don't want to waste time of project members or get anyone's hope up.
What I would wish for is a more open access to the development procedure for casually interested people, like it is done in so many other Open Source projects. E.g.:
1.) Promote the Google project page (and other relevant stuff) better along with the volunteer form.
2.) Open up mailing lists (or whatever your means for communication are) for non-project members. If it turns out that this causes too much non-useful traffic or is a hindrance to your internal communication process, make those lists read-only, but have at least one list where anyone can post. This will enable outsiders to lurk around and learn, to see what's currently being worked on, where problems are, where work is needed most etc. And then, maybe, to gradually get involved.
3.) Make documentation openly readable. You say you'll train newbies, so there must be some documentation, right? It doesn't have to be perfect, or complete; just something is better than nothing at all. Since I couldn't find anything when I took an interest in the software and wanted to play around with it, I wrote some stuff down as I figured it out on my own, but it was a time-consuming process! If you are afraid that this will flood you with support requests by strangers--state that you don't give support for any of the documentation, and set up a mailing list (or whatever) where those people can help each other.
4.) State in which format you accept patches. Some people might not be interested in being a regular coder, but might still have come up with this one cool feature or bug fix.
Bottom line: Encourage lurking. Keep in mind that there are people out there who prefer to work stuff out on their own and then decide if they want to get involved.
This is really helpful! Most of us didn't really start out in big Open Source projects, so I suspect that things which seem obvious if you've come from that environment didn't occur to us. Some would be harder than others - for example, our main means of communication is via Campfire chat rooms, which aren't that conducive to just dropping in - but I think there are definitely things we could build on here. Thanks!
While Zooey and others are looking at ways we can improve this long-term, in the short term, you'd be very welcome to fill in the volunteer form on the basis that you won't have time to help out but you'd like to see more of what's going on.
For patches, we don't currently go through that process - every regular coder has commit access to svn, so we don't need to. However, if you have something you'd like to contribute, I expect someone could either give you access or commit a patch for you.
Comment on Accessibility, Design and Technology Meeting 29 May 2010
Rebecca Thu 10 Jun 2010 08:41AM UTC
Last Edited Thu 10 Jun 2010 08:44AM UTC
Comment Actions
Zooey_Glass Thu 10 Jun 2010 08:50AM UTC
Comment Actions
Cesy Wed 30 Jun 2010 10:13PM UTC
Comment Actions
Rebecca Thu 01 Jul 2010 11:42AM UTC
Comment Actions