On 04/04/16 05:57, NP-Hardass wrote: > On 04/04/2016 12:34 AM, Göktürk Yüksek wrote: >> +sufficient for adding or removing a developer. Note that >> different +projects have different requirements and procedures for >> recruiting +developers, which may require prior arrangements to be >> made before +modifying the member list. > I'm not particularly fond of this statement. The implication is that > most projects require permission, whereas I believe that the opposite > is true. To the best of my knowledge, most projects are open, and > ones that have special requirements almost always list them explicitly > on their project pages. As far as I know, the only exception to this > is new developers, as they are noobs and thus project lead approval is > a slight quality control. I'd rather see it worded more like: > > Seasoned developers, generally speaking, can join any project at their > leisure, however, some projects explicitly list restrictions or > requirements to join such as training, apprenticing, or approval of > the project lead. When in doubt, consulting the project/lead prior to > joining a project. > > Still needs some work, I think ... :)
signature.asc
Description: OpenPGP digital signature
