| 1 |
On 30/06/16 21:00, Kristian Fiskerstrand wrote: |
| 2 |
> On 06/30/2016 09:52 PM, NP-Hardass wrote: |
| 3 |
>> On 06/30/2016 03:43 PM, Kristian Fiskerstrand wrote: |
| 4 |
>>> On 06/30/2016 09:39 PM, Manuel Rüger wrote: |
| 5 |
>>>> On 30.06.2016 02:06, Kristian Fiskerstrand wrote: |
| 6 |
>>>>> On 06/30/2016 02:05 AM, Göktürk Yüksek wrote: |
| 7 |
>>>>>> Hi, |
| 8 |
>>>>>> |
| 9 |
>>>>>> Kristian Fiskerstrand: |
| 10 |
>>>>>>> This is a call for nominations to a member-initiated election |
| 11 |
>>>>>>> of a lead for the Proxy Maintainers project. |
| 12 |
>>>>>>> |
| 13 |
>>>>>> I propose "no-lead" to be an option to run the project officially |
| 14 |
>>>>>> without a leader. |
| 15 |
>>>>>> |
| 16 |
>>>>> A lead is required for gentoo projects, so thats not an option. |
| 17 |
>>>>> |
| 18 |
>>>>> |
| 19 |
>>>> Just being curious, is there a GLEP that defines this? |
| 20 |
>>> GLEP 39, " It may have one or many leads, and the leads are selected by |
| 21 |
>>> the members of the project. This selection must occur at least once |
| 22 |
>>> every 12 months, and may occur at any time." |
| 23 |
>>> |
| 24 |
>>> |
| 25 |
>> My interpretation of this statement is "may" means optional. It doesn't |
| 26 |
>> say must have at least one lead. |
| 27 |
>> |
| 28 |
> May refers to the choice of 1 or multiple |
| 29 |
> |
| 30 |
I think most would better understand the use of *must* rather than *may* |
| 31 |
would have a clearer meaning if the interpretation was intended as |
| 32 |
Kristian suggests. In lieu of additional consultation on the subject, I |
| 33 |
suggest the project uses the wording as is, and as others have confirmed |
| 34 |
the interpretation of 'may' is preserved as indicating an option rather |
| 35 |
than enforcing a mandate. |
| 36 |
|
| 37 |
MJE |
Archives