diff options
author | Andreas K. Hüttel <dilfridge@gentoo.org> | 2017-04-16 17:46:45 +0200 |
---|---|---|
committer | Andreas K. Hüttel <dilfridge@gentoo.org> | 2017-04-16 17:46:45 +0200 |
commit | 86cf0692d4f8f5e0934fa87df6f3ec9cedf078b9 (patch) | |
tree | d52a55666d9dfb1cd0632c2527cc8f8cc819a486 | |
parent | Improve up to 12/2007 (diff) | |
download | council-86cf0692d4f8f5e0934fa87df6f3ec9cedf078b9.tar.gz council-86cf0692d4f8f5e0934fa87df6f3ec9cedf078b9.tar.bz2 council-86cf0692d4f8f5e0934fa87df6f3ec9cedf078b9.zip |
Improve 1/2008
-rw-r--r-- | decisions/decisions.ded | 17 | ||||
-rw-r--r-- | decisions/decisions.gld | 4 | ||||
-rw-r--r-- | decisions/decisions.mlf | 6 | ||||
-rw-r--r-- | decisions/decisions.mls | 6 | ||||
-rw-r--r-- | decisions/decisions.mlt | 6 | ||||
-rw-r--r-- | decisions/summary-20080110.tex | 161 |
6 files changed, 116 insertions, 84 deletions
diff --git a/decisions/decisions.ded b/decisions/decisions.ded index 311ee83..af9483a 100644 --- a/decisions/decisions.ded +++ b/decisions/decisions.ded @@ -4,6 +4,9 @@ Aron Griffis amne Wernfried Haas +araujo +Luis Francisco Araujo + azarah Martin Schlemmer @@ -13,6 +16,9 @@ Steve Dibb betelgeuse Petteri Räty https://wiki.gentoo.org/wiki/User:Betelgeuse +caleb +Caleb Tennis + ciaranm Ciaran McCreesh @@ -25,6 +31,9 @@ Daniel Drake flameeyes Diego Elio Pettenò https://wiki.gentoo.org/wiki/User:Flameeyes +fmccor +Ferris McCormick + g2boojum Grant Goodyear @@ -55,9 +64,12 @@ Thierry Carrez kugelfang Danny van Dyk +kumba +Joshua Kinard +https://wiki.gentoo.org/wiki/User:Kumba lu_zero Luca Barbato - +https://wiki.gentoo.org/wiki/User:Lu\%20zero musikc Christina Gianelloni @@ -70,6 +82,9 @@ Patrick Lauer ramereth Lance Albertson +rich0 +Richard Freeman + robbat2 Robin H. Johnson diff --git a/decisions/decisions.gld b/decisions/decisions.gld index 8f2a068..d577a69 100644 --- a/decisions/decisions.gld +++ b/decisions/decisions.gld @@ -69,11 +69,11 @@ keywords;project!prefix 54 scm package version suffix Deferred -scm version suffix +scm version suffix;live suffix;ebuilds!live;packages!build from scm 55 Use EAPI-suffixed ebuilds (.ebuild-EAPI) Rejected - +EAPI suffix 57 Security of distribution of Gentoo software - Overview Final diff --git a/decisions/decisions.mlf b/decisions/decisions.mlf index 7108d59..f968835 100644 --- a/decisions/decisions.mlf +++ b/decisions/decisions.mlf @@ -118,6 +118,8 @@ Denis Dupeyron Rich Freeman 60481da5b44b778ca5c4405da28f61c7:gentoo-project Michał Górny +6196880b1c05412836850b2476aacdc1:gentoo-dev +Kumba 62b5df924d6e9e74c94149e7e7f17d23:gentoo-dev Fabian Groffen 637270936c9f07e3bd2f10ee45264a42:gentoo-project @@ -142,6 +144,8 @@ Alexandre Buisse Mike Frysinger 69ed522b3b53de90e616267a77441012:gentoo-project Michał Górny +6a77b647228fc497a720151fa8a6e54c:gentoo-dev +Mike Frysinger 6cad9409772fa44415e84005ff922145:gentoo-council Ulrich Mueller 6db80f9a66d80a3c4ec0480690ce77e4:gentoo-project @@ -244,6 +248,8 @@ bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project Ulrich Mueller bec5db8373fca0271fcadf0cd55724e8:gentoo-dev Arfrever Frehtes Taifersar Arahesis +c32c17977368bc02019bc8318df40dfc:gentoo-dev +Caleb Tennis c60f7c1514f175b8cc0d376ae9373e17:gentoo-project Ulrich Mueller c6e4ba8293f50c1e0444e67d59cf85ea:gentoo-dev diff --git a/decisions/decisions.mls b/decisions/decisions.mls index 4c3eacf..c5c52a3 100644 --- a/decisions/decisions.mls +++ b/decisions/decisions.mls @@ -118,6 +118,8 @@ Re: [gentoo-project] Call for agenda items -- Council meeting 2012-05-08 Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 60481da5b44b778ca5c4405da28f61c7:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2016-11-13 +6196880b1c05412836850b2476aacdc1:gentoo-dev +Re: [gentoo-dev] Of Mips and Devs [Was: Monthly Gentoo Council Reminder for January] 62b5df924d6e9e74c94149e7e7f17d23:gentoo-dev Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds 637270936c9f07e3bd2f10ee45264a42:gentoo-project @@ -142,6 +144,8 @@ Re: [gentoo-dev] News item: Python ABIFLAGS rebuild needed [gentoo-dev] Monthly Gentoo Council Reminder for May 69ed522b3b53de90e616267a77441012:gentoo-project Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14 +6a77b647228fc497a720151fa8a6e54c:gentoo-dev +[gentoo-dev] Monthly Gentoo Council Reminder for January 6cad9409772fa44415e84005ff922145:gentoo-council [gentoo-council] Re: Meeting chair 6db80f9a66d80a3c4ec0480690ce77e4:gentoo-project @@ -244,6 +248,8 @@ bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-01-10 bec5db8373fca0271fcadf0cd55724e8:gentoo-dev [gentoo-dev] Summary of suggested new features in EAPI="4" +c32c17977368bc02019bc8318df40dfc:gentoo-dev +Re: [gentoo-dev] Monthly Gentoo Council Reminder for January c60f7c1514f175b8cc0d376ae9373e17:gentoo-project Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-12-13 c6e4ba8293f50c1e0444e67d59cf85ea:gentoo-dev diff --git a/decisions/decisions.mlt b/decisions/decisions.mlt index 7cf4447..9bd5199 100644 --- a/decisions/decisions.mlt +++ b/decisions/decisions.mlt @@ -118,6 +118,8 @@ Sun, 16 May 2010 01:11:34 Sun, 30 Mar 2014 14:07:52 60481da5b44b778ca5c4405da28f61c7:gentoo-project Mon, 31 Oct 2016 07:32:03 +6196880b1c05412836850b2476aacdc1:gentoo-dev +Thu, 10 Jan 2008 04:07:00 62b5df924d6e9e74c94149e7e7f17d23:gentoo-dev Thu, 26 Nov 2009 13:44:16 637270936c9f07e3bd2f10ee45264a42:gentoo-project @@ -142,6 +144,8 @@ Tue, 10 Apr 2007 19:36:37 Sun, 07 May 2006 23:37:06 69ed522b3b53de90e616267a77441012:gentoo-project Fri, 12 Feb 2016 22:22:24 +6a77b647228fc497a720151fa8a6e54c:gentoo-dev +Tue, 01 Jan 2008 10:32:51 6cad9409772fa44415e84005ff922145:gentoo-council Sat, 16 Jul 2011 10:03:40 6db80f9a66d80a3c4ec0480690ce77e4:gentoo-project @@ -244,6 +248,8 @@ bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project Sun, 27 Dec 2015 18:03:56 bec5db8373fca0271fcadf0cd55724e8:gentoo-dev Sat, 18 Dec 2010 01:45:51 +c32c17977368bc02019bc8318df40dfc:gentoo-dev +Thu, 03 Jan 2008 13:06:46 c60f7c1514f175b8cc0d376ae9373e17:gentoo-project Sun, 29 Nov 2015 16:08:38 c6e4ba8293f50c1e0444e67d59cf85ea:gentoo-dev diff --git a/decisions/summary-20080110.tex b/decisions/summary-20080110.tex index dd5d36d..7f296f7 100644 --- a/decisions/summary-20080110.tex +++ b/decisions/summary-20080110.tex @@ -1,142 +1,141 @@ \summary{2008}{1}{10} +Agenda call: \agoref{gentoo-dev}{6a77b647228fc497a720151fa8a6e54c} + \agendaitem{GLEP 54: scm package version suffix} -\index{scm version suffix}\index{CPV} Reference: \glep{54} -Comment from portage maintainer: +The proposed GLEP was discussed. Comments from portage maintainer \dev{genone} +were: \begin{itemize} \item - no statement about compatibility/implementation plans + There is no statement about compatibility/implementation plans in the GLEP. + \item + While a distinction between CPV and atom may not be technically required, it + might be useful to have \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} + (minor) If the version part is optional there could be some complications. \end{itemize} -So is this something we'd like to have? +So is this something we'd like to have (before we decide on details)? The -9999 +version usage in the tree was started since there was no progress on \bug{9202}. -Other ideas that came up during discussion: +Other (implementation) ideas that came up during discussion: \begin{itemize} \item - -scm or _scm ? + Should we use a -scm or _scm suffix? \item - handling as (-|_pre)9999) versions per definition + Alternatively, handling (-$\vert$_pre)9999) as scm versions per definition? \item - implement as dynamic package sets + Implement this 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. +The topic was pushed back to the gentoo-dev mailing list as there are too many +unresolved questions at the moment. \dev{peper} is given the task to repost it +and expand on usefulness / use cases as well as on compatibility issues. \agendaitem{GLEP 55: Use EAPI-suffixed ebuilds (.ebuild-EAPI)} Reference: \glep{55} -Agreement on eapi subdirectories are not feasible. +This resulted in a lengthy discussion on technical advantages and +disadvantages, including using a pre-sourcing EAPI as mask before providing the +final EAPI of an ebuild via sourcing, or converting the EAPI assignment to a +function call and using a repository bashrc for backwards +compatibility.\footnote{The whole proposal was +initially kicked off for allowing eclasses to use a different EAPI from an +ebuild.} There was agreement that 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. +The topic was pushed back to the gentoo-dev mailing list as there are too many +unresolved questions at the moment. \agendaitem{Slacker arches} -\index{arches!slacking} +\index{arches!slacking}\index{arch!mips} References: \begin{itemize} \item - Calebs post: - http://article.gmane.org/gmane.linux.gentoo.devel/53933 (dead link) + \dev{caleb}'s post: http://article.gmane.org/gmane.linux.gentoo.devel/53933 + (dead link)\footnote{Likely the + \agoref{gentoo-dev}{c32c17977368bc02019bc8318df40dfc}} \item - Kumba's comment on mips status: - http://article.gmane.org/gmane.linux.gentoo.devel/54168 (dead link) + \dev{kumba}'s comment on mips status: + http://article.gmane.org/gmane.linux.gentoo.devel/54168 (dead + link)\footnote{Likely the + \agoref{gentoo-dev}{6196880b1c05412836850b2476aacdc1}} \item - Rich0's proposal: - http://article.gmane.org/gmane.linux.gentoo.devel/54103 (dead link) + \dev{rich0}'s proposal: http://article.gmane.org/gmane.linux.gentoo.devel/54103 + (dead link)\footnote{Can't find it in the archive. It seems to have involved + timeouts of some sorts.} \end{itemize} -vapier will work on rich0's suggestion and repost it for discussion on - -dev ML +\dev{vapier} will work on \dev{rich0}'s suggestion and repost it for discussion +on the gentoo-dev mailing list. \agendaitem{Code of Conduct} -\index{Code of Conduct!enforcement} +\index{Code of Conduct!enforcement}\index{project!devrel} +\index{project!userrel} References: \begin{itemize} \item - http://thread.gmane.org/gmane.linux.gentoo.council/82 (dead link) + \agoref{gentoo-council}{cbfe572adb090dfba1cc004b1cca6979} \item - http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt + November 2007 Council meeting \item - http://www.gentoo.org/proj/en/council/meeting-logs/20071213-summary.txt + December 2007 Council meeting \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. +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: +\dev{fmccor} 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.) +\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.)\footnote{This question is +not in the meeting log.} \end{enumerate} - - Council members agreed on the direction, dberkholz will provide - additional details on -council ML - - +Council members agreed on the direction; \dev{dberkholz} will provide +additional details on the gentoo-council mailing list. \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. +\index{developer certificate}\index{trustees}\index{Foundation} + +\dev{araujo} raised that he needs some kind of written document of being an +active developer. His argument was that mentioning this in a CV in his +environment is only accepted if there is some kind of proof. Our trustee +\dev{grant} deferred it back to council and infra as the Foundation only handles +IP, but suggested it could be some kind of generated document. + +One suggested option how to handle this in an automated fashion would be to log +in to dev.gentoo.org and automatically generate the document there, signed by +an infra-maintained key; put userinfo.xml website in the document as reference. + +\dev{dberkholz} and \dev{araujo} will look into a scribus based template. devrel +will have to generate a signing key for these purposes.\footnote{Also having +the council sign it with, e.g., a "Gentoo Council Signing Key 2007-2008" was +discussed.} |