blob: 554388a22c74e64cc79631e56184c4910a2d837c (
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{2011}{4}{8}
Agenda call: \agoref{gentoo-project}{8aa9417185bf730d868e353beb1ffc1e}
Agenda announcement: ---
\agendaitem{Project Canterbury, Gentoo's restructure}
\index{Project Canterbury}
These two topics were added to the agenda for April's Fool day.\footnote{Unfortunately
the link for Project Canterbury only points to the main Gentoo website,
which was likely modified on April 1st.}
\agendaitem{Council web app}
\index{council!web app}\index{GSoC}
\dev{betelgeuse} asked for this topic to be added to the meeting right before
its start as
a student submitted an application for GSoC for doing a council application
(dead link). As \dev{betelgeuse} presented it, the application would provide at least
the following 3 features: 1) doodle like feature or doodle integration for
setting times 2) irc bot for automatic log handling (integrate with some
existing software) 3) handling agendas. Other members noted that if it could
also deal with voting, that would be great. There was some discussion about
technical details but the council decided to focus on whether the project was
desired and leave the discussion about details for later. The council members
didn't object to the idea and are open to see what will come out of that
project. \dev{betelgeuse} will mentor the student for the project and
\dev{ferringb} will watch over it.
\agendaitem{Progress on the slacking arches topic}
\index{arches!slacking}\index{automated testing}
\index{statistics}\index{arches!resources}
\dev{jmbsvicetto} explained to the other council members that he had planned to
start a new round of emails at the start of the week, but work got in the way.
He informed the other members that he will send 3 or 4 emails during this
weekend about ``hiring people'' (to address the lack of people), ``automated
testing'', ``statistics'' and a revised email about ``arch resources''.
\dev{wired} volunteered to send the email about ``automated testing'' and
manifested his interest to participate in this discussion.
\agendaitem{Open bugs with council involvement}
\index{GLEP!54}\index{appeals process}
\begin{itemize}
\item
\bug{234706}: The council agreed on adding a note that it's working on this
issue
\item
\bug{234711}:
The council agreed on adding a note that it has decided to use ``live'' as
the suffix instead of ``scm'' if \glep{54} ever goes forward and to leave the
bug open.
\item
\bug{237381}:
\dev{jmbsvicetto} promised to finally take care of this bug.
\item
\bug{237381}, \bug{331987}:
Both bugs are on infrastructure side so there's nothing for the council to do
about them.
\item
\bug{341959}:
\dev{scarabeus} noted that the devmanual needs some updates and \dev{wired}
volunteered to take care of this bug.
\item
\bug{344479}:
\dev{jmbsvicetto} will take care of this bug.
\end{itemize}
\agendaitem{Open floor}
No issues were brought forward to the council.
|
GitWeb