summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2018-05-25 22:48:36 +0200
committerAndreas K. Hüttel <dilfridge@gentoo.org>2018-05-25 22:48:36 +0200
commitae21387202ccfdfcb25555cf9f3611e893074883 (patch)
tree2415028f645d5f5a0a469b066d55d8dc7d410660 /decisions/summary-20101130.tex
parentImprove 9/2010 and 10/2010 (diff)
downloadcouncil-ae21387202ccfdfcb25555cf9f3611e893074883.tar.gz
council-ae21387202ccfdfcb25555cf9f3611e893074883.tar.bz2
council-ae21387202ccfdfcb25555cf9f3611e893074883.zip
Improve 2010/11 and 2010/12
Diffstat (limited to 'decisions/summary-20101130.tex')
-rw-r--r--decisions/summary-20101130.tex66
1 files changed, 37 insertions, 29 deletions
diff --git a/decisions/summary-20101130.tex b/decisions/summary-20101130.tex
index 2c2a0eb..4c2abcb 100644
--- a/decisions/summary-20101130.tex
+++ b/decisions/summary-20101130.tex
@@ -1,48 +1,56 @@
\summary{2010}{11}{30}
+Agenda call: \agoref{gentoo-project}{02f133c3f1ef09e5ec04f055b5cf5ba7}
-\agendaitem{future meetings}
+Agenda announcement: \agoref{gentoo-project}{d5f9f86f7f8051379cc164207bf1f222}
-We've talked [on alias] about alternating between Tuesdays and
- Saturdays, because Halcy0n can't do weekdays and Chainsaw couldn't do
- weekends.
-
- In the meeting it turned out that Chainsaw can do Saturdays,
- although the timing is really hard for ferringb.
- We decided to have our next meeting on Saturday the 18th of December,
- at 1500 UTC. jmbsvicetto will chair.
+\agendaitem{Future meetings}
+\index{council!meeting!schedule}
- We'll keep switching between Tuesdays and Saturdays for the time
- being to try and accomodate all members.
+The council members have discussed internally alternating between Tuesdays and
+Saturdays, because \dev{halcy0n} can't do weekdays and \dev{chainsaw} can't do
+weekends. During the meeting it turned out that \dev{chainsaw} can attend on
+Saturdays, although the timing is then really hard for \dev{ferringb}.
+
+The council decided to have the next meeting on Saturday the 18th of December,
+at 1500 UTC. \dev{jmbsvicetto} will chair. We'll keep switching between Tuesdays
+and Saturdays for the time being to try and accomodate all members.
\agendaitem{EAPI 4}
-\index{EAPI!4}\index{MERGING_FROM}
+\index{EAPI!4}\index{MERGING_FROM}\index{PMS}
+\index{REPLACED_VERSIONS}\index{REPLACED_BY_VERSION}
+\index{pkg_pretend}\index{EAPI!usage in ebulds}\index{EAPI!deprecation}
+
+The council agreed that the current EAPI-4_pre1 implementation is pretty good.
+Some clarifications concerning REPLACED_VERSIONS and REPLACED_BY_VERSION and the
+impact of the new pkg_pretend phase were discussed.
+\dev{ulm} will work on a PMS patch for EAPI-4. He will create a final tag, that
+will also include one extra feature, a variable called MERGING_FROM, available
+in pkg_* phases, with the following possible values: ["source","binary"].
+
+The tag will then be approved by the council, either by email or in a meeting,
+whatever is faster. Our goal is to have EAPI-4 before 2010 ends.
-The council agreed that the current EAPI-4_pre1 implementation is
- pretty good. Ulm will work on a PMS patch for EAPI-4. He will
- create a final tag, that will also include one extra feature, a var
- called MERGING_FROM, available in pkg_* phases, with the following
- possible values: ["source","binary"].
+On a related note, a discussion about deprecating EAPIs and the QA
+recommendation on which EAPI to use for new ebuilds was started.
-The tag will then be approved by the council, either by email or in a
- meeting, whatever is faster. Our goal is to have EAPI-4 before 2010
- ends.
-\agendaitem{la files removal status/progress}
+\agendaitem{Libtool archive (.la) files removal status/progress}
\index{.la files}\index{package!sys-devel/libtool}
-Nothing has happened since the last meeting. Jorge did start some ML
- threads, but there was no interest in the subject.
+Nothing has happened since the last meeting. \dev{jmbsvicett} did start some
+mailing list threads, but there was no interest in the subject.
-This needs to be done:
+The following needs to be done:
\begin{enumerate}
-\item write a doc (w/ Diego's blog as source)
-\item publish news item
-\item get portage 2.1.9 stable
-\item let devs remove la files.
+\item write documentation (with \dev{flameeyes}'s blog as source),
+\item publish a news item,
+\item get portage 2.1.9 stable, and
+\item let developers remove .la files.
\end{enumerate}
-Since no-one volunteered to do 1, we'll push it to the ML.
+Since no-one volunteered to do step 1, the topic was pushed to the mailing
+lists.