summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20100714.tex')
-rw-r--r--decisions/summary-20100714.tex59
1 files changed, 59 insertions, 0 deletions
diff --git a/decisions/summary-20100714.tex b/decisions/summary-20100714.tex
new file mode 100644
index 0000000..50eb7ef
--- /dev/null
+++ b/decisions/summary-20100714.tex
@@ -0,0 +1,59 @@
+
+\summary{2010}{7}{14}
+
+
+\agendaitem{select the probable date for the monthly meetings}
+ 1900 UTC, 2nd Monday of each month
+
+
+\agendaitem{discuss desired 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
+ 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.
+\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
+
+ jmbsvicetto --- to continue the work to review GLEP39 and Gentoo's
+metastructure ; to study and promote ways to allow more involvement from
+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
+
+
+\agendaitem{listen to the community}
+
+ tanderson - have the council decide on proposals solely on their merit and not on the person who submits them
+