Index 2007/6 to 2007/11

8 files changed, 353 insertions, 2 deletions

diff --git a/decisions/decisions.but b/decisions/decisions.but
index 30b5096..30c4c53 100644
--- a/decisions/decisions.but
+++ b/decisions/decisions.but
@@ -4,14 +4,24 @@ Native Portage Multilib Support
 Document howto configure MTA and MUA to use SPF effectively
 154595
 Document how to change reply-to headers on gentoo lists
+174405
+[EAPI-1] add support for SLOT depends
 174407
 [Future EAPI] add support for dynamic SLOTS
+174410
+[EAPI-1] support for IUSE defaults
 174536
 [Future EAPI] "Package names" spec inconsistent
 176467
 [Future EAPI] Limit values in $USE to ones in $IUSE
 177966
 Clarify Foundation page on external entities
+179380
+[EAPI-1] add ECONF_SOURCE support to the default src_compile() function
+187971
+Gentoo Website Command Injection Issue
+194876
+EAPI-1 tracker
 211529
 [Future EAPI] have econf run ./configure with --disable-dependency-tracking
 21310
diff --git a/decisions/decisions.bux b/decisions/decisions.bux
index 49ec564..953da8c 100644
--- a/decisions/decisions.bux
+++ b/decisions/decisions.bux
@@ -4,8 +4,16 @@ GLEP!27;UIDs
 reply-to header;mailing lists;reply-to-list
 154594
 SPF;dev.gentoo.org
+174405
+SLOT;dependencies!slot depends
 174407
 dynamic SLOT;SLOT!dynamic
+174410
+IUSE defaults
+179380
+ECONF_SOURCE
+194876
+EAPI!1
 211529
 --disable-dependency-tracking;src_configure;econf
 234706
diff --git a/decisions/decisions.tex b/decisions/decisions.tex
index 36c6039..b241f70 100644
--- a/decisions/decisions.tex
+++ b/decisions/decisions.tex
@@ -167,8 +167,11 @@ All summaries have been added here.
 
 \chapter{Meeting summaries 2006/07}
 
-Council members: Flameeyes (until 2/2007), KingTaco, kloeri, Kugelfang, 
-robbat2, uberlord (starting 3/2007), vapier, wolf31o2 
+Council members: flameeyes (until 2/2007), jaervosz (since 6/2007), kingtaco, 
+kloeri (until 5/2007), kugelfang, robbat2, uberlord (starting 3/2007), vapier, 
+wolf31o2 
+
+All summaries have been added here.
 
 \include{summary-20060914}
 \include{summary-20061019}
@@ -181,9 +184,18 @@ robbat2, uberlord (starting 3/2007), vapier, wolf31o2
 \include{summary-20070412}
 \include{summary-20070424}
 \include{summary-20070510}
+\include{summary-20070614}
+\include{summary-20070712}
+\include{summary-20070816}
 
 \chapter{Meeting summaries 2007/08}
 
+Council members: amne, betelgeuse, dberkholz, flameeyes, jokey 
+(starting 11/2007), lu_zero, uberlord (until 10/2007), vapier 
+
+\include{summary-20071011}
+\include{summary-20071108}
+
 \chapter{Meeting summaries 2008/09}
 
 \chapter{Meeting summaries 2009/10}
diff --git a/decisions/summary-20070614.tex b/decisions/summary-20070614.tex
new file mode 100644
index 0000000..dab2684
--- /dev/null
+++ b/decisions/summary-20070614.tex
@@ -0,0 +1,53 @@
+
+\summary{2007}{6}{14}
+
+
+\agendaitem{Council membership}
+\index{council!membership}
+
+Council vote approves jaervosz replacing kloeri.
+
+
+\agendaitem{Using Git to access the PMS repo}
+\index{packages!dev-vcs/git}\index{PMS}
+
+robbat2 to write a doc on using Git to access the PMS repo (which presently
+  just mirrors the SVN). spb to bug robbat2 if he doesn't get said doc.
+
+
+\agendaitem{Handling of mailing lists, including proctors and moderation}
+\index{mailing lists}\index{mailing list!gentoo-project}
+\index{mailig list!gentoo-dev}\index{project!proctors}
+\index{Code of Conduct}\index{Freenode Catalyst}
+
+Large discussion about handling of mailing lists, including proctors and
+moderation. Vote is proposed for:
+\begin{enumerate}
+ \item 
+ Having a seperate unmoderated -project (in the fashion of Debian's 
+ -project). 
+ \item
+ -dev becoming moderated for non-@gentoo, as well as any @gentoo that with
+  to be moderated, or have flamish tendancies.
+ \item
+ Moderators are a seperate and more open group from proctors. Mainly devs,
+  and are expected to show good judgement (see Catalyst item).
+\end{enumerate}
+
+Decision is made to send the above to -dev list for discussion, and have an
+  intermediate meeting in 2 weeks. Non-binding vote by council gets 4 yes
+  votes and one no.
+  
+Musikc had sent an email to council about the proctors process and the CoC.
+  This leads into a discussion of the FreeNode Catalyst system, which was a
+  partial basis for the CoC. Rough agreement that in an ideal work, all
+  developers should act as positive catalysts, but this is a lot harder than
+  it seems.
+\begin{enumerate}
+ \item 
+ The moderation discussion needs to be integrated into musikc's document.
+ \item
+ More catalyst material into the CoC per Proctor's revisions.
+ \item
+ Musikc needs to send her mail to the lists in a week.
+\end{enumerate}
diff --git a/decisions/summary-20070712.tex b/decisions/summary-20070712.tex
new file mode 100644
index 0000000..9850040
--- /dev/null
+++ b/decisions/summary-20070712.tex
@@ -0,0 +1,41 @@
+
+\summary{2007}{7}{12}
+
+
+\agendaitem{Lack of agenda}
+
+Council noted the lack of pre-prepared agenda items, and tried to see what
+  outsanding issues from previous months were still running. jaervosz and
+  vapier were marked as slackers for non-attendance.
+
+
+\agendaitem{Proctors proposal}
+\index{project!proctors}
+
+On the Musikc's proposal from the June meeting that was to be assembled and
+  discussed by proctors, no progress had been made due to real-life issues and
+  timing conflicts. The previously existing document was not agreed upon by
+  existing proctors either.
+
+\agendaitem{Moderation of -project}
+\index{mailing list!gentoo-project}
+
+The issues of -project, and moderation of email were brought up the
+  counterproposal to the proctors, as they had been discussed in the June 2007
+  meeting.
+
+\agendaitem{Proctors project}
+\index{project!proctors!dissolution}
+
+Kingtaco wanted a vote to cancel the proctors. robbat2 wanted them to just
+  die quietly if no material was forthcoming. Others called for a definate
+  stand rather than the "die quietly". All 5 attending council members voted
+  in favour of dropping the proctors.
+
+More discussion was put into the -project and moderation issue and the state
+  of proctors.
+
+\agendaitem{Council work}
+
+nightmorph aske the council questions about how much time council work takes
+  up and the like.
diff --git a/decisions/summary-20070816.tex b/decisions/summary-20070816.tex
new file mode 100644
index 0000000..764b481
--- /dev/null
+++ b/decisions/summary-20070816.tex
@@ -0,0 +1,43 @@
+
+\summary{2007}{8}{16}
+
+\agendaitem{Transition to new Council}
+\index{council!transition}
+
+Clarification on the procedural side of things with transition to new Council:
+\begin{itemize}
+ \item 
+ Nominations will always be in the month of July
+ \item
+ Voting will always be in the month of August
+ \item
+ August will always be the last month for a new Council
+ \item
+ New Council will always take over in September
+\end{itemize}
+Delays in misc aspects (like setting up infra to allow voting) will 
+merely
+	delay the start of the new Council and the end of the old Council.  Once
+	the new Council is voted in and takes over, it will still face the end
+	date of August.  This is to avoid ugly sliding windows over time of "Council
+	members serve for a year, but they started late on date XXX so we have to
+	delay the start of the next Council by XXX days blah blah blah".
+
+  Since this year voting ends after the 2nd Thursday but before the 3rd
+  Thursday in September, we'll simply delay the September meeting until the 3rd
+  Thursday so that the new Council gets to sit out 12 meetings.
+
+
+\agendaitem{Mailing list changes (wrt new gentoo-dev-announce)}
+\index{mailing list!gentoo-dev-announce}\index{mailing list!gentoo-dev}
+
+gentoo-dev-announce is
+  no longer auto cross-posted to gentoo-dev.  reply munging is no longer in
+  effect.  devs can manually cross-post and take discussion to gentoo-dev.
+
+
+\agendaitem{PMS maintenance}
+\index{PMS}
+
+PMS has been moved over to Gentoo infra and will be maintained by the portage
+  team and any other interested Gentoo parties.
diff --git a/decisions/summary-20071011.tex b/decisions/summary-20071011.tex
new file mode 100644
index 0000000..b03e786
--- /dev/null
+++ b/decisions/summary-20071011.tex
@@ -0,0 +1,83 @@
+
+\summary{2007}{10}{11}
+
+
+\agendaitem{Code of Conduct}
+\index{Code of Conduct}\index{project!userrel}\index{project!devrel}
+
+"What are not clear are (1) whether the Code of Conduct is in effect; (2)
+if so, how we enforce it."
+
+The CoC is in effect, but it needs a new enforcement section since the 
+proctors were disbanded. The council is sending discussion of this to 
+the gentoo-project list, to come up with proposals for three points:
+\begin{itemize}
+ \item 
+ who enforces it
+ \begin{itemize}
+  \item musikc said devrel could
+  \item tsunam said userrel could
+ \end{itemize}
+ \item
+ how to enforce it
+ \begin{itemize}
+  \item whether it's active or passive enforcement
+  \item which actions are appropriate
+ \end{itemize}
+\end{itemize}
+
+If the -project list does not come up with a draft, dberkholz will 
+write one based on -project discussion to vote upon at the November 
+council meeting.
+
+
+\agendaitem{packages.gentoo.org}
+\index{packages.gentoo.org}
+
+Reference: \bug{187971}, 
+	comment \#86 from marduk on rewrite, 
+	comment \#90 re jokey's rewrite (comment \#85)
+
+The infrastructure team will decide the future of packages.gentoo.org.
+
+KingTaco informed us that the current code will probably not return. 
+Alternatives include:
+\begin{itemize}
+ \item 
+ \url{http://packages.gentooext.net/} (written by jokey)
+ \item
+ \url{http://spaceparanoids.org/gentoo/gpnl/} (written by beandog)
+ \item
+ \url{http://gentoo-portage.com/}
+\end{itemize}
+
+Until we get a replacement, packages.gentoo.org will link to 
+alternatives. It now links to a forums thread describing them.
+
+
+\agendaitem{GLEP 39: project RFC addition}
+\index{GLEP!39}
+
+We will amend the GLEP rather than writing a new one, and a note will 
+be added saying the GLEP was amended.
+
+
+\agendaitem{When does the new council term end?}
+\index{council!term}
+
+Voting will always take place the same month, as mentioned in 
+http://thread.gmane.org/gmane.linux.gentoo.devel/52081/focus=52143 (broken 
+link).
+
+If the new council is delayed, it gets a slightly shortened term.
+
+
+\agendaitem{Open floor}
+\index{PMS}
+
+Where is the PMS repo?
+	--- robbat2 has imported it. It's in git. Need to ping him for 
+	details.
+
+The channel was not moderated during the meeting and it went well. 
+Let's try that again next time.
diff --git a/decisions/summary-20071108.tex b/decisions/summary-20071108.tex
new file mode 100644
index 0000000..8d34a84
--- /dev/null
+++ b/decisions/summary-20071108.tex
@@ -0,0 +1,101 @@
+
+\summary{2007}{11}{8}
+
+Agenda: http://thread.gmane.org/gmane.linux.gentoo.devel/52772 (dead link)
+
+Also continuing discussion on CoC enforcement. Proposal:
+http://thread.gmane.org/gmane.linux.gentoo.council/82 (dead link)
+
+
+
+\agendaitem{Empty council slot: vote for Jokey to happen on gentoo-council list}
+
+Jokey is the candidate to replace uberlord, and it requires a 
+unanimous council vote. Since not all council members are present, 
+we'll do this vote on the gentoo-council list. All 6 present council 
+members supported Jokey's addition.
+
+
+\agendaitem{Daylight savings change: no slacker marks}
+
+In the US and Europe, 2000 UTC shifted by an hour in local time. The 
+email announcement was wrong, so we will not give slacker marks to the 
+two absent council members.
+
+vapier needs to fix his script before the next announcement.
+
+
+\agendaitem{EAPI=1 approved for use in the main tree}
+\index{EAPI!1}
+
+Stable portage version 2.1.3.12 supports EAPI=1. It's now officially OK 
+to start using it in the main tree. From the ebuild ChangeLog for 
+portage:
+
+\begin{quote}
+  This release is the first to have support for EAPI-1 (\bug{194876}), which 
+  includes SLOT dependencies (\bug{174405}), IUSE defaults (\bug{174410}), and 
+  ECONF_SOURCE support for the default src_compile function (\bug{179380}). 
+  Package maintainers should carefully consider the backward compatibility 
+  consequences before defining EAPI="1" in any ebuilds, especially if
+  other packages depend on those ebuilds. See the ebuild(5) and emerge(1) 
+  manual pages for EAPI related documentation.
+\end{quote}
+
+EAPI=1 features are documented in PMS as well as the man pages, but they 
+are not yet documented in the devmanual or the dev handbook.
+
+
+\agendaitem{Code of Conduct enforcement proposal: generally positive feedback}
+\index{Code of Conduct}
+
+Reference: http://thread.gmane.org/gmane.linux.gentoo.council/82 (dead link)
+
+dberkholz sent out a proposal this morning, so we just discussed it 
+today instead of voting. Initial feedback from council members was 
+positive. Some concerns came up on the list about time zone differences 
+and coverage, which were brought up again during the meeting.
+
+People generally agreed that although the environment is better now, it 
+hasn't been before and won't always be good.
+
+lu_zero brought up the point that since things are fairly good now, we 
+don't need to rush through this process and we can take our time and do 
+things right.
+
+Council support for the team's actions should not be as controversial 
+with the requirement that all actions be private.
+
+The team will need to create the tools to deal with the actions it needs 
+to take (short-term moderation on IRC, mailing lists, and Bugzilla). 
+This could happen during the initial training period suggested on the 
+gentoo-council list.
+
+If there's already existing moderation somewhere (for example many of 
+the \#gentoo-* IRC channels or the forums), the team will first liaise 
+with them rather than preempt them. All official Gentoo forums must 
+adhere to the CoC, however; having their own moderation does not exclude 
+them from following Gentoo's standards as a whole.
+
+The expectation is that successive actions against the same person will 
+increase in length, eventually reaching the 3-day cutoff that requires 
+council approval and forwarding to devrel/userrel. The idea is that if 
+someone keeps violating the CoC after a given length of moderation, it 
+apparently wasn't enough so it shouldn't be repeated.
+
+Next month, we will vote on a concrete proposal.
+
+
+\agendaitem{Baselayout-2: uberlord will continue to maintain it}
+\index{package!sys-apps/baselayout}
+
+lu_zero asked whether we had anything to do about baselayout-2 since 
+uberlord resigned. He's continuing to maintain it in a git repository 
+and will remain upstream for it. More details will emerge over time.
+
+kingtaco raised the question of trusting external releases and hosts. 
+Some responses suggested that using git may prevent the malicious host, 
+because of the possibility of GPG-signed tags. He mentioned the 
+possibility of the infra team hosting Gentoo-critical repositories with 
+access by non-Gentoo developers. It's just an idea at this point, but 
+he's going to talk to the rest of the infra team.