On Wed, 20 Mar 2013 17:13:01 +0000 Sven Vermeulen <[email protected]> wrote:
> I'd like to suggest a few changes on our GDP policy, namely: > > - updating the license comment if you use a different license should be > mandatory (hence switch from "should" to "must") approved. > - drop using metadoc.xml for registering long outstanding bugs approved. i'd forgotten that was even setup that way. we haven't used it like that in years. > - have project lead (or delegated person) "decide" on the recruitment > process / progress approved. especially since i'm away quite a bit these days with health issues -- i read everything sent in to bugzie and the lists, but am unable to do much activity-wise. more than one designated contact, and a streamlined recruitment, is a good idea. (i volunteer you, if you're willing. :) ) > - drop mandatory gdp quiz, make it recommended approved, tentatively. we need to be careful going forward to make sure that folks at least know the basics of GDP so they don't break the tree (and/or their translations). the point of the quiz is to make sure that everyone is "on the same page" so that we don't have wildly different code styles, broken code, or lacking knowledge on how to do "stuff." we can keep an eye on potential new recruits without the up-front strict requirements; make sure they know what they're doing. we do already have guidelines in place for translations for example, where we do as-is or reject-all for proxy commits, so...this new way of doing it could fit right in. though a revised quiz might not be a bad idea. as it is, i've caught a lot of errors on every quiz i've reviewed, so it is good that folks get their misconceptions corrected early in the process, so they spend more time writing good code, and less re-writing bad. thanks again for your extensive review and suggestions, sven! (and for inadvertently giving me a needed kick-in-the-pants.) i'm in favor of making all these changes happen.
signature.asc
Description: PGP signature
