blob: 75d05f483365ab958039996948bc56b2c51c9ede (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
|
\summary{2007}{4}{12}
Agenda call: \agoref{gentoo-dev}{85c578debc4821504803755cd6756fb3}
\agendaitem{Code of Conduct}
\index{Code of Conduct}\index{project!proctors}
\dev{amne} has been doing a good job putting the initial group of proctors
together. We ask the proctors to address these two issues for next meeting:
\begin{itemize}
\item
add a "mission" statement, and
\item
fix the wording to have a positive spin.
\end{itemize}
\agendaitem{Splitting gentoo-dev mailing lists}
\index{mailing list!gentoo-dev}\index{project!proctors}
\index{mailing list!gentoo-dev-announce}
There was no real favorable backing for this idea. People don't like the -dev
mailing list because of the crap; splitting the lists will just move the crap
elsewhere, not really solving anything.
Let the proctors do their thing, and if need be, review this again.
\agendaitem{PMS}
\index{PMS}
The current status looks good in getting open bugs resolved. It should be up and
running as git repository on Gentoo infrastructure by the next meeting.\footnote{Some
discussion arose about getting \dev{ciaranm} as non-developer commit access.}
Let the developers sort out the todo list as the current workflow seems
to be getting things done finally.
\agendaitem{Surveys}
\index{surveys}
\dev{robbat2} will look at getting user / developer surveys in place after the
release of 2007.0. We should probably try and take fresh surveys after each
bi-annual release from now on to see if we are meeting many of users' desires.
\agendaitem{Limiting of council powers}
\index{council!limiting powers}
There doesnt seem to be real backing for this from dev community or the council
itself. If a majority of developers are truly upset / disturbed by a council
decision, it should show easily. If you dont like a council member, dont vote
for them next time.
\agendaitem{Moving gentoo-core to public archives}
\index{mailing list!gentoo-core}\index{mailing list!gentoo-dev}
Many people dislike this moving forward. It is not going to happen at this time.
We should motivate people to use -dev over -core for most things.\footnote{The
official summary also contains ``Look into getting a dev-only archive finally.'',
however, there was no agreement on this in the log --- people see it as a potential
leak.}
\agendaitem{New metastructure proposal}
This doesn't seem to address any of the problems it proposes to address.\footnote{The
topic likely refers to the \agoref{gentoo-dev}{69368b0ef5e30bdfe268a92338f5196e}.}
A large majority of developers and users prefer the single tree development style
that Gentoo has versus many smaller trees.
\agendaitem{Sync Social Contract with Gentoo Foundation (external entities)}
\index{social contract}\index{trustees}\index{foundation!trustees}
The trustees will review the statement to clarify things and then
we'll look again at syncing.\footnote{No, the log is not much clearer.}
\agendaitem{Documentation for the mail servers}
The documentation is supposed to be finished in terms of content.
\dev{wolf31o2} will look at getting it actually committed.
|
GitWeb