summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'decisions/summary-20080214.tex')
-rw-r--r--decisions/summary-20080214.tex89
1 files changed, 33 insertions, 56 deletions
diff --git a/decisions/summary-20080214.tex b/decisions/summary-20080214.tex
index edc02ab..6bf3e48 100644
--- a/decisions/summary-20080214.tex
+++ b/decisions/summary-20080214.tex
@@ -1,72 +1,52 @@
\summary{2008}{2}{14}
+Agenda call: \agoref{gentoo-dev}{eedef3ff358221e8dd267182f8ff9103}
+
\agendaitem{Code of Conduct enforcement}
\index{Code of Conduct!enforcement}
-Last month:
- Council members agreed on the direction.
- dberkholz will provide additional details on -council ML
-
- Updates:
- dberkholz posted a simple suggestion to -council last night:
- \agoref{gentoo-council}{ba125098c929ea31f34051dfb009d436}
- The basic idea is to just promote individual devs responding to
- people who are being jerks. Privately, unless things get out of
-hand. Council supported the implementation.
- dberkholz will get things going.
-
+\dev{dberkholz} posted a simple suggestion to -council last night, see the
+\agoref{gentoo-council}{ba125098c929ea31f34051dfb009d436}. The basic idea is to
+just promote individual developers responding to people who are being jerks.
+Privately, unless things get out of hand. Council supported the implementation.
+\dev{dberkholz} will get things going.
\agendaitem{Document of being an active developer}
-\index{developer certificate}
-
- Last month:
- dberkholz and araujo will look into a scribus based template.
- Devrel will have to generate a signing key for these purposes.
+\index{developer certificate}\index{project!devrel}
- Updates:
- araujo was working on a script to automatically insert data into XML
- in scribus or inkscape formats. He said he would work on it
- this weekend.
+Updates: \dev{araujo} was working on a script to automatically insert data into
+XML in scribus or inkscape formats. He said he would work on it this weekend.
- Template file on hold pending format decision from script
+Creating the template file is on hold pending a format decision from this
+script project.
- Any news from devrel on key? dberkholz pinged musikc for an update.
+Any news from devrel on key? \dev{dberkholz} pinged \dev{musikc} for an update.
\agendaitem{Slacker arches}
\index{arches!slacking}
- Last month:
- vapier will work on rich0's suggestion and repost it for
- discussion on -dev ML
-
- Updates:
- No changes.
+There was no news on this issue.
\agendaitem{GLEP 54: scm package version suffix}
\index{GLEP!54}\index{scm version suffix}
- Last month:
- Sent back to -dev. peper was to repost it.
-
- Updates:
- No discussion on -dev. No resubmission to council.
+Concerning \glep{54}, none of the planned discussion on gentoo-dev took place.
+No resubmission to the council was done.
\agendaitem{GLEP 55: Use EAPI-suffixed ebuilds (.ebuild-EAPI)}
\index{GLEP!55}\index{EAPI suffix}
- Last month:
- Sent back to -dev
- Updates:
- No discussion on -dev. No resubmission to council.
+Concerning \glep{55}, none of the planned discussion on gentoo-dev took place.
+No resubmission to the council was done.
\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}
@@ -80,30 +60,27 @@ References:
\agoref{gentoo-dev}{46d474d621455bc204654dc483e87cc5}
\end{itemize}
-Approved, with a caveat
-
- Questions were raised about requiring http:// and https:// only.
- What about ftp:// ? What about no limitation, and requiring
- tools to throw out protocols they don't recognize?
- Why is that restriction there?
+The GLEP was approved, with a caveat: Questions were raised about requiring
+http:// and https:// only. What about ftp:// ? What about no limitation, and
+requiring tools to throw out protocols they don't recognize? Why is that
+restriction there?
- Once those questions are resolved, it will be finalized.
+Once those questions are resolved, the GLEP will be finalized.
\agendaitem{EAPI=1: Where is the approved specification?}
-\index{EAPI!1}\index{EAPI!0}
+\index{EAPI!1}\index{EAPI!0}\index{PMS}
Reference: \agoref{gentoo-dev}{e1b4a369534e30b8a64c6c6429cfe729}
-A long discussion was had about whether we should continue using
- EAPI=1 when we don't have EAPI=0 approved, reverting EAPI=1, and the
- value of specifications in producing quality code. People generally
- agreed about not adding any new EAPIs until the PMS for EAPI=0 is
- approved, but there wasn't agreement on changing anything about
- EAPI=1.
+A long discussion was had about whether we should continue using EAPI=1 when we
+don't have EAPI=0 approved, reverting EAPI=1, and the value of specifications in
+producing quality code. People generally agreed about not adding any new EAPIs
+until the PMS for EAPI=0 is approved, but there wasn't agreement on changing
+anything about EAPI=1.
- To make forward progress, Halcy0n agreed to work on getting the PMS
- ready for EAPI=0. He asked for anyone else interested to contact him
- so we can get it done and approved ASAP.
+To make forward progress, \dev{halcy0n} agreed to work on getting the PMS ready
+for EAPI=0. He asked for anyone else interested to contact him so we can get it
+done and approved ASAP.
- Halcy0n will give us an update at the next council meeting.
+\dev{halcy0n} will give us an update at the next council meeting.