summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20080925.tex')
-rw-r--r--decisions/summary-20080925.tex49
1 files changed, 23 insertions, 26 deletions
diff --git a/decisions/summary-20080925.tex b/decisions/summary-20080925.tex
index 136fa46..92fd637 100644
--- a/decisions/summary-20080925.tex
+++ b/decisions/summary-20080925.tex
@@ -1,50 +1,47 @@
\summary{2008}{9}{25}
+Agenda call: \agoref{gentoo-dev}{e56a4be3a7fdfd47ce26583dd32f0f69}
+
+Agenda announcement: \agoref{gentoo-dev}{26d869ad968c831e4e8cc08d66a188ee}
+
\agendaitem{EAPI 2}
\index{EAPI!2}\index{EAPI!2!approval}
-Goal: Vote on approval
-
-Requirements:
+On the procedure side, it was agreed to
\begin{itemize}
\item
- Put a generated copy (preferably HTML) in the PMS project webspace.
- People who want to refer to an EAPI=2 reference don't necessarily
+ put a generated copy (preferably HTML) in the PMS project webspace.
+ People who want to refer to an EAPI 2 reference don't necessarily
want to install all the dependencies to build it.
\item
- Let's tag the git repository something like
+ tag the git repository something like
eapi-\$EAPI-approved-\$DATE.
\end{itemize}
-
-Result: EAPI=2 is approved.
+With that in mind, EAPI 2 was approved by vote.
-\agendaitem{PROPERTIES in cache}
+\agendaitem{PROPERTIES in the metadata cache}
\index{PROPERTIES}\index{metadata cache}
-Goal: Vote: Does council need to approve cache changes?
+Does the council need to approve metadata cache content changes (i.e. changes
+to the list of cached fields)?
-Goal: Vote on approval
-
-Result: Since it's related to the EAPI, this should be another issue
-that package-manager developers resolve amongst themselves and only
-present to council if they can't agree.
-
-They agree on adding it to the cache as a value that package managers
-can ignore, so it is.
+Since it's related to the EAPI, this should be another issue that
+package-manager developers resolve amongst themselves and only present to
+council if they can't agree. The package manager developers agree on adding
+PROPERTIES to the cache as a value that package managers can ignore, so it will
+be added.
\agendaitem{PROPERTIES=interactive in ebuilds}
+\index{ebuilds!interactive}\index{PROPERTIES}
-Goal: Vote: Does council need to approve global-variable changes in
- ebuilds?
-
-Result: This is a retroactive, backwards-compatible EAPI change and thus
-is handled the same as any other EAPI change -- it requires council
-approval.
+Does the council need to approve changes of the global variables used in
+ebuilds?
-Goal: Vote on approval
+Result: This is a retroactive, backwards-compatible EAPI change and thus is
+handled the same as any other EAPI change -- it requires council approval.
-Result: PROPERTIES=interactive is approved.
+\vote{Approve PROPERTIES=interactive for use in ebuilds}{Approved.}