-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 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. - -- NP-Hardass -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXAfRPAAoJEBzZQR2yrxj7ER0P/1CGUdUBNaGNV6BmawohnbIs U6OsqSGOM1VJk6KjG+wZkhi+BdbNfTrv/3ynrE39fJO1XqmOrBRSJ5PBIpQZHoHP N6IfiZgUHvGpdFr8nmLrEBNSP9VUZ56UJYS468hWObUOehp1V4TZDfKWAoi1SA5k RwAZUu0L69I6I06wodnP1yBuIk56sPmCUdwGC0oOmQnEyPdIsQ934VYnRg2yfXqg 8fFaoXdPYOX/Au+dEDGyEWVRd73XRyMEFkt3IVvewph1X/nQ63ArbYsiNvTh/tnO XLz0M5Tk726ONRRflvb2A5K6fC+/s3wQBGWThLJcuA45MOr470EBsnAy0Ii1ZuD3 WtRT1h57pBO4HEZ1WQfgfAfNRXgp4E8hiCY5Rgd0CcI/Z/QzLrZG49oFaWiTfd7I wfIWZ0oyrYtL9UiXBU8ArDjQmQRqbS4iATMeXvfHLFUAYjXrySwdlTEa/lK7OVWE 8WAL2SR/UUrzn097NuT2Sj270a9ShmW9rdM6hl9gnRlwbO4+K2KwXHh1FK3sx60g MOAgy0jxVaNWqjwrXEocXbziQIqofmRa47mcjJ1/ipH+gWZfoYt6gICIziIkCJxH GaCURYGwFdGvfVLdDsKaopVcJ31XbQZHckYSrJcRqtLd2QCTRV19R/FYORDiTJU2 LTyD0d43Kh5E6Ob7PA6b =50RB -----END PGP SIGNATURE-----
