Hi Michael,
I'm sending this message to the mailing list, with the intent that what I say and your reply to be public so that it can be archived for future reference.
Oooh, sounds ominous. Should my lawyer be talking to your lawyer? ;-)
advocacy, writing documentation, supporting other users and developers, submitting patches and coding new features that interest me and are in line with the project vision.
All of which are incredibly valuable!
also understand that you are working for VPRI on what must be very focused tasks without much leeway to meander endlessly as other free software projects are wont to do.
Well, there's actually a lot of leeway for meandering. The goal is to build something that is 'as small and as correct as we can' that is a complete, self-describing, self-maintaining system (where 'correct' means conceptually correct, not 'free of bugs' although the latter is obviously a goal too).
I'm quite sure that COLA, despite whatever shortcomings are in the currently public implementation phase (Jolt/Pepsi), is at a point where it would benefit from and be capable of sustaining contributions from outsiders. I would like to jump right in and help get that process going.
Great! There's lots to be done.
I presume that the reason you've been silent in response to my earlier requests (various bug fixes, the unanswered questions on LtU, no SVN commits since 2007-09-20) has been just because you're deep into the implementation of Coke and don't have the attention to spare to jobs that can be done by other people.
Sorry for the silence. October was a month of administrivia, deadlines, maintenance of non-COLA projects, demo preparation, travel, vacation, etc., with the result that I didn't read email at all for most of the month. November is a little less frantic, but I still have a backlog to clear...
For that reason, I've adopted Mercurial as my source control tool planning to continually import the COLA SVN tree, with my additions separated cleanly into different branches.
You should do whatever works best for you. Sounds like this is the perfect solution for your 'parallel' patches.
Please let me know if you would like to see patches in general, or just upon request.
Interrupts work far better than polling. If there's something you think is useful outside of your code base then please send them along to me or to this list for consideration. It's unlikely I'd remember to go looking for stuff remotely on a regular basis (and it would take up a lot more time too).
Also, would you prefer future discussion of my branch to be held on [email protected], or my own mailing list?
This mailing list is very low-volume so you wouldn't be overwhelming it, and it might be good to discuss compatible contributions in a wider context; it'd make advocacy for new features easier too. But ultimately, do whatever works best for you and for your current/ inteded use of the system!
Cheers, Ian _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
