summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2017-03-30 22:51:50 +0200
committerAndreas K. Hüttel <dilfridge@gentoo.org>2017-03-30 22:51:50 +0200
commit2d229e6291b9d8c0e6571b2e1b3c22b155669731 (patch)
treeca7547552e67738a5c8c6bdbb8eeb574f1fbf72b /decisions
parentIndex 2013/9 and 2013/10 (diff)
downloadcouncil-2d229e6291b9d8c0e6571b2e1b3c22b155669731.tar.gz
council-2d229e6291b9d8c0e6571b2e1b3c22b155669731.tar.bz2
council-2d229e6291b9d8c0e6571b2e1b3c22b155669731.zip
Index 2007/12 to 2008/5
Diffstat (limited to 'decisions')
-rw-r--r--decisions/decisions.but4
-rw-r--r--decisions/decisions.bux2
-rw-r--r--decisions/decisions.mlf8
-rw-r--r--decisions/decisions.mls8
-rw-r--r--decisions/decisions.mlt8
-rw-r--r--decisions/decisions.tex8
-rw-r--r--decisions/summary-20071213.tex98
-rw-r--r--decisions/summary-20080110.tex142
-rw-r--r--decisions/summary-20080214.tex109
-rw-r--r--decisions/summary-20080313.tex89
-rw-r--r--decisions/summary-20080410.tex99
-rw-r--r--decisions/summary-20080508.tex180
-rw-r--r--decisions/summary-20080515.tex4
13 files changed, 759 insertions, 0 deletions
diff --git a/decisions/decisions.but b/decisions/decisions.but
index 9b7c245..a604e67 100644
--- a/decisions/decisions.but
+++ b/decisions/decisions.but
@@ -20,6 +20,8 @@ Clarify Foundation page on external entities
[EAPI-1] add ECONF_SOURCE support to the default src_compile() function
187971
Gentoo Website Command Injection Issue
+188449
+[PMS] individual version component restrictions
194876
EAPI-1 tracker
211529
@@ -230,3 +232,5 @@ Please create a BZ product "Gentoo Council" similar to "Gentoo Foundation"
Council vote: CVS headers and git expansion
611376
New GitHub Terms of Service
+9202
+Better support for CVS Ebuilds...
diff --git a/decisions/decisions.bux b/decisions/decisions.bux
index f8bdcaf..081c6a4 100644
--- a/decisions/decisions.bux
+++ b/decisions/decisions.bux
@@ -1,3 +1,5 @@
+9202
+CVS ebuilds;live ebuilds
53269
GLEP!27;UIDs
154595
diff --git a/decisions/decisions.mlf b/decisions/decisions.mlf
index 87f61d4..d6238f3 100644
--- a/decisions/decisions.mlf
+++ b/decisions/decisions.mlf
@@ -56,6 +56,8 @@ Ulrich Mueller
Michał Górny
44defe3ffe0fc93ad754bd895ed0196c:gentoo-project
Chris Reffett
+46d474d621455bc204654dc483e87cc5:gentoo-dev
+Tiziano Müller
474fc6822dba50ccc6192c9f31d8024a:gentoo-project
Patrick Lauer
4929c54fc37dee78cdff606d4d9cb030:gentoo-project
@@ -162,6 +164,8 @@ b69cab4b36b6b3c6e68be82df09c2d36:gentoo-project
Pacho Ramos
b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
Ulrich Mueller
+ba125098c929ea31f34051dfb009d436:gentoo-council
+Donnie Berkholz
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Ulrich Mueller
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -178,6 +182,8 @@ d899dd93be2f93b85f65f47c54087806:gentoo-project
Pacho Ramos
daa09e196660d1ecfe2fb7a7726ce489:gentoo-project
Andreas K. Huettel
+db2f5c09c2c0c8b042ca3d0dcec7cdaf:gentoo-dev
+Ciaran McCreesh
dc5406af670aebc050362fcbd8cd528e:gentoo-project
Anthony G. Basile
dc9656603171900ed007b6be143c88da:gentoo-project
@@ -186,6 +192,8 @@ dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Brian Harring
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
Tomáš Chvátal
+e1b4a369534e30b8a64c6c6429cfe729:gentoo-dev
+Mark Loeser
e4e0ee942cf7af8f47b8e3d312498be7:gentoo-project
Andreas K. Huettel
e6eafd6be25794ca503e0ac9d6968cd3:gentoo-project
diff --git a/decisions/decisions.mls b/decisions/decisions.mls
index 191985c..f1342af 100644
--- a/decisions/decisions.mls
+++ b/decisions/decisions.mls
@@ -56,6 +56,8 @@ Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14
[gentoo-dev] [RFC] Masterplan for solving LINGUAS problems
44defe3ffe0fc93ad754bd895ed0196c:gentoo-project
Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08
+46d474d621455bc204654dc483e87cc5:gentoo-dev
+[gentoo-dev] Updated GLEP 46: Allow upstream tags in metadata.xml
474fc6822dba50ccc6192c9f31d8024a:gentoo-project
Re: [gentoo-project] Call for agenda items - Council meeting 2014-03-11
4929c54fc37dee78cdff606d4d9cb030:gentoo-project
@@ -162,6 +164,8 @@ b69cab4b36b6b3c6e68be82df09c2d36:gentoo-project
Re: [gentoo-project] Call for agenda items - Council meeting 2014-08-12
b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
[gentoo-dev] RFD: News item format 2.0
+ba125098c929ea31f34051dfb009d436:gentoo-council
+[gentoo-council] CoC: informal enforcement
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-01-10
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -178,6 +182,8 @@ d899dd93be2f93b85f65f47c54087806:gentoo-project
Re: [gentoo-project] Council meeting 2015-03-10: call for agenda items
daa09e196660d1ecfe2fb7a7726ce489:gentoo-project
Build log locales (was: [gentoo-project] Call for agenda items - Council meeting 2013-08-13)
+db2f5c09c2c0c8b042ca3d0dcec7cdaf:gentoo-dev
+[gentoo-dev] The eight digit limit
dc5406af670aebc050362fcbd8cd528e:gentoo-project
[gentoo-project] Re: [gentoo-dev-announce] Call for Agenda Items -- Council Meeting 2016-02-14
dc9656603171900ed007b6be143c88da:gentoo-project
@@ -186,6 +192,8 @@ dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Re: [gentoo-dev] New eclass: autotools-utils.eclass
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
[gentoo-project] Gentoo Code of Conduct
+e1b4a369534e30b8a64c6c6429cfe729:gentoo-dev
+Re: [gentoo-dev] One-Day Gentoo Council Reminder for February
e4e0ee942cf7af8f47b8e3d312498be7:gentoo-project
Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25
e6eafd6be25794ca503e0ac9d6968cd3:gentoo-project
diff --git a/decisions/decisions.mlt b/decisions/decisions.mlt
index 70f7d14..ec0247d 100644
--- a/decisions/decisions.mlt
+++ b/decisions/decisions.mlt
@@ -56,6 +56,8 @@ Sun, 03 Apr 2016 18:07:18
Tue, 31 May 2016 12:49:45
44defe3ffe0fc93ad754bd895ed0196c:gentoo-project
Mon, 07 Apr 2014 16:37:09
+46d474d621455bc204654dc483e87cc5:gentoo-dev
+Mon, 21 Jan 2008 09:07:57
474fc6822dba50ccc6192c9f31d8024a:gentoo-project
Fri, 28 Feb 2014 11:15:52
4929c54fc37dee78cdff606d4d9cb030:gentoo-project
@@ -162,6 +164,8 @@ b69cab4b36b6b3c6e68be82df09c2d36:gentoo-project
Tue, 29 Jul 2014 12:06:28
b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
Tue, 12 Jan 2016 18:13:51
+ba125098c929ea31f34051dfb009d436:gentoo-council
+Thu, 14 Feb 2008 10:13:41
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Sun, 27 Dec 2015 18:03:56
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -178,6 +182,8 @@ d899dd93be2f93b85f65f47c54087806:gentoo-project
Sat, 07 Mar 2015 10:28:17
daa09e196660d1ecfe2fb7a7726ce489:gentoo-project
Tue, 06 Aug 2013 14:12:57
+db2f5c09c2c0c8b042ca3d0dcec7cdaf:gentoo-dev
+Mon, 03 Mar 2008 17:42:29
dc5406af670aebc050362fcbd8cd528e:gentoo-project
Thu, 04 Feb 2016 10:08:02
dc9656603171900ed007b6be143c88da:gentoo-project
@@ -186,6 +192,8 @@ dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Sun, 18 Jul 2010 00:58:59
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
Fri, 24 May 2013 11:46:47
+e1b4a369534e30b8a64c6c6429cfe729:gentoo-dev
+Wed, 13 Feb 2008 17:58:08
e4e0ee942cf7af8f47b8e3d312498be7:gentoo-project
Tue, 11 Feb 2014 19:43:40
e6eafd6be25794ca503e0ac9d6968cd3:gentoo-project
diff --git a/decisions/decisions.tex b/decisions/decisions.tex
index 27e1749..4a48b51 100644
--- a/decisions/decisions.tex
+++ b/decisions/decisions.tex
@@ -195,6 +195,14 @@ Council members: amne, betelgeuse, dberkholz, flameeyes, jokey
\include{summary-20071011}
\include{summary-20071108}
+\include{summary-20071213}
+\include{summary-20080110}
+\include{summary-20080214}
+\include{summary-20080313}
+\include{summary-20080410}
+\include{summary-20080508}
+\include{summary-20080515}
+
\chapter{Meeting summaries 2008/09}
diff --git a/decisions/summary-20071213.tex b/decisions/summary-20071213.tex
new file mode 100644
index 0000000..ee0c2c9
--- /dev/null
+++ b/decisions/summary-20071213.tex
@@ -0,0 +1,98 @@
+
+\summary{2007}{12}{13}
+
+
+\agendaitem{New USE documentation}
+\index{USE}\index{global changes}
+
+Reference: http://archives.gentoo.org/gentoo-dev/msg_149120.xml (dead link)
+
+Considering the precedent set by how this was implemented,
+what should we do? Should we leave it or revert it? Should we require a GLEP?
+
+Other options:
+\begin{itemize}
+\item Discuss improvements on -dev, make changes, document them.
+ In other words, normal development process
+\item Leave as is
+\item Require future global changes to be sent to -dev in advance,
+ or they will be reverted.
+\end{itemize}
+
+Result of the discussion:
+\begin{enumerate}
+ \item
+ We're leaving it, and considering further changes
+ \item
+ It should have been posted to -dev before committing for discussion
+\end{enumerate}
+
+General process for global changes:
+\begin{itemize}
+ \item
+ 1. Post to -dev for discussion
+ \item
+ 2a. Consensus for implementing your idea as-is. No GLEP, no council.
+BREAK.
+ \item
+ 2b. Consensus for a GLEP for your idea, maybe disagreement over the idea.
+ Write GLEP. Discuss on -dev. Submit GLEP to council.
+ \item
+ 2c. Disagreement, but some support. No consensus for a GLEP. Respond to the
+ council agenda mail with a post containing a summary of your idea as
+ well as patches for code and documentation.
+ \item
+ 2d. No support. Refine your idea, or think of a new one. GOTO 1.
+ \item
+ 3. Council votes on the idea.
+\end{itemize}
+
+Any future global changes that aren't discussed on -dev in advance may
+be reverted by the council if at least two council members vote to revert
+the changes. Those changes must be discussed on -dev and approved by the
+council before recommitting. If they're recommitted without council
+approval, the developer in question gets kicked out.
+
+
+
+\agendaitem{Code of Conduct enforcement}
+\index{Code of Conduct}\index{mailing list!gentoo-dec}\index{IRC
+channel!\#gentoo-dev}
+
+References:
+\begin{itemize}
+ \item
+ http://thread.gmane.org/gmane.linux.gentoo.council/82 (broken link)
+ \item
+ \url{http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt}
+\end{itemize}
+
+
+Christy Fullam (musikc) made some valuable suggestions:
+
+\begin{itemize}
+\item The proposal should be restricted to only apply to \#gentoo-dev and the
+ gentoo-dev list. Most other locations already have moderators of some
+ sort, and the council can work with them directly if there are CoC
+ problems. This idea went over really well.
+\item Moderation should be capped at 2 days, and then will be handed off to
+ devrel/userrel. No council approval involved.
+\end{itemize}
+
+Mike Doty (kingtaco) suggested that we look for a way to prevent the
+snowball effect on IRC: what if a modded person is voiced/opped by an
+unmodded person, and a chain of this goes?
+
+Donnie Berkholz (dberkholz) will incorporate these changes into the
+proposal and post an update to the -council list.
+
+
+\agendaitem{Open floor}
+\index{PMS}\index{PMS!authoritative repo}
+
+Wulf Krueger (philantrop) asked which PMS repo was authoritative. The
+external one had been getting changes, and the "official" gentoo.org one
+had not. Mike Doty reported that they're working on allowing non-Gentoo
+developers to contribute to the repository, which should resolve the
+technical problems. Wulf responded that some people didn't want to
+commit to a Gentoo-hosted repository.
diff --git a/decisions/summary-20080110.tex b/decisions/summary-20080110.tex
new file mode 100644
index 0000000..c4bebc5
--- /dev/null
+++ b/decisions/summary-20080110.tex
@@ -0,0 +1,142 @@
+
+\summary{2008}{1}{10}
+
+
+\agendaitem{GLEP 54: scm package version suffix}
+\index{scm suffix}\index{CPV}
+
+Reference: \glep{54}
+
+Comment from portage maintainer:
+\begin{itemize}
+ \item
+ no statement about compatibility/implementation plans
+ \item
+ more subjective:
+ \begin{itemize}
+ \item while a distinction between CPV and atom may not be technically
+ required, I might be useful to have
+ \item (minor) if the version part is optionl there could be some
+ complications
+ \end{itemize}
+\end{itemize}
+
+So is this something we'd like to have?
+
+Other ideas that came up during discussion:
+\begin{itemize}
+ \item
+ -scm or _scm ?
+ \item
+ handling as (-|_pre)9999) versions per definition
+ \item
+ implement as dynamic package sets
+\end{itemize}
+
+Related bugs: \bug{9202}
+
+Pushed back to -dev ML as there are too many unresolved questions at
+ the moment. peper is given the task to repost it and expand on
+ usefulness / use cases as well as compatibility issues.
+
+
+\agendaitem{GLEP 55: Use EAPI-suffixed ebuilds (.ebuild-EAPI)}
+
+Reference: \glep{55}
+
+Agreement on eapi subdirectories are not feasible.
+
+Ideas during discussion:
+ moving from EAPI= to eapi function and using repository bashrc for
+ compatibility
+
+Pushed back to -dev ML as there are too many unresolved questions at
+ the moment.
+
+
+
+\agendaitem{Slacker arches}
+\index{arches!slacking}
+
+References:
+\begin{itemize}
+ \item
+ Calebs post:
+ http://article.gmane.org/gmane.linux.gentoo.devel/53933 (dead link)
+ \item
+ Kumba's comment on mips status:
+ http://article.gmane.org/gmane.linux.gentoo.devel/54168 (dead link)
+ \item
+ Rich0's proposal:
+ http://article.gmane.org/gmane.linux.gentoo.devel/54103 (dead link)
+\end{itemize}
+
+vapier will work on rich0's suggestion and repost it for discussion on
+ -dev ML
+
+
+
+\agendaitem{Code of Conduct}
+\index{Code of Conduct!enforcement}
+
+
+References:
+\begin{itemize}
+ \item
+ http://thread.gmane.org/gmane.linux.gentoo.council/82 (dead link)
+ \item
+ http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt
+ \item
+ http://www.gentoo.org/proj/en/council/meeting-logs/20071213-summary.txt
+\end{itemize}
+
+What needs to happen for us to make a decision?
+
+Last week, we agreed to just add moderators to \#gentoo-dev and the
+gentoo-dev list. Other places with their own moderation should enforce
+the CoC themselves. We also agreed that moderation must be handed over to
+devrel or userrel after 2 days.
+
+Ferris asked some questions:
+\begin{enumerate}
+\item Do we have an implementation schedule? ;
+\item Have we identified some warm bodies for it?;
+\item Most devrel requests seem really to relate to CoC
+violations. Would
+ you like us to bounce those to the CoC people, process them
+using CoC
+ rules, or keep doing what we are doing now (generally, close
+them with a
+ note explaining why or mediate them)? (I'm talking about the
+"He's
+ being rude/sarcastic/disrespectful" sorts of things which really
+need to
+ be processed immediately and merit a warning or brief suspension
+if
+ anything.)
+\end{enumerate}
+
+
+ Council members agreed on the direction, dberkholz will provide
+ additional details on -council ML
+
+
+
+
+\agendaitem{Document of being an active developer}
+\index{developer certificate}
+
+Araujo raised that he needs some kind of written document of being an
+ active developer. Argument being that mentioning in CV in his
+ environment is only accepted if there is some kind of proof.
+ Our trustee grant deferred it back to council+infra as Foundation only
+ handles IP, but suggested it could be some kind of generated document.
+
+
+
+Suggested option: Log in to dev.g.o and automatically generate there signed by
+ infra-maintained key, put userinfo.xml website in the doc as
+ reference.
+
+ dberkholz and araujo will look into a scribus based template.
+ devrel will have to generate a signing key for these purposes.
diff --git a/decisions/summary-20080214.tex b/decisions/summary-20080214.tex
new file mode 100644
index 0000000..7cd4fd4
--- /dev/null
+++ b/decisions/summary-20080214.tex
@@ -0,0 +1,109 @@
+
+\summary{2008}{2}{14}
+
+
+\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.
+
+
+
+\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.
+
+ 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.
+
+ Template file on hold pending format decision from script
+
+ Any news from devrel on key? dberkholz pinged 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.
+
+
+\agendaitem{GLEP 54: scm package version suffix}
+\index{GLEP!54}\index{scm suffix}
+
+
+ Last month:
+ Sent back to -dev. peper was to repost it.
+
+ Updates:
+ No discussion on -dev. No resubmission to council.
+
+
+\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.
+
+
+\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}
+\index{metadata.xml}\index{upstream tags}
+
+References:
+\begin{itemize}
+ \item
+ \glep{46}
+ \item
+ \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?
+
+ Once those questions are resolved, it will be finalized.
+
+
+\agendaitem{EAPI=1: Where is the approved specification?}
+\index{EAPI!1}\index{EAPI!0}
+
+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.
+
+ 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.
+
+ Halcy0n will give us an update at the next council meeting.
diff --git a/decisions/summary-20080313.tex b/decisions/summary-20080313.tex
new file mode 100644
index 0000000..d4478ec
--- /dev/null
+++ b/decisions/summary-20080313.tex
@@ -0,0 +1,89 @@
+
+\summary{2008}{3}{13}
+
+
+
+\agendaitem{Document of being an active developer}
+\index{developer certificate}
+
+No updates
+
+
+\agendaitem{Slacker arches}
+\index{arches!slacking}
+
+2 months ago:
+vapier will work on rich0's suggestion and repost it for
+discussion on -dev ML
+
+Updates:
+vapier said he was going to work on it this weekend.
+
+
+\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}
+
+Reference: \glep{46}
+
+Last month: Caveat on approval about allowed protocols
+
+Updates: No updates; no authors present
+
+
+\agendaitem{EAPI 0}
+\index{EAPI!0}
+
+Last month: Halcy0n was working on it
+
+Updates:
+ Ciaran has been contributing and has committed quite a few
+ things. Halcy0n hopes to work on it in the next couple of weeks.
+ He informed us that Ciaran said when he finishes the environment
+ tables, EAPI=0 is probably a week of solid work from having a
+ draft for review.
+
+ Halcy0n wasn't around when the topic came up, so the above info
+ was from after the meeting.
+
+
+\agendaitem{Google Summer of Code}
+\index{GSoC}
+
+Should Gentoo devs be allowed to participate?
+
+GNOME's policy is that they favor people who haven't contributed
+ before, but they will accept great projects from contributors.
+
+Decision: Council members will become additional SoC admins, and
+ will serve as tiebreaker votes if they aren't actively participating
+ in SoC project selection.
+
+Decision: Gentoo SoC admins will decide whether non-contributors
+ should be favored over contributors.
+
+
+
+\agendaitem{Package maintainers}
+\index{proxy-maintainers}
+
+Decision: We'll promote proxy-maintainers more -- GMN, website, etc.
+
+
+
+\agendaitem{amd64 arch team and big bug list}
+\index{arches!slacking}\index{arch!amd64}
+
+ kingtaco (mike) said it's hard to keep people interested in
+ keywording.
+
+ Anyone interested has had permission to keyword and stabilize
+ non-system packages since 2007.1 (see -core email from kingtaco with
+ subject "AMD64 keywording").
+
+
+\agendaitem{Open floor}
+\index{required attendees}
+
+ A list of required attendees would be useful. dberkholz will start
+ creating the agenda along with this list in advance of the meeting.
+ Posting the agenda on a google calendar, along with other stuff,
+ could help. flameeyes is starting to work with the PR team on this.
diff --git a/decisions/summary-20080410.tex b/decisions/summary-20080410.tex
new file mode 100644
index 0000000..86f580e
--- /dev/null
+++ b/decisions/summary-20080410.tex
@@ -0,0 +1,99 @@
+
+\summary{2008}{4}{10}
+
+
+\agendaitem{Document of being an active developer}
+\index{developer certificate}
+
+Last month: No updates
+
+Updates: No updates
+
+
+
+\agendaitem{Slacker arches}
+\index{arches!slacking}
+
+
+3 months ago:
+ vapier will work on rich0's suggestion and repost it for
+ discussion on -dev ML
+
+ Last month:
+ vapier said he was going to work on it this weekend.
+
+ Updates:
+ vapier said he's finishing it up and will have it posted tonight.
+
+
+\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}
+\index{GLEP!46!approval}
+
+Reference: \glep{46}
+
+ 2 months ago:
+ Caveat on approval about allowed protocols
+
+ Updates:
+ Restriction to http/https has been dropped as pointed out by
+ council members (amne and Flameeyes if I'm right). The point
+ for restricting the URLs to the mentioned protocols was that
+ they shouldn't link to automatically updated ressources. This
+ has been replaced by an explicit specification and a
+ recommendation that http/http should be favoured over
+ ftp/svn/gopher/etc to make the implementation for automated
+ update discovery tools easier (they should of course ignore URLs
+ they can't handle).
+
+ Approved.
+
+
+\agendaitem{Minimal activity for ebuild devs}
+\index{developers!minimal activity}
+
+Current is 1 commit every 60 days. Should it be higher?
+
+Agreement was hard to find. Some people thought it should be 1
+ commit / week, others said that people have busy lives and
+ questioned the benefits.
+
+A number of people did agree that we should trust the judgment of
+ the undertakers.
+
+dberkholz suggested that low commit rates may not maintain the
+ quality of the committer, and we should more carefully review the
+ commits of these people.
+
+Ways to track commit stats of various sorts came up, such as cia.vc
+ and ohloh. cia seems to have too much downtime to rely on. ciaranm
+ talked with ohloh people already. ohloh would require some
+ modifications to ohcount to recognize ebuilds and eclasses, and a
+ full copy of the cvs repository to start, but it seems worth
+ exploring. Betelgeuse said he would tar up a copy of the gentoo-x86
+ repo.
+
+
+\agendaitem{Initial comments on PMS}
+\index{PMS}\index{EAPI!kdebuild-1}
+
+Reference: http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git
+
+Are there any major changes needed, or just tuning details?
+
+The council voted that kdebuild-1 and other unapproved EAPIs could
+ not be in an approved PMS document. The spec isn't a place for
+ proposals or things that will never be submitted for approval by the
+ council. It's a specification, a reference of what is allowed in the
+ main tree.
+
+
+\agendaitem{Open floor}
+\index{project!devrel}
+
+ blackace asked about complaints against philantrop, eroyf, and spb.
+ vapier referred that to devrel. Betelgeuse said that there's been no
+ rejection or action on those complaints yet, and internal discussion
+ is ongoing. Philantrop complained that he hadn't heard anything
+ about complaints, and Betelgeuse said that since some members
+ already left, he didn't want to take matters into his own hands in
+ sharing private information.
diff --git a/decisions/summary-20080508.tex b/decisions/summary-20080508.tex
new file mode 100644
index 0000000..cee6619
--- /dev/null
+++ b/decisions/summary-20080508.tex
@@ -0,0 +1,180 @@
+
+\summary{2008}{5}{8}
+
+
+\agendaitem{New process}
+
+The last few meetings have dragged out for hours unnecessarily. This
+time, we tried moderating the channel during discussion of each topic,
+then temporarily opening the floor for that topic before a vote so
+anyone could contribute. Here's the time breakdown:
+
+\begin{verbatim}
+ 2000-2030: closed, 30 min
+ 2030-2046: open, 16 min
+ 2046-2056: closed, 10 min
+ 2056-2114: open, 18 min
+ 2114-2146: closed, 32 min
+ 2146-2209: open, 23 min
+ 2209-2242: closed, 33 min
+ 2242- : open floor
+\end{verbatim}
+
+Total before open floor: 105 minutes closed, 57 minutes open.
+
+Optimistically, we could have saved an hour if the channel was moderated
+throughout the meeting. That's unlikely to be the case in reality,
+because we'd be redirecting people's comments from queries into the
+channel.
+
+Should we keep it moderated until the final open floor? Should we have
+an open "backchannel"?
+
+
+\agendaitem{Document of being an active developer}
+\index{developer certificate}
+
+
+Last month:
+ No updates
+
+Updates:
+ araujo made http://dev.gentoo.org/~araujo/gcert1.pdf in Scribus.
+ He'd like to ask for approval of this design and discuss the
+ script, in particular its infrastructure requirements.
+
+Suggestions on certificate content:
+\begin{itemize}
+\item Add title to the top: "Developer Certification"
+\item Add devrel contact info (general devrel email address)
+\item Add link to devrel userinfo page
+\item Add start and end dates to devrel retired developers
+page
+\item Add a sentence saying e.g. "This certifies that XXX was
+a
+ Gentoo developer from START_DATE to TODAY_DATE." The point
+ is to avoid implying that the developer is certified
+ forever, or will be a developer in the future.
+
+The information should be gotten from LDAP, for example using
+ python-ldap. Could base this script on devrel's slacker script.
+
+It's unsure how signatures are going to happen, but one option
+ is to keep a GPG-encrypted image of a signature and decrypt it
+ on-demand for certificate creation. This should be discussed
+ with the person doing the signing.
+\end{itemize}
+
+\agendaitem{Slacker arches}
+\index{arches!slacking}
+
+4 months ago: vapier will work on rich0's suggestion and repost it for
+discussion on -dev ML
+
+2 months ago: vapier said he was going to work on it that weekend.
+
+Last month: No updates
+
+Updates: ---
+
+
+\agendaitem{When are ChangeLog entries required?}
+\index{ChangeLog}
+
+This question mainly relates to arch stabilizations.
+
+The consensus was that ChangeLog entries even for arch
+ stabilizations provide valuable information that is unique without
+ network access and more accessible than CVS logs even with network
+ access.
+
+So, Always required. If you aren't making them now, fix
+your script to call echangelog.
+
+Some people were curious what proportion of space ChangeLogs take in
+ the tree, but most people didn't think that was relevant.
+
+welp suggested making a changelog message part of repoman commit.
+
+It would be helpful for the QA team to help with checking for and
+ enforcing ChangeLog messages. If that doesn't help matters, the
+ council may have to take action.
+
+
+\agendaitem{Can the council help fewer bugs get ignored by arm/sh/s390 teams?}
+\index{arch!arm}\index{arch!sh}\index{arch!s390}
+
+The work happens, but Mart says it's not communicated to anyone and
+ has no relationship to whether bugs are open.
+
+We need to understand the workflow of undermanned arch teams and see
+ whether there's anything we can help improve.
+
+Possibly improving recuitment -- add a good, motivating
+ staffing-needs entry.
+
+
+\agendaitem{PMS: Are versions allowed to have more than 8 digits?}
+
+References:
+\begin{itemize}
+ \item
+ \agoref{gentoo-dev}{db2f5c09c2c0c8b042ca3d0dcec7cdaf}
+ \item
+ \bug{188449}
+\end{itemize}
+
+What do various PMs/tools support? Portage, Pkgcore, Paludis all
+ handle >8. portage-utils does not but could be fixed to use longs
+ instead of ints, with some loss of performance (magnitude unclear).
+
+versionator.eclass also needs fixing for >8 digits.
+
+Apparently [ ]-style tests break with large numbers, but [[ ]]
+ works. Have to be careful which tests are getting used anywhere
+ large versions are compared.
+
+The council generally favored allowing versions to have <=18 digits.
+ This allows them to fit into 64 bits (18 signed digits or 19
+ unsigned) and gives them an upper bound, which some implementations
+ of version parsing could find useful.
+
+We voted to do more research and testing, specifically to ask the
+ package maintainers with extremely long PVs whether they were needed
+ and to test the impact of extending versionator.eclass. The involved
+ packages:
+
+\begin{verbatim}
+ sys-process/fuser-bsd
+ sys-apps/net-tools
+ sys-apps/gradm
+ net-im/ntame
+ media-video/captury
+ media-libs/libcaptury
+ media-libs/capseo
+ sys-block/btrace
+ www-apache/mod_depends
+ net-wireless/rt2500
+ sys-fs/unionfs
+\end{verbatim}
+
+
+\agendaitem{Enforced retirement}
+\index{retirement!enforced}\index{project!devrel}
+
+The meeting had already gone 2.5 hours and we were short multiple
+ council members because of the late hour in their timezone, or
+ broken hardware in the case of jokey. Because of the urgency of
+ getting this resolved, we decided it couldn't wait for next month's
+ meeting and scheduled a special session for next week at the same
+ time.
+
+
+\agendaitem{Open floor}
+\index{retirement!appeal}
+
+ Some people thought that we were going to make a final decision on
+ the above appeals today, because the agenda was insufficiently clear
+ on that. That was not the case. What we intended to do was explain
+ why we can take the appeal and then figure out the process for it
+ because we haven't done any appeals before.
diff --git a/decisions/summary-20080515.tex b/decisions/summary-20080515.tex
new file mode 100644
index 0000000..a38f20a
--- /dev/null
+++ b/decisions/summary-20080515.tex
@@ -0,0 +1,4 @@
+\summary{2008}{5}{15}
+
+The meeting was attended by less than 50\% of council members.
+No topics of the agenda were discussed and no votes were taken.