blob: 55884a86cc1b65ffa9697ab5f5215ab149c44cbf (
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{2008}{3}{13}
Agenda call: \agoref{gentoo-dev}{ee52223219e2ff676ba6c106c227c2a7}
\agendaitem{Document of being an active developer}
\index{developer certificate}
There were no updates
\agendaitem{Slacker arches}
\index{arches!slacking}
\dev{vapier} said he was going to work on it this weekend.
\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}
Reference: \glep{46}
There were no updates and no GLEP authors present.
\agendaitem{EAPI 0}
\index{EAPI!0}
\dev{ciaranm} has been contributing and has committed quite a few things.
\dev{halcy0n} hopes to work on it in the next couple of weeks. He informed us
that \dev{ciaranm} said when he finishes the environment tables, EAPI=0 is
probably a week of solid work from having a draft for
review.\footnote{\dev{halcy0n} wasn't around when the topic came up, so the
above info was from after the meeting.}
\agendaitem{Google Summer of Code}
\index{GSoC}
Should Gentoo developers be allowed to participate? GNOME's policy is that they
favor people who haven't contributed before, but they will accept great projects
from contributors.
Decision: The council members will become additional SoC admins, and will serve
as tiebreaker votes if they aren't actively participating in SoC project
selection. The Gentoo SoC admins will decide whether non-contributors should be
favored over contributors.
\agendaitem{Package maintainers}
\index{proxy-maintainers}\index{overlays}
The argument was made that maintaining specific packages does not necessarily
require wide-ranging developer powers and / or knowledge --- which might make
streamlining the recruitment process possible.
Decision: We'll promote proxy-maintainers and overlays more -- e.g., via GMN,
website, etc.
\agendaitem{amd64 arch team and big bug list}
\index{arches!slacking}\index{arch!amd64}
In his \agoref{gentoo-dev}{29d8d713a2d94da730ee2247426174bc}, \dev{armin76}
wrote that amd64 has many open bugs even though it's the most staffed arch team.
\dev{kingtaco} said it's hard to keep people interested in
keywording. Anyone interested has had permission to keyword and stabilize
non-system packages since 2007.1 (see -core email from \dev{kingtaco} with
subject "AMD64 keywording").
\agendaitem{Open floor}
\index{council!meeting!required attendees}
A list of required attendees for council meetings would be useful.
\dev{dberkholz} will start creating the agenda along with this list in advance
of the meeting. Posting the agenda on a Google calendar, along with other
stuff, could help. \dev{flameeyes} is starting to work with the PR team on this.
|
GitWeb