\summary{2008}{9}{11}

Agenda call: \agoref{gentoo-dev}{fe14a3fbca60e1f6da6a81c6f2ad5725}

Agenda announcement: \agoref{gentoo-dev}{619e8ac19efadb77a5c24add7a7b529b}


\agendaitem{Filling the empty slot}
\index{council!members}

Last time there was an empty slot, we voted on whether to fill the slot 
with the next person from the original rankings. Let's do the same this 
time.\footnote{\dev{flameeyes} resigned from the 
council.} The next in ranking is \dev{cardoe}.

\vote{Approve \dev{cardoe} for the empty council slot.}{Approved. \dev{cardoe} 
is a new council member.}


\agendaitem{PMS as a draft standard of EAPI 0}
\index{PMS}\index{EAPI!0}\index{EAPI!0!approval}\index{project!pms}

Shall PMS be approved as a draft standard of EAPI 0?

The following requirements were worked out in discussion during the meeting:
\begin{itemize}
 \item 
 There should be a PMS lead who is a Gentoo developer. Both \dev{cardoe} and 
 \dev{antarus} volunteered if this was needed.
 \item
 The conflict resolution process that we agreed upon last week should be 
 documented.
 \item
 The patch acceptance process should be documented.
 \item
 A public mailing list should be created so discussions and patches aren't lost 
 on the pms-bugs alias.
\end{itemize}

Vote result: PMS is a draft standard of EAPI 0, with acceptance conditional 
upon resolution of the above four requirements. They should be resolved within 
two weeks.