I have decided to tacitly ignore the "codifying rules might make no sense" suggestion below and written up a wiki page which gives rules for preparing a contribution.
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?PreparingContributions But then, of course the purpose isnt to break the "no rules" rule, but help others avoid stepping into the same dog patty;) - Michael Am 05.09.2012 um 16:29 schrieb Kent A. Reed: > On 9/5/2012 12:26 AM, Chris Morley wrote: >> >>> I'm not sure what the right answer is here. Putting this experimental >>> driver into master makes it easily accessible to folks like me who >>> forget Michael's git hub but at the same time it's what the Saturday >>> Night show would call Not Ready For Prime Time. >>> >> hmm Isn't that is what master is for? >> introduce/stabilize new work. >> right from buildbot page: >> "The master branch, containing the latest development >> version. >> This branch is not always stable! Use with care! And if >> it breaks, please let us know." >> >> Obviously Michael didn't mean to break anything but that is what buildbot is >> for. >> To point out that something is broken that the author didn't know about. >> particularly packaging. >> >> We do a very good job of making sure master is useable most of the time - >> to the point that some people actually use it on machines! But sometimes it >> will >> be broken. >> >> As far as I can tell, the system worked: >> new item was added, buildbot checked it and it broke, the author worked on >> fixing it. >> I see no guide lines written anywhere on what is acceptable and what is >> pushing limits. >> Maybe it is time to write down guide lines? >> >> Chris M >> > > Thanks for such a gentle reminder to RTFM! > > I'm not sure it's profitable to try to codify guidelines at this point. > We aren't such a big operation that we can't function without them > written down, and I saw some standards committees wrap themselves around > the axle with such things. > > It seems to me the current modus operandi is working well enough. Let a > new author prove his/her chops (and sincerity) before giving credentials > to add to the git repository. If enough complain about the effects, a > good author will self-calibrate; a bad one can have credentials removed. > > Regards, > Kent > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
