-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Andreas K. Huettel:
> On Monday 04 April 2016 06:57:51 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.
> 
> It's true that most projects are happy to accept new members, but
> usually you're expected to talk at least to some team member
> first.
> 
> (Hi I'd like to join... Sure, just add yourself!)
> 
> More of a courtesy, really... and also a good way to find out *if*
> there are any rules/restrictions.
> 
> 

My intention was to document only the mechanics involved in the
process and sidestep the permission discussion as much as possible.
Frankly, I have no experience in joining/leaving projects. I
understand that some projects are happy with people just adding
themselves without permission whereas others, like the security team,
are stricter with their requirements. Either way, the wiki will need
to be modified and possibly the alias file too. Maybe we are better
off without the last sentence, so it's less controversial?

- --
gokturk
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJXCSDrAAoJEIT4AuXAiM4zTgkIAJpoyFylEAaYzpZLiBoNw/UD
AiBpbaJUtwtfgrIs11PCKORJfsJXRd4WxuNdh05NWxsmKRht1IESoE9RokCT2eQA
NbS/GUS6r7DZEifBjAtIbgykhvzWGgq4uybxUaktp9tOn+t+/zg3rvh/1316udTR
R4eXB5n9YumUrLuvVdbeQUz/bxJ1/0mKyebrKpeci+brDPjO7xpXV2xfRimZ9msP
9R2ceDzMlEYX0V1kwe/Q+Zc9fnGw+C0Z8FXZf9fgbr/bjYDL3ROPQSvjIyiVq9zF
8aCbMIS5+ZvwbkhJJ3mnChiCkH1pujMiqlgr3dqi1XdbMjL/rsphElorQt5pbSc=
=xz02
-----END PGP SIGNATURE-----

Reply via email to