diff options
| -rw-r--r-- | decisions/decisions.but | 2 | ||||
| -rw-r--r-- | decisions/decisions.mlf | 18 | ||||
| -rw-r--r-- | decisions/decisions.mls | 18 | ||||
| -rw-r--r-- | decisions/decisions.tex | 2 | ||||
| -rw-r--r-- | decisions/summary-20140311.tex | 89 | ||||
| -rw-r--r-- | decisions/summary-20140408.tex | 117 |
6 files changed, 246 insertions, 0 deletions
diff --git a/decisions/decisions.but b/decisions/decisions.but index f9a15ea..f9e6630 100644 --- a/decisions/decisions.but +++ b/decisions/decisions.but @@ -2,6 +2,8 @@ [Future EAPI] add support for dynamic SLOTS 282296 [Future EAPI] Allow directories for use.* and package.* entries in profiles +477030 +Missing summary for 20130611 council meeting 498332 Dropping stable keywords on m68k, s390, sh 503382 diff --git a/decisions/decisions.mlf b/decisions/decisions.mlf index 3fc4c34..f97750d 100644 --- a/decisions/decisions.mlf +++ b/decisions/decisions.mlf @@ -4,18 +4,28 @@ Andrew Savchenko Michał Górny 14cc0e4a82ac3fe0a6aca94aaebb981f:gentoo-project Ulrich Mueller +1c2224a5a468ff854e73fc60d25f7dce:gentoo-project +Michał Górny 1ccf2b07b96f4b164e6f69fb5d2d6cc7:gentoo-project Raymond Jennings +3a319600f3dc2dc42703a710155b2882:gentoo-project +Ulrich Mueller 3ebf4ccf0d4f27d6240888a3100d0d58:gentoo-project Dirkjan Ochtman 402eb403e0f451e7bc0525b76e9d3da2:gentoo-project Ulrich Mueller 41e09d1ddc8b30abb9f9d21d205b7b82:gentoo-dev Michał Górny +44defe3ffe0fc93ad754bd895ed0196c:gentoo-project +Chris Reffett +474fc6822dba50ccc6192c9f31d8024a:gentoo-project +Patrick Lauer 4a88db38253494c6612a29117b2b19c8:gentoo-project Matthew Thode 50dbe189dd2641d5730f08944e7fa7ce:gentoo-project Anthony G. Basile +6041b91cfa4c52c427ddbbd4f69607ff:gentoo-project +Rich Freeman 60481da5b44b778ca5c4405da28f61c7:gentoo-project Michał Górny 637270936c9f07e3bd2f10ee45264a42:gentoo-project @@ -30,10 +40,16 @@ Ulrich Mueller Michał Górny 70b28773ada15c2f4d1bcf1428ffa6a9:gentoo-project Kristian Fiskerstrand +71c67cdf620f262b4f94765360c8c8c2:gentoo-project +Tom Wijsman 87e630b9da724c5c59060608aba596a9:gentoo-dev Kristian Fiskerstrand +8fb1d8c0dd80e17cbb1fc633006f14b9:gentoo-project +Patrick Lauer 9578d459aee22ca47b1dc19149684662:gentoo-project Ulrich Mueller +9bc36a643a969e165c6f7cf228f2745c:gentoo-project +Andreas K. Huettel a08ea09c2c8e534fd9bc1146703c66ff:gentoo-dev Michał Górny a0a53d00109512557d233997699e8ce1:gentoo-project @@ -42,6 +58,8 @@ a292e9567fac838681899b50dff24cce:gentoo-project Michał Górny b2e8c759b08c29f2c4215ea74511bf1c:gentoo-project Ulrich Mueller +b59d8abb15e148b71d6e50180a2a27a7:gentoo-project +Patrick Lauer b9460b9c8d578c3498c217c17b75afd4:gentoo-dev Ulrich Mueller bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project diff --git a/decisions/decisions.mls b/decisions/decisions.mls index 7bc21f8..9e63b40 100644 --- a/decisions/decisions.mls +++ b/decisions/decisions.mls @@ -4,18 +4,28 @@ Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14 Re: [gentoo-project] Call for agenda items - Council meeting 2017-02-12 14cc0e4a82ac3fe0a6aca94aaebb981f:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25 +1c2224a5a468ff854e73fc60d25f7dce:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 1ccf2b07b96f4b164e6f69fb5d2d6cc7:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2016-11-13 +3a319600f3dc2dc42703a710155b2882:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-03-11 3ebf4ccf0d4f27d6240888a3100d0d58:gentoo-project Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14 402eb403e0f451e7bc0525b76e9d3da2:gentoo-project [gentoo-project] Re: Call for agenda items - Council meeting 2016-04-10 41e09d1ddc8b30abb9f9d21d205b7b82:gentoo-dev [gentoo-dev] [RFC] Masterplan for solving LINGUAS problems +44defe3ffe0fc93ad754bd895ed0196c:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 +474fc6822dba50ccc6192c9f31d8024a:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-03-11 4a88db38253494c6612a29117b2b19c8:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2016-11-13 50dbe189dd2641d5730f08944e7fa7ce:gentoo-project [gentoo-project] Gentoo Council: agenda for June 12 meeting +6041b91cfa4c52c427ddbbd4f69607ff:gentoo-project +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 637270936c9f07e3bd2f10ee45264a42:gentoo-project @@ -30,10 +40,16 @@ Re: [gentoo-dev] News item: Python ABIFLAGS rebuild needed Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14 70b28773ada15c2f4d1bcf1428ffa6a9:gentoo-project Ongoing stabilization discussion (Re: [gentoo-project] Council meeting 2016-11-13) +71c67cdf620f262b4f94765360c8c8c2:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 87e630b9da724c5c59060608aba596a9:gentoo-dev [gentoo-dev] RFC: Eclasses and EAPI +8fb1d8c0dd80e17cbb1fc633006f14b9:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-03-11 9578d459aee22ca47b1dc19149684662:gentoo-project Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-12-13 +9bc36a643a969e165c6f7cf228f2745c:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-04-08 a08ea09c2c8e534fd9bc1146703c66ff:gentoo-dev [gentoo-dev] [RFC] How to deal with LINGUAS mess? a0a53d00109512557d233997699e8ce1:gentoo-project @@ -42,6 +58,8 @@ a292e9567fac838681899b50dff24cce:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2016-04-10 b2e8c759b08c29f2c4215ea74511bf1c:gentoo-project Re: [gentoo-project] Call for agenda items - Council meeting 2014-02-25 +b59d8abb15e148b71d6e50180a2a27a7:gentoo-project +Re: [gentoo-project] Call for agenda items - Council meeting 2014-03-11 b9460b9c8d578c3498c217c17b75afd4:gentoo-dev [gentoo-dev] RFD: News item format 2.0 bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project diff --git a/decisions/decisions.tex b/decisions/decisions.tex index d9d13e5..35861d4 100644 --- a/decisions/decisions.tex +++ b/decisions/decisions.tex @@ -125,6 +125,8 @@ pdfauthor={Andreas K. Huettel} \include{summary-20140114} \include{summary-20140225} +\include{summary-20140311} +\include{summary-20140408} \chapter{Meeting summaries 2015/16} diff --git a/decisions/summary-20140311.tex b/decisions/summary-20140311.tex new file mode 100644 index 0000000..38fce80 --- /dev/null +++ b/decisions/summary-20140311.tex @@ -0,0 +1,89 @@ + +\summary{2014}{3}{11} + +\agendaitem{Vote on GLEP 63} + +Previous council action approved in principle the policies outlined in +"\glep{63}: Gentoo GPG key policies", but delayed the vote for approval +until the final language was put in place. dilfridge presented a shorter +version of the GLEP which removed the "howto" language and reduced it to +just policy (\wgoref{User:Dilfridge/GLEP:1001a}). Discussion progressed to a +consensus that we should have only policy in the GLEP and a practical guide +should be a separate document which can be changed without council vote. + +We tabled the vote until either an email vote (initiated by dilfridge) or +the next meeting. + + +\agendaitem{Ban on EAPI 1 and 2 should extend to updating EAPI in existing +ebuilds} +\index{EAPI!1}\index{EAPI!2} + +Reference: \agoref{gentoo-project}{3a319600f3dc2dc42703a710155b2882} + +The council considered the question of whether the ban on EAPIs 1 and 2 should +extended to updating EAPIs in *existing* ebuilds, and not just new ebuilds added +to the tree. mgorny noted that we need bumps from EAPI 0 to 1 because we need +an easy way to introduce slotting without the major rewriting of ebuild phases +than an EAPI 0 to 3 bump would require. After discussion, the council voted on +the following motion: + +\vote{EAPI 1 and 2 are now banned. This ban should not only be limited to new +ebuilds, but should be extended to include updating EAPIs in *existing* ebuilds. +In case of non-maintainer commits to fix dependencies, EAPI=0 ebuilds may be +updated to EAPI=1 to keep the changes at a non-intrusive level, as a temporary +workaround.}{Carried with 4 yes, 1 no and 1 abstention.} + + +\agendaitem{Make all cosmetic repoman warnings fatal} +\index{repoman} + +Reference: \agoref{gentoo-project}{8fb1d8c0dd80e17cbb1fc633006f14b9} + +The council considered the question of whether all repoman warnings should be +made fatal. Consensus was reached that this would lead to too many false +positives. + +The motion failed with 4 no and 1 abstention. + + +\agendaitem{Adherence to FHS standards in Gentoo: putting config files int /etc} +\index{FHS}\index{udev rules}\index{configuration files!location} + +References: +\begin{itemize} + \item \agoref{gentoo-project}{474fc6822dba50ccc6192c9f31d8024a} + \item \agoref{gentoo-project}{b59d8abb15e148b71d6e50180a2a27a7} + \item \url{http://devmanual.gentoo.org/general-concepts/filesystem/index.html} +\end{itemize} + + +The question of where config files should go was raised by patrick. The +council discussed whether it should be policy to put all config files in /etc. +However, what defines a config file is unclear because some packages, like udev or +eudev, put their *default* config files in /lib/udev/rules.d which are overridden +by the files in /etc/udev/rules.d. The former are not meant to be user-edited while +the later are. The council is okay with static config files living outside of /etc +while user-editable config files should be in /etc. + +rich0 introduced the following motion: + +\vote{Council does not feel additional policy required regarding config files +in /etc. +In particular packages that place config templates in /usr or /lib* and allow overriding +in /etc are fine. Specific issues not already discussed can be raised in future +meetings.}{Passed with 4 yes and 1 abstention.} + + +\agendaitem{Bugs with council involvement} + +The council looked at two open bugs: +\begin{itemize} +\item \bug{503382}: dberkholz said he would upload those summaries soon. +\item \bug{477030}: There has been no progress. scarabeus was to nudge +betelgeuse for that summary. +\end{itemize} + +\agendaitem{Open floor} + +No issues were brought forward. diff --git a/decisions/summary-20140408.tex b/decisions/summary-20140408.tex new file mode 100644 index 0000000..c3de03b --- /dev/null +++ b/decisions/summary-20140408.tex @@ -0,0 +1,117 @@ + +\summary{2014}{4}{8} + +\agendaitem{Vote on GLEP 63} + +Council action last meeting tabled the vote on "\glep{63}: Gentoo GPG key +policies" because dilfridge, one of the authors, presented a shorter version +which removed the "howto" language and reduced it to just policy +(\wgoref{User:Dilfridge/GLEP:1001a}). The council has now had time to consider +this version and the general feeling was that the GLEP should concentrate only +on policy and move any questions of implementation to another document. + +The council unanimously approved the shorter version. + + +\agendaitem{Use of ISO/IEC prefixes vs base-10} +\index{ISO prefixes} + +References: +\begin{itemize} + \item + \agoref{gentoo-project}{1c2224a5a468ff854e73fc60d25f7dce} + \item + \agoref{gentoo-project}{6041b91cfa4c52c427ddbbd4f69607ff} +\end{itemize} + +The council considered whether a) ISO/IEC prefixes, Ki=$2^{10}$, etc., should be +preferred over ISO base-10 prefixes, k=$10^3$, etc., or b) we should just +require unambiguous units in check-reqs.eclass, where KiB etc are base-2 and k +etc are base-10. Two proposal were brought forward by rich0. Proposal +2 was adopted: + +\begin{quote}{\it +Whenever practical developers are required to use unit prefixes defined in +IEC 80000-13 (kB, KiB, etc) so that output is unambiguous. This does not +require maintainers to patch upstream code to change its behavior, but they +should be applied with code that originates in Gentoo.} +\end{quote} + + +\agendaitem{Recent events regarding new virtuals, masking by QA and then +unmasking} +\index{project!QA}\index{mailing lists} + +References: +\begin{itemize} + \item \agoref{gentoo-project}{71c67cdf620f262b4f94765360c8c8c2} + \item http://article.gmane.org/gmane.linux.gentoo.devel/90800 (broken link) + \item \agoref{gentoo-project}{9bc36a643a969e165c6f7cf228f2745c} + \item \agoref{gentoo-project}{44defe3ffe0fc93ad754bd895ed0196c} +\end{itemize} + +The council consider what action to take with regards to the controversy around +the recent introduction of virtual/libudev and virtual/libgudev. Roughly the +time sequence of events was as follows: +\begin{enumerate} +\item the eudev team was excluded from discussions about the virtuals +\item the virtuals were committed, leading to breakage for eudev +\item the virtuals were masked by a member of the QA team +\item the virtuals were unmasked by their maintainer without authorization +from QA. +\end{enumerate} + +This led to two long discussion threads on gentoo-project@g.o and +gentoo-dev@g.o. dilfridge suggested the council take a position on five +points which address the systematic problems in the Gentoo community that led to +the above events. The council approved sending an email to the community +based on the following 4 of the 5 points: + +{\it \begin{enumerate} +\item The council encourages teams maintaining central parts of Gentoo to +accept new developers as team members and teach them the required knowledge and +intricacies. We consider this important to ensure long-term continuity and +increase the bus factor in critical areas. +\item While it is any developer's choice not to participate on the gentoo-dev +and +gentoo-project mailing lists, they nevertheless serve as main communication +channels. If something has been discussed there, and then action has been taken, +the council regards ignorance of the discussion not as a good foundation for +protests against the actions. +\item +The council believes that a wide announcement and if needed discussion of +changes to central parts of Gentoo (as, e.g., system packages, profiles) should +be preferred. In particular, only informing "relevant people" makes no sense if +others will also be affected. +\item +The council strongly disapproves of any developers unilaterally reverting QA +team actions. While any future case decisions lie with QA and ComRel teams, the +council welcomes the idea of immediate sanctions in such a case. An individual +developer who disagrees with an action made in the name of QA, whether the +action is proper or not, MUST follow the escalation procedures set forth in GLEP +48, and is encouraged to work with QA, or eventually ComRel or the council to +settle any concerns. The council will follow up on any accusations of QA abuse +the same way as on any commit that is in conflict with a QA action. +\end{enumerate}} + +One point urging QA to adopt policies regarding internal disagreements was +dropped since QA is in fact looking into the matter now. + + + +\agendaitem{Bugs with council involvement} + +The council looked at two open bugs: +\begin{itemize} + \item +\bug{503382}: dberkholz said he would upload those summaries soon. + \item +\bug{477030}: Still no progress here. scarabeus said he would try to bug +Betelgeuse again. +\end{itemize} + + +\agendaitem{Open floor} + +No issues were brought forward. + |