On 23.11.2010 16:43, Jesper Louis Andersen wrote: > My take is that the coccinelle team needs to look out for the > situation where somebody forks the project and begin providing > patches. There is a "github effect" which happen on some projects: as > soon as they are present on github, contributions start to flow. The > reason is that the barrier to entry is considerably lowered.
Actually, the github effect means that people will fork your code without telling you, and they will not bother at all with sending anything upstream. Due to that, github is detrimental to project development. Fortunately there is a way to make github forks harder: Just change the internal interfaces of the code often enough that the forkers will need too much effort keeping their own trees up to date. That forces them to either submit their changes upstream or have their trees be seriously out of date and thus mostly useless for others. By the way, the Linux kernel employs a similar way to encourage upstream contribution: The internal interfaces of the kernel are changed often enough so that maintaining a module out of tree is really painful. AFAICS the Coccinelle git tree is only there to stop people from complaining, and making one commit per release means that the effort needed to keep git up to date is low. IMHO that is the best way to handle requests for git trees, especially if no substantial outside contributions exist. Julia, please don't let anybody force you to change your development style. It's your code. Regards, Carl-Daniel _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
