Improve 11/7, 11/8

Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

1 files changed, 31 insertions, 39 deletions

diff --git a/decisions/summary-20110715.tex b/decisions/summary-20110715.tex
index 001680c..11e3590 100644
--- a/decisions/summary-20110715.tex
+++ b/decisions/summary-20110715.tex
@@ -1,74 +1,66 @@
 
 \summary{2011}{7}{15}
 
+Agenda call: ---
 
- * allow council members to present issues to be addressed in this term (15 min)
- * listen to the community to see if there are any issues it would like
-   to see the council address in this term (10 min)
- * next meeting date / chair
-
- * Open Floor (10 min)
-       
+Agenda announcement: \agoref{gentoo-project}{16eca4f8a548ae51e5401df09e4c4d47}
 
 \agendaitem{Select the probable date for the monthly meetings}
 
-     2nd Tuesday of the month at 1900 UTC
+2nd Tuesday of the month at 1900 UTC is selected for council meetings.
      
 \agendaitem{Discuss desired model of operation}
 
-
 After a review of some of the rules used by the previous council, the 
-council
-     members opted to keep some and review others:
+council members opted to keep some and review others:
 \begin{itemize}
- \item 
- instead of choosing the chair for the next meeting at the end of a meeting,
-     interested volunteers will send an email to the mls manifesting their willingness
-     and the council will setup a schedule for the whole year by rotating the task by
-     them. Chairs will also serve as secretaries and summaries should be maintained
-     during meetings by using a collaborative tool. 
- \item
- the council will use bugs to track issues. A specific council member will be
-     assigned to each bug to track it. The bugs progress will be reviewed on 
+\item 
+instead of choosing the chair for the next meeting at the end of a meeting,
+interested volunteers will send an email to the mailing lists manifesting their willingness
+and the council will setup a schedule for the whole year by rotating the task by
+them. Chairs will also serve as secretaries and summaries should be maintained
+during meetings by using a collaborative tool. 
+\item
+the council will use bugs to track issues. A specific council member will be
+assigned to each bug to track it. The bugs progress will be reviewed on 
 meetings.
- \item
- the council members will discuss issues in the mls before the meetings so they
-     can focus on voting during the meetings.
- \item
- the council is open to have a 2nd montly meeting (possibly on the 4th Tuesday
-     of the month) or impromptu meetings when required.
-     Petteri recalled the council webapp and bot work is progressing so that should
-     help with chairing the meetings.
+\item
+the council members will discuss issues in the mailing lists before the meetings so they
+can focus on voting during the meetings.
+\item
+the council is open to have a 2nd montly meeting (possibly on the 4th Tuesday
+of the month) or impromptu meetings when required. \dev{betelgeuse} recalled 
+the council webapp and bot work is progressing so that should help with chairing the meetings.
 \end{itemize}
 
 
 \agendaitem{Allow council members to present issues to be addressed in this 
 term}
    
-     No member opted to present any issues at this time.
+No member opted to present any issues at this time.
 
      
 \agendaitem{Council election results}
+\index{project!elections}\index{council!election results}
 
-Jorge requested during the meeting that the council election results be moved to
-     the elections project space and be linked from the council space, instead of the
-     current duplication. The council members agreed with the change and Jorge will
-     ensure it is carried out.
+\dev{jmbsvicetto} requested during the meeting that the council election results be moved to
+the elections project space and be linked from the council space, instead of the
+current duplication. The council members agreed with the change and \dev{jmbsvicetto} will
+ensure it is carried out.
 
 \agendaitem{Modifying GLEP 39}
-\index{GLEP!39}
      
-Donnie asked for a clarification by the council members on whether they think a
-     global dev vote is required to update GLEP39 or not. The council voted 5 yes and
-     1 no that the council can't change GLEP39 as it requires a full developer vote.
+\dev{dberkholz} asked for a clarification by the council members on whether they think a
+global dev vote is required to update \glep{39} or not. The council voted 5 yes and
+1 no that the council can't change \glep{39} as it requires a full developer vote.
 
 \agendaitem{Further meeting}
      
 The council voted 4 yes and 3 no that there's no requirement for another meeting
-     this month to meet the requirements of GLEP39.
+this month to meet the requirements of \glep{39}.
 
 
 \agendaitem{Listen to the community}
 
-   No issues were brought up to the council by the community.
+No issues were brought up to the council by the community.