summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2017-05-18 23:21:08 +0200
committerAndreas K. Hüttel <dilfridge@gentoo.org>2017-05-18 23:21:08 +0200
commit56a0af72f879ac4e74174fb64f723089110e5dca (patch)
tree23a3b2ec963f97f76479801c5c31672d0574d5cb /decisions/summary-20091207.tex
parentAdd council meeting log 20170514 (diff)
downloadcouncil-56a0af72f879ac4e74174fb64f723089110e5dca.tar.gz
council-56a0af72f879ac4e74174fb64f723089110e5dca.tar.bz2
council-56a0af72f879ac4e74174fb64f723089110e5dca.zip
Improve up to 1/2010
Diffstat (limited to 'decisions/summary-20091207.tex')
-rw-r--r--decisions/summary-20091207.tex83
1 files changed, 40 insertions, 43 deletions
diff --git a/decisions/summary-20091207.tex b/decisions/summary-20091207.tex
index 10997d1..35bee83 100644
--- a/decisions/summary-20091207.tex
+++ b/decisions/summary-20091207.tex
@@ -1,43 +1,23 @@
\summary{2009}{12}{7}
-Agenda call:
+Agenda call: \agoref{gentoo-dev}{e588558e19aefd9f477f452cfdce955a}
Agenda announcement:
\agoref{gentoo-council}{55e2123621095cba53e2fe4d700bfb76}
-\agendaitem{Actions}
-\index{council!votes!by mail}
-
-\begin{itemize}
- \item
- Discuss voting by e-mail post-meeting in case of absence
- \item
- ulm to talk with Zac Medico about defining current portage mtime
- preservation behaviour for documenting in EAPI-3
- \item
- dertobi123 to check what day of the week is best for council members
- nowadays and what week to hold the next meeting, possibly rescheduling
- the next meetings date
- \item
- lu_zero missed the meeting while having a slacker mark, figuring out
- what happens next (via e-mails) is necessary before the 18th December,
- 2009.
-\end{itemize}
+\agendaitem{EAPI 3 status}
-\agendaitem{EAPI-3 status}
+The ETA of EAPI 3, see \bug{273620}, is according to \dev{zmedico} roughly 3
+months. The currently implemented EAPI 3 items have no significant benefits to
+warrant a new EAPI with only the items that are already implemented. Because
+prefix support will be EAPI 3 (see below), the EAPI items referenced here will
+be referred to as EAPI 4 in the future.
-The ETA of EAPI-3, see \bug{273620}, is roughly 3 months. The currently
-implemented
-EAPI-3 items have no significant benefits to warrant a new EAPI with
-only the items that are already implemented.
-Because prefix support will be EAPI-3 (see below), the EAPI items
-referenced here will be referred to as EAPI-4 in the future.
-
-\agendaitem{Prefix support}
-\index{prefix}
+\agendaitem{Prefix support in PMS}
+\index{prefix}\index{EAPI!3}\index{EAPI!4}
References:
\begin{itemize}
@@ -50,23 +30,40 @@ References:
\end{itemize}
-The council accepts (4x yes, 2x abstain) the technical proposition
-about Prefix support made to it by now, in the form of a PMS patch,
-answers by the Prefix team members to the discussion thread and the
-portage branch implementing this.
-
-The council majority voted for a quick prefix-specific EAPI bump,
-from here-on known as EAPI-3. The previously intended collection
-of EAPI changes for a EAPI-3 will likely be referenced from now on
-as EAPI-4 instead.
+The council accepts (4x yes, 2x abstain) the technical proposition about Prefix
+support made to it by now, in the form of a PMS patch, answers by the Prefix
+team members to the discussion thread and the portage branch implementing this.
+The council majority voted for a quick prefix-specific EAPI bump, from here-on
+known as EAPI 3. The previously intended collection of EAPI changes for an EAPI
+3 will likely be referenced from now on as EAPI 4 instead.
\agendaitem{mtime preservation}
\index{mtime preservation}\index{EAPI!3}
-The council majority voted to document precisely the current behavior
-of portage and what can be relied upon as part of the upcoming EAPI-3
-(prefix support EAPI), so that since EAPI-3 the current portage
-behaviour can be relied upon from all compliant package managers.
-The exact behaviour needs to still get documented, however.
+The council majority voted to document precisely the current behavior of
+portage and what can be relied upon as part of the upcoming EAPI 3 (prefix
+support EAPI), so that since EAPI 3 the current portage behaviour can be relied
+upon from all compliant package managers. The exact behaviour still needs to be
+documented, however.
+
+
+
+\agendaitem{Actions}
+\index{council!votes!by mail}\index{slacker mark}
+
+\begin{itemize}
+ \item
+ Discuss voting by e-mail post-meeting in case of absence
+ \item
+ \dev{ulm} is to talk to \dev{zmedico} about defining current portage mtime
+ preservation behaviour for documenting in EAPI 3
+ \item
+ \dev{dertobi123} is to check what day of the week is best for council members
+ nowadays and what week to hold the next meeting, possibly rescheduling the next
+ meeting date
+ \item
+ \dev{lu_zero} missed the meeting while having a slacker mark; figuring out
+ what happens next (via e-mails) is necessary before the 18th December 2009.
+\end{itemize}