summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20100714.tex')
-rw-r--r--decisions/summary-20100714.tex90
1 files changed, 49 insertions, 41 deletions
diff --git a/decisions/summary-20100714.tex b/decisions/summary-20100714.tex
index 50eb7ef..b137f7b 100644
--- a/decisions/summary-20100714.tex
+++ b/decisions/summary-20100714.tex
@@ -1,59 +1,67 @@
\summary{2010}{7}{14}
+Agenda call: ---
-\agendaitem{select the probable date for the monthly meetings}
- 1900 UTC, 2nd Monday of each month
+Agenda announcement: \agoref{gentoo-dev}{f691d019baa3e4dd48c75f8c867ae55d}
-\agendaitem{discuss desired model of operation}
+\agendaitem{Date and time for the monthly meetings}
+
+The council agreed to meet 19:00 UTC, 2nd Monday of each month.
+
+
+\agendaitem{Model of operation}
\begin{itemize}
- \item
- using bugs to track issues:
- bugs for now (without any restrictions, fully visible and editable by any registered user)
- rails project for council management is under development, will check that when finished
+\item
+Using bugs to track issues: \index{council!web app}
+Bugzilla will be used to track issues for now (without any restrictions, fully visible and editable by any registered user); a Rails project for council
+management is under development, and will be checked out when finished
+\item
+Having an agenda item in all meetings to check the bugs status:
+\index{council!bugzilla usage}
+Discussion about bug progress should happen on each meeting. Each bug will have an assigned named council member that should be responsible for its tracking. We may use bugzilla voting capabilities if it is deemed useful.
\item
- have a section on all meetings to check the bugs status:
- discussion about bug progress should happen on each meeting.
- each bug will have an assigned named council member that should be responsible for its tracking
- we may use bugzilla voting capabilities if deemed useful
- \item
- ability to have 2nd monthly / impromptu meetings when required:
- there can be any number of meetings during the month, with the requirement of a minimal 1 week advance notice
- \item
- secretary / meeting chair:
- council members will replace a secretary by using google wave to create meeting summaries on the fly
- the chair of a meeting is going to be decided at the end of the previous meeting. scarabeus volunteers to be default fallback
- the selected chair is responsible for the initial email and the upcoming meeting agenda, as well as committing the summary of the meeting he chairs.
+Ability to have a 2nd monthly and/or impromptu meetings when required:
+There can be any number of meetings during the month, with the requirement of a minimal 1 week advance notice
+\item
+Secretary / meeting chair:\index{council!secretary}
+The council members will use Google Wave\footnote{See
+\url{https://de.wikipedia.org/wiki/Google_Wave} for some historical information on this abandoned project.} to create meeting summaries on the fly,
+thus not needing a secretary. The chair of a meeting is going to be decided at
+the end of the previous meeting. \dev{scarabeus} volunteers to be default fallback.
+The selected chair is responsible for the initial email and the upcoming meeting agenda, as well as for committing the summary of the meeting he chairs.
\end{itemize}
-\agendaitem{allow council members to present issues to be addressed in this
-term}
-
- Chainsaw --- to kill (the official status of) overlays ; to review
-package maintenance policy
+\agendaitem{Issues to be addressed in this term}
- jmbsvicetto --- to continue the work to review GLEP39 and Gentoo's
-metastructure ; to study and promote ways to allow more involvement from
+The council members plan to address the following topics:
+\begin{itemize}
+\item
+\dev{chainsaw}: to kill (the official status of) overlays, moving development to the main tree; to review package maintenance policy especially with respect to unresponsive maintainers \index{overlays}
+\item
+\dev{jmbsvicetto}: to continue the work to review \glep{39} and Gentoo's
+metastructure; to study and promote ways to allow more involvement from the
community
-
- scarabeus --- increase QA of the tree (be more strict with developers)
-and revive GWN
-
- ferringb --- make council less involved in day-to-day matters and more
-focused on bigger picture
-
- wired --- decisive and effective council
-
- halcy0n --- bigger QA hammer, easier and more straight rules for
-joining or helping out in our community
-
- betelgeuse --- putting GSoC results to some good use ; mostly PM stuff
+\item
+\dev{scarabeus}: to improve QA of the tree (be more strict with developers)\footnote{Log quote: ``I want to bash people more for commiting crap simply put.''};
+to revive the Gentoo Weekly Newsletter (GWN) \index{project!qa}\index{GWN}
+\item
+\dev{ferringb}: to make the council less involved in day-to-day matters and more
+focused on the bigger picture; also to focus on PMS\index{PMS}
+\item
+\dev{wired}: to make sure we are a decisive and effective council
+\item
+\dev{halcy0n}: to have a bigger QA hammer, and to provide easier and more straight rules for joining or helping out in our community\index{project!qa}
+\item
+\dev{betelgeuse}: to put GSoC results to some good use; then, mostly PM stuff\footnote{And, according to the log, also to stop global warming.}\index{GSoc}
+\index{global warming}
+\end{itemize}
-\agendaitem{listen to the community}
+\agendaitem{Open floor}
- tanderson - have the council decide on proposals solely on their merit and not on the person who submits them
+\dev{tanderson} requests that the council decides on proposals based solely on their merit and not on the person who submits them.