blob: b3a81027d0d5bec9fb07c8b5f75836decaf0bd2a (
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
|
\summary{2010}{8}{9}
\agendaitem{the mailing list situation}
\index{mailing list!gentoo-council}
\index{mailing list!gentoo-project}
\vote{merge -project and -council mls into one (-project)}{
for: scarabeus, betelgeuse, chainsaw, ferringb (as experiment first
that could be reverted), halcy0n;
against: jmbsvicetto, wired}
Fill up bug for infra to do this. (scarabeus will fill the bug)
\agendaitem{eclass API changes}
\index{eclasses!api changes}\index{PV}\index{project!qa}\index{GLEP!48}
\begin{itemize}
\item
document better what PV means, \bug{331921}
\item
make it easier for QA to take action when common sense is *not* used and
things are broken
\item
QA team will update its internal policies about the process to request the
suspension of commit rights from a developer. The revision might involve an
update to \glep{48}. (QA mailinglist)
\end{itemize}
\agendaitem{fallout and suspension policies}
\index{suspension policies}\index{package!dev-lang/python}
\begin{itemize}
\item
learn from the python breakage to promote the importance of current
policies and why developers should use them properly
\item
use this as an example of how not do things and how it should be dealt
with and start a discussion of how to recover from it and how to ensure we
can reach users in such cases
\item
continue discussion on -project ml (per 3a)
\end{itemize}
\agendaitem{council comment about the Portage breakage fallout}
\index{package!sys-apps/portage}
jmbsvicetto argued that Gentoo needs to acknowledge the incident, ensure
affected users can find correct documentation on how to fix it and make it
clear that the practices that lead to it are neither appropriate nor acceptable
\agendaitem{EAPI 4 status}
\index{EAPI!4}
ferringb will review the status, and try to find some minion to help him
\agendaitem{Bugs assigned to council@ in bugzilla and their progress}
\begin{itemize}
\item
\bug{234706}:
halcy0n will create new draft proposal soonish
\item
\bug{256451}:
last summary tbd by betelgeuse
\item
\bug{256453}:
wired wrote nice patch and it will be updated according to the comments on
-project mailinglist
\item
\bug{237381}:
jmbsvicetto plans to have something to show next mont meeting
\end{itemize}
|
GitWeb