1 |
On Wed, Dec 18, 2013 at 3:04 AM, "Paweł Hajdan, Jr." |
2 |
<phajdan.jr@g.o> wrote: |
3 |
> Some idea: it's not that obvious to me what's the process to become a |
4 |
> GLEP editor, or to change the GLEP editors team if everyone is inactive |
5 |
> (which I think either happened recently or was very close to it). |
6 |
> |
7 |
|
8 |
The GLEP team is just an ordinary project - anybody can |
9 |
join/contribute. In fact, this is a great place for interested |
10 |
non-devs to contribute as well, and I passed a long a list of |
11 |
volunteers I solicited a few months ago to creffett (who seems to be |
12 |
doing a great job). |
13 |
|
14 |
Even though QA got some special attention recently this isn't some |
15 |
kind of a trend - in general teams should be open for anybody to |
16 |
participate in. QA just needed a bit more care (IMHO) since it has an |
17 |
unusually high level of authority/responsibility. The GLEP team (like |
18 |
every other project) doesn't have any special authority - they are |
19 |
there to be caretakers, make recommendations, etc. |
20 |
|
21 |
I think the question came up as to whether these non-substantive |
22 |
changes really need Council approval. My personal feeling is that as |
23 |
long as the changes are announced and there are no major objections |
24 |
they should be able to stand without further approval. If somebody |
25 |
questions whether a particular change is major vs minor they can |
26 |
always stick it on the council agenda. However, it isn't a big deal |
27 |
for the council to rubber-stamp minor changes either - we should be |
28 |
reading this stuff anyway and it takes little time (it just creates |
29 |
latency - unless we vote by bug as we did with the QA lead |
30 |
confirmation which got done in less than a day). |
31 |
|
32 |
Rich |