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