summaryrefslogtreecommitdiff log msg author committer range
diff options
 context: 12345678910152025303540 space: includeignore mode: unifiedssdiffstat only
Diffstat (limited to 'decisions/summary-20080612.tex')
-rw-r--r--decisions/summary-20080612.tex201
1 files changed, 80 insertions, 121 deletions
 diff --git a/decisions/summary-20080612.tex b/decisions/summary-20080612.texindex 499682e..9286c98 100644--- a/decisions/summary-20080612.tex+++ b/decisions/summary-20080612.tex@@ -1,58 +1,40 @@ \summary{2008}{6}{12} +Agenda call: \agoref{gentoo-dev}{8d3e2ff5235b214f77d234449cdd5897}++Agenda announcement: \agoref{gentoo-dev}{868e239918e9bf80524415d5d12e2493}+ \agendaitem{Moderation} \index{council!meeting!channel mode} -Modes +qnm, with voice for people involved in discussions?--If it becomes necessary, we'll do it. Leave channel open till then.+Shall we use channel modes +qnm, with voice for people involved in discussions?+This means +\begin{itemize}+ \item + +m - Moderated - People who don't have voices (+v) can't send + messages to the channel.+ \item+ +n - No external messages - With this mode, no one can send messages + to the channel without even being joined.+ \item + +z - Relaxed moderation - When +z is set each message that would be + blocked by +m is sent to all the users who are currently operator.+\end{itemize}+Concusion --- if it becomes necessary, we'll do it. We leave the channel open +until then. \agendaitem{Time limit} \index{council!meeting!time limit} -2 hours?--Yes. We'll move any topics we didn't cover to the mailing lists.----\agendaitem{Document of being an active developer}-\index{developer certificate}--Last month: Numerous suggested improvements to info on the certificate.--Preparation: araujo needs to post progress, an updated certificate and -any new requests to the gentoo-council or gentoo-project list 2+ hours -before the meeting.--Goal: Suggest changes. This should happen on-list. No discussion -expected.---\agendaitem{Slacker arches}-\index{arches!slacking}--Preparation: vapier needs to send the post 2+ hours before the meeting.--Goal: Suggest changes. This should happen on-list. No discussion -expected.---\agendaitem{Can the council help fewer bugs get ignored by arm/sh/s390 teams?}-\index{arch!arm}\index{arch!sh}\index{arch!s390}--Preparation: Someone on an undermanned arch team needs to describe their -workflow on-list 2+ hours before the meeting.--Goal: Suggest changes. This should happen on-list. No discussion -expected.+Shall we set a time limit of 2 hours for the council meeting? ---+Yes. We will move any topics we didn't cover to the mailing lists. \agendaitem{PMS: Are versions allowed to have more than 8 digits?}-\index{PMS}\index{eclass!versionator}+\index{PMS}\index{eclass!versionator}\index{version specifications} References: \begin{itemize}@@ -62,134 +44,104 @@ References: \bug{188449} \end{itemize} -Preparation: Do the package maintainers with extremely long PVs need -them? 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}--Preparation: What's the impact of extending versionator.eclass? --Goal: With data in hand, make a decision.--Decision: We didn't have all of the testing requested. We still voted to -allow versions $>8$ digits. Adding a maximum restriction is a separate -question and was not addressed -- if anyone wants this restriction, -please discuss with fellow implementors and present your consensus to -the council.---\agendaitem{How to handle appeals}-\index{council!appeal process}+The required testing was not done in the meantime. We still voted to allow +versions $>8$ digits. Adding a maximum restriction is a separate question and +was not addressed -- if anyone wants this restriction, please discuss with +fellow implementors and present your consensus to the council. -Preparation: Post to the gentoo-council mailing list 2+ hours before the -meeting with your opinion. -\agoref{gentoo-council}{d7c402fb577a3d5b1707e2bdf4b0a264}+\agendaitem{How to handle the current appeals}+\index{council!appeal process}\index{enforced retirement} -Goal: Vote on an approach that was previously posted to the list.--Decision: We approved dberkholz's proposal.+Refernce: \agoref{gentoo-council}{d7c402fb577a3d5b1707e2bdf4b0a264} +Decision: We approved \dev{dberkholz}'s proposal. \agendaitem{as-needed by default} \index{as-needed}\index{--as-needed}\index{LDFLAGS} -antarus requested that we vote on whether to add it to the default -LDFLAGS.--Preparation: Post your opinion to the -dev thread "RFC: --as-needed to -default LDFLAGS" 2+ hours before the meeting.+Reference: \agoref{gentoo-dev}{fdfd519c5372394cc7f3aacaefa387b9} -\agoref{gentoo-dev}{fdfd519c5372394cc7f3aacaefa387b9}+\dev{antarus} requested that we vote on whether to add --as-needed to the +default LDFLAGS. -Goal: Vote.+Whether this should be in default LDFLAGS or suggested in make.conf.example +wasn't clear. \dev{betelgeuse} suggested that we should know the whole tree +will build with this LDFLAGS setting (with open bugs for packages that append +-Wl,--no-as-needed) before we would consider enabling it by default. -Result: Whether this should be in default LDFLAGS or suggested in -make.conf.example wasn't clear. Betelgeuse suggested that we should know -the whole tree will build with this LDFLAGS setting (with open bugs for -packages that append -Wl,--no-as-needed) before we would consider -enabling it by default.+The current state of the tree is tracked in \bug{129413}. -Antarus will post a deployment plan to -dev for discussion. We can vote +\dev{antarus} will post a deployment plan to -dev for discussion. We can vote on it on -council as soon as it solidifies. \agendaitem{GLEP 54} \index{GLEP!54}\index{scm version suffix}\index{PV} -Preparation: Post your opinion to the -dev thread "A few questions to -our nominees" 2+ hours before the meeting.-+References: \begin{itemize}+ \item+ \glep{54} \item \agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea} \item \agoref{gentoo-dev}{05614741b3942bfdfb21fd8ebb7955e0} \end{itemize} -Goal: Vote.--Result: lu_zero posted a second plan 12 hours ago. Since it hasn't been -around long enough to get much feedback, we decided to let them develop -and see if the ideas somehow merge.+\dev{lu_zero} posted an alternative approach 12 hours ago. Since it hasn't been +around long enough to get much feedback, we decided to let the proposals +develop and see if the ideas somehow merge. \agendaitem{GLEP 55} \index{GLEP!55}\index{EAPI suffix} -Preparation: Post your opinion to the -dev thread "GLEP 55" 2+ hours -before the meeting. Let it attempt to come to a consensus before we -vote.--\agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}+References: +\begin{itemize}+ \item + \glep{55}+ \item+ \agoref{gentoo-dev}{c6e4ba8293f50c1e0444e67d59cf85ea}+\end{itemize} -Goal: Vote once the discussion's no longer clearly ongoing. We can hold -this vote on the -council mailing list instead of waiting for the next -meeting.+Let's vote once the discussion is no longer clearly ongoing. We can hold this +vote on the -council mailing list instead of waiting for the next meeting. \agendaitem{GLEP 56} \index{GLEP!56}\index{use flags}\index{metadata.xml} -Preparation: Post your opinion to the -dev thread "[GLEP56] USE flag -descriptions in metadata" 2+ hours before the meeting. Let it attempt to -come to a consensus before we vote.--\agoref{gentoo-dev}{54ee20d2b1d8122370afdd4b3d7aafc9}--Goal: Vote once the discussion's no longer clearly ongoing. We can hold -this vote on the -council mailing list instead of waiting for the next -meeting.+References:+\begin{itemize}+ \item + \glep{56}+ \item+ \agoref{gentoo-dev}{784e2b1c30bbffcaca4c27d3961de9c9}+ \item+ \agoref{gentoo-dev}{54ee20d2b1d8122370afdd4b3d7aafc9}+\end{itemize} -There is still room for improvement in this GLEP, not so much in its +There is still room for improvement in \glep{56}, not so much in its technical aspects but in the way it promotes itself, the possible -generation of legacy files, and the tools to use it.+generation of legacy files, and the tools to use it.\footnote{Note that in this +iteration the intention is that global useflag descriptions cannot be +overridden locally. This later changed.}++A final vote will be done on the -council mailing list. \agendaitem{Status of PMS} \index{PMS} -ferringb said:- I'd like the council to please discuss the current status of PMS, if +\dev{ferringb} said: +I'd like the council to please discuss the current status of PMS, if the running of it satisfys the councils requirements of a *neutral* standard, if the proposed spec actually meets said standards, and if - said spec is actually going to be approved sometimes this side of '09.--Preparation: Post your opinion to the -dev thread "One-Day Gentoo -Council Reminder for June" 2+ hours before the meeting.+ said spec is actually going to be approved sometimes this side of '09.'' +References: \begin{itemize} \item \agoref{gentoo-dev}{9e9652212b3aefe09d93fc24c6ec4cb7}@@ -199,3 +151,10 @@ Council Reminder for June" 2+ hours before the meeting. Result: This is a discussion that belongs on the mailing list. Council members should post anything they have to add by the end of the weekend.++++\vspace*{1cm}++Several further agenda items are mentioned in the official summary, but were +not actually discussed during the meeting.