summaryrefslogtreecommitdiff
blob: a8333fdb497cff64a3b81259cfd60d88154aea2e (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
\summary{2009}{6}{11}

Agenda call: \agoref{gentoo-dev}{690c6d098a6233d131d893e3b52bb230}

Agenda announcement: \agoref{gentoo-dev}{7c7607d3659007c40ac122fcb12fe498}


\agendaitem{Short discussion of EAPI 3 progress}
\index{EAPI!3}\index{package!sys-apps/portage}\index{package!sys-apps/paludis}

Reference: \bug{273620}

\dev{zmedico} commented that while no progress had been made, a tracker bug had 
been made, for those interested in providing patches for and tracking the 
progress of the EAPI 3 implementation. \dev{ciaranm} noted that paludis is ready 
for EAPI 3 whenever the portage implementation is finished.


\agendaitem{Default contents of ACCEPT_LICENSE (license filtering)}
\index{ACCEPT_LICENSE}

\glep{23} provided a method for users to select what licenses they are willing 
to accept based on a ACCEPT_LICENSE configuration variable. In addition it 
provided for 'license groups' so users could accept or decline to use software 
of a certain license type. What GLEP 23 did not specify was the default value of 
ACCEPT_LICENSE.

Conclusion: The council unanimously voted to have the default ACCEPT_LICENSE
value as ACCEPT_LICENSE="* -@EULA".


\agendaitem{bash 4 in EAPI 3}
\index{EAPI!3}\index{bash!features in ebuilds}\index{packages!app-shells/bash}

There were three parts to this topic:
\begin{enumerate}
\item 
Unlocking of feature requests for EAPI 3.
\item
Allowing bash-4 features in EAPI 3 ebuilds.
\item
Allowing bash-4 features in all ebuilds with EAPIs $>=$ 3 after a fixed amount 
of time in gentoo-x86 (Overlays could begin use immediately).
\end{enumerate}

Conclusion: By a 4-3 decision the council voted not to open the feature list for
EAPI 3.


\agendaitem{The banning of igli (Steve Long) from \#gentoo-council}
\index{irc!channel!\#gentoo-council}\index{irc!ban}

\dev{dev-zero} banned Steve Long (igli) from \#gentoo-council for what he called
repeated trolling after private warnings.\footnote{See 
\url{http://dev.gentoo.org/~dev-zero/council/igli.txt} for the referenced 
background.} The ban was later reversed by \dev{cardoe} because it had not been 
put to a council vote as all bans in \#gentoo-council are.

Conclusion: No decision yet, the council decided to discuss this issue privately
on the council@ alias so that precious meeting time is not spent.


\agendaitem{Define EAPI development/deployment cycles}

Reference: \agoref{gentoo-dev}{d3a4758c455fded00608e891f525d3cc}

Various Council members expressed support for \dev{ciaranm}'s EAPI 
development guidelines. However, the discussion reached no conclusion and 
quickly spiraled into a discussion of the removal of \dev{ciaranm}'s bugzilla 
privileges.


\agendaitem{Removal of Ciaran McCreesh's (ciaranm) bugzilla permissions}

At some point in the last year \dev{ciaranm}'s bugzilla permissions were
removed. He filed a bug about the issue (\bug{273759}) and was talking about
moving PMS off of Gentoo Infrastructure, a move that some council members were 
strongly opposed to. When asked about the permissions, \dev{ciaranm} had no 
objections to waiting a few days for the infra to complete an investigation into 
who removed the access and for what reason.

Conclusion: The council voted to reinstate \dev{ciaranm}'s editbugs privileges. 
\dev{solar} noted that infra will investigate who removed the privileges in the 
first place, and asked for not changing bugzilla privileges before this is 
completed.