+1 It will be easy to enforce this.
David Sent from my latest-and-greatest, proprietary, DRM-enabled, crypto- locked gadget. On Apr 17, 2009, at 10:17 PM, [email protected] wrote: > I'd like to propose a change to our guidelines for accepting > community plugins. > > As it stands we do no strict code review, and just test "does it > blow up". This was (debatably) fine when we had separate trees for > community and official, but now they both exist in the same code > tree, and some of the ugly community code is sullying up our code > base. I think we should change our rules to require community > plugins to 1) not blow up, and 2) conform to mono guidelines. The > major difference will be that community plugin reviews will not be > subject to strict usability scrutiny, and fixes for bugs will not be > guaranteed. > > I realize this may discourage contributers a little bit, but I don't > think that this will be significant as long as when we review, we do > so kindly and help our contributers improve their coding, in turn > doing our new contributers a service. > > Thoughts? > > -- > -- Alex Launi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
