+1 for github. I recently decided on github for my fledgling project[1] for the same reasons that you mentioned. Its definitely a superior solution for encouraging patches. Patches don't get lost or forgotten this way. It also has the benefit of allowing the community to review a more complicated patch/feature in its entirety. Just clone the fork and try it out on your box.
This also has promise for Radiant extensions. Its a low cost way for people to throw up the work they've done. Someone else might just want to finish off one of my half-assed extensions some day. It should also be possible to build an "official" extensions project of officially sanctioned and tested extensions that are pulled in from individual development efforts. Good luck with this new approach. Look for my fork as soon as I have something to contribute ;-) Sean Schofield [1] http://github.com/schof/spree/tree/master _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
