Hello everyone, As of recent events, I want to poll the developers' perception on "Private projects in e.svn.org". Some developers were suprised that their projects (which were in trunk) were (re)moved/rewritten/majorly changed by other developers of our community. Both sides came up with reasonable arguments, I don't want to discuss here.
I'll just propose two basic and simple ideas of how code (in e's central svn, except for the dev's directories) is to be treated by other developers. The already available guidlines for commits apply for both proposals: 1.) Code in e.svn.org is free for (entire, including remove) change by anyone with commit access. People who put their code there aggree with this. The mailinglist shall be consulted in cases of 'major' changes. - Leif (T_UNIX) 2.) If a developer changes (adds/(re)moves/changes to almost rewrite) code in e.svn.org he or she has to consult the respective project's maintainer. Put your name under which idea you see suits your oppinion best. Please don't make this a flamewar and stay _on_ topic. Make sure you don't put annything in your answer besides your name/signature. This mail is not a discussion thread. If you think a different policy should be discussed feel free to open another thread so people might comment if necessary. BR, Leif ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
