1 |
On Mon, Mar 26, 2018 at 7:30 PM, Rich Freeman <rich0@g.o> wrote: |
2 |
|
3 |
> On Mon, Mar 26, 2018 at 9:14 PM, Francisco Blas Izquierdo Riera |
4 |
> (klondike) <klondike@g.o> wrote: |
5 |
> > |
6 |
> > If you cvs annotate the index.xml file for the Gentoo Foundation on the |
7 |
> > old documentation CVS you'll find that such line was added by Corey |
8 |
> > Shields (cshields) on the first edition of the project page itself, |
9 |
> > revision 1.1 made on 26-March-2005 before GLEP-39 existed. According to |
10 |
> > that same page Corey was one of the members of the Board of the |
11 |
> Foundation. |
12 |
> > |
13 |
> |
14 |
> Well, that answers the first half of the question then. |
15 |
> |
16 |
|
17 |
Council is related to technical leadership, inter-project technical issues |
18 |
and issues impacting development, which can include disciplinary issues. |
19 |
|
20 |
Trustees look out for the long-term health of the project. This includes |
21 |
legal matters, social contract, and quite a few other things. |
22 |
|
23 |
I resigned after the initial trustees were appointed. It appears that the |
24 |
initial trustees had challenges making decisions and leading the project. |
25 |
However, while they might have been relatively "weak" and had very limited |
26 |
scope in practice (most likely due to being overwhelmed with their new |
27 |
responsibilities, learning to run a NFP, etc.which has a very high learning |
28 |
curve,) that does not mean that the trustees were intended to be passive in |
29 |
regards to the direction of the project. Non-technical issues that are |
30 |
large in scope should by default go to the trustees for direction. |
31 |
|
32 |
Best, |
33 |
|
34 |
Daniel |