summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2017-04-15 23:56:09 +0200
committerAndreas K. Hüttel <dilfridge@gentoo.org>2017-04-15 23:56:09 +0200
commit23956f3be8fbb1e6b49eab65e23bb76c01137969 (patch)
treeafcbf6e807485cadae3a53bddf260c6bef4d828a /decisions
parentImprove up to 10/2007 (diff)
downloadcouncil-23956f3be8fbb1e6b49eab65e23bb76c01137969.tar.gz
council-23956f3be8fbb1e6b49eab65e23bb76c01137969.tar.bz2
council-23956f3be8fbb1e6b49eab65e23bb76c01137969.zip
Improve up to 12/2007
Diffstat (limited to 'decisions')
-rw-r--r--decisions/decisions.bux2
-rw-r--r--decisions/decisions.mlf10
-rw-r--r--decisions/decisions.mls10
-rw-r--r--decisions/decisions.mlt10
-rw-r--r--decisions/summary-20071108.tex104
-rw-r--r--decisions/summary-20071213.tex115
6 files changed, 134 insertions, 117 deletions
diff --git a/decisions/decisions.bux b/decisions/decisions.bux
index d39e3f0..3168ecc 100644
--- a/decisions/decisions.bux
+++ b/decisions/decisions.bux
@@ -13,7 +13,7 @@ dynamic SLOT;SLOT!dynamic
174410
IUSE defaults
179380
-ECONF_SOURCE
+ECONF_SOURCE;src_compile
185572
Code of Conduct;project!proctors
188449
diff --git a/decisions/decisions.mlf b/decisions/decisions.mlf
index a367d97..7108d59 100644
--- a/decisions/decisions.mlf
+++ b/decisions/decisions.mlf
@@ -150,6 +150,8 @@ Michael Palimaka
Mike Frysinger
70451197c3109e61ddd27e14a7bf89fa:gentoo-project
Andreas K. Huettel
+704eaff864d5f3484d940e6a2bc058d9:gentoo-council
+Donnie Berkholz
70b28773ada15c2f4d1bcf1428ffa6a9:gentoo-project
Kristian Fiskerstrand
70f0a835d44f0f772f80999d704b3dc8:gentoo-dev
@@ -236,6 +238,8 @@ b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
Ulrich Mueller
ba125098c929ea31f34051dfb009d436:gentoo-council
Donnie Berkholz
+ba2cdfa0060c1a2b7583e19185564855:gentoo-dev
+Mike Frysinger
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Ulrich Mueller
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -248,6 +252,8 @@ ca4a98ec7ab8c8b61561e3efdf59183d:gentoo-dev
Mike Frysinger
cb8a98613ce0682f9ee0aaa268f3374b:gentoo-dev
Spider
+cbfe572adb090dfba1cc004b1cca6979:gentoo-council
+Donnie Berkholz
cd71445e6968d5630161ae72d9c38562:gentoo-project
Michał Górny
cf6b02db6aa6c28021511fbf28f3aba3:gentoo-dev
@@ -274,8 +280,12 @@ dc5406af670aebc050362fcbd8cd528e:gentoo-project
Anthony G. Basile
dc9656603171900ed007b6be143c88da:gentoo-project
Andreas K. Huettel
+dcc6227eceaa2a4999e6a2a256dcddbc:gentoo-dev
+Jose Luis Rivero
dd3a90ba5e19283d05dd31ed4e104b5d:gentoo-council
Torsten Veller
+ded25cba302bfc6580c998d7ba33e1c7:gentoo-dev
+Mike Frysinger
dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Brian Harring
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
diff --git a/decisions/decisions.mls b/decisions/decisions.mls
index 34f3c40..4c3eacf 100644
--- a/decisions/decisions.mls
+++ b/decisions/decisions.mls
@@ -150,6 +150,8 @@ Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14
[gentoo-dev] Monthly Gentoo Council Reminder for March
70451197c3109e61ddd27e14a7bf89fa:gentoo-project
Re: Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2015-10-11
+704eaff864d5f3484d940e6a2bc058d9:gentoo-council
+[gentoo-council] Vote: Jokey for empty council slot
70b28773ada15c2f4d1bcf1428ffa6a9:gentoo-project
Ongoing stabilization discussion (Re: [gentoo-project] Council meeting 2016-11-13)
70f0a835d44f0f772f80999d704b3dc8:gentoo-dev
@@ -236,6 +238,8 @@ b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
[gentoo-dev] RFD: News item format 2.0
ba125098c929ea31f34051dfb009d436:gentoo-council
[gentoo-council] CoC: informal enforcement
+ba2cdfa0060c1a2b7583e19185564855:gentoo-dev
+[gentoo-dev] Monthly Gentoo Council Reminder for December
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Re: [gentoo-project] Call for Agenda Items -- Council Meeting 2016-01-10
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -248,6 +252,8 @@ ca4a98ec7ab8c8b61561e3efdf59183d:gentoo-dev
[gentoo-dev] Monthly Gentoo Council Reminder for June
cb8a98613ce0682f9ee0aaa268f3374b:gentoo-dev
Re: [gentoo-dev] GTK und GTK2 Use Flag
+cbfe572adb090dfba1cc004b1cca6979:gentoo-council
+[gentoo-council] CoC enforcement proposal
cd71445e6968d5630161ae72d9c38562:gentoo-project
Re: [gentoo-project] Council Meeting June 2: Call for Agenda Items
cf6b02db6aa6c28021511fbf28f3aba3:gentoo-dev
@@ -274,8 +280,12 @@ dc5406af670aebc050362fcbd8cd528e:gentoo-project
[gentoo-project] Re: [gentoo-dev-announce] Call for Agenda Items -- Council Meeting 2016-02-14
dc9656603171900ed007b6be143c88da:gentoo-project
Re: [gentoo-project] Council Meeting June 2: Call for Agenda Items
+dcc6227eceaa2a4999e6a2a256dcddbc:gentoo-dev
+[gentoo-dev] New USE flags documentation
dd3a90ba5e19283d05dd31ed4e104b5d:gentoo-council
[gentoo-council] Nominations open for the Gentoo Council 2007/08
+ded25cba302bfc6580c998d7ba33e1c7:gentoo-dev
+[gentoo-dev] Monthly Gentoo Council Reminder for November
dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Re: [gentoo-dev] New eclass: autotools-utils.eclass
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
diff --git a/decisions/decisions.mlt b/decisions/decisions.mlt
index fdc2e56..7cf4447 100644
--- a/decisions/decisions.mlt
+++ b/decisions/decisions.mlt
@@ -150,6 +150,8 @@ Thu, 31 Jul 2014 14:40:50
Wed, 01 Mar 2006 14:22:06
70451197c3109e61ddd27e14a7bf89fa:gentoo-project
Fri, 02 Oct 2015 14:44:16
+704eaff864d5f3484d940e6a2bc058d9:gentoo-council
+Thu, 08 Nov 2007 22:54:44
70b28773ada15c2f4d1bcf1428ffa6a9:gentoo-project
Mon, 07 Nov 2016 12:14:58
70f0a835d44f0f772f80999d704b3dc8:gentoo-dev
@@ -236,6 +238,8 @@ b9460b9c8d578c3498c217c17b75afd4:gentoo-dev
Tue, 12 Jan 2016 18:13:51
ba125098c929ea31f34051dfb009d436:gentoo-council
Thu, 14 Feb 2008 10:13:41
+ba2cdfa0060c1a2b7583e19185564855:gentoo-dev
+Sat, 01 Dec 2007 10:48:04
bc0a1b7498c389bdbb0b0d52feb43391:gentoo-project
Sun, 27 Dec 2015 18:03:56
bec5db8373fca0271fcadf0cd55724e8:gentoo-dev
@@ -248,6 +252,8 @@ ca4a98ec7ab8c8b61561e3efdf59183d:gentoo-dev
Thu, 01 Jun 2006 15:02:53
cb8a98613ce0682f9ee0aaa268f3374b:gentoo-dev
Tue, 29 Mar 2005 20:44:33
+cbfe572adb090dfba1cc004b1cca6979:gentoo-council
+Thu, 08 Nov 2007 12:05:25
cd71445e6968d5630161ae72d9c38562:gentoo-project
Tue, 09 Jun 2015 11:12:05
cf6b02db6aa6c28021511fbf28f3aba3:gentoo-dev
@@ -274,8 +280,12 @@ dc5406af670aebc050362fcbd8cd528e:gentoo-project
Thu, 04 Feb 2016 10:08:02
dc9656603171900ed007b6be143c88da:gentoo-project
Sun, 07 Jun 2015 16:34:15
+dcc6227eceaa2a4999e6a2a256dcddbc:gentoo-dev
+Sat, 24 Nov 2007 13:06:48
dd3a90ba5e19283d05dd31ed4e104b5d:gentoo-council
Mon, 02 Jul 2007 18:58:55
+ded25cba302bfc6580c998d7ba33e1c7:gentoo-dev
+Thu, 01 Nov 2007 09:32:52
dee3aab5e8c840ed3fa4add9c7d74b97:gentoo-dev
Sun, 18 Jul 2010 00:58:59
dfcb99f9fd1799313c6a5ef6e18f15b6:gentoo-project
diff --git a/decisions/summary-20071108.tex b/decisions/summary-20071108.tex
index 8d34a84..9fda1c9 100644
--- a/decisions/summary-20071108.tex
+++ b/decisions/summary-20071108.tex
@@ -1,19 +1,21 @@
\summary{2007}{11}{8}
-Agenda: http://thread.gmane.org/gmane.linux.gentoo.devel/52772 (dead link)
+Agenda call: \agoref{gentoo-dev}{ded25cba302bfc6580c998d7ba33e1c7}
-Also continuing discussion on CoC enforcement. Proposal:
-http://thread.gmane.org/gmane.linux.gentoo.council/82 (dead link)
+Also continuing the discussion on Code of Conduct enforcement. Proposal:
+\agoref{gentoo-council}{cbfe572adb090dfba1cc004b1cca6979}
+\agendaitem{Empty council slot: vote for jokey}
-\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.
+\dev{jokey} is the candidate to replace \dev{uberlord} who
+resigned,\footnote{It's unclear whether he resigned from the council or also
+from Gentoo in general.} and this requires a
+unanimous council vote. Since not all council members are present, we'll do
+this vote on the gentoo-council list.\footnote{See also the
+\agoref{gentoo-council}{704eaff864d5f3484d940e6a2bc058d9}.} All 6 present
+council members supported Jokey's addition.
\agendaitem{Daylight savings change: no slacker marks}
@@ -22,16 +24,15 @@ 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.
+\dev{vapier} needs to fix his script before the next announcement.
-\agendaitem{EAPI=1 approved for use in the main tree}
-\index{EAPI!1}
+\agendaitem{EAPI 1 approved for use in the main tree}
+\index{EAPI!1}\index{EAPI!1!in the tree}
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
@@ -41,7 +42,6 @@ portage:
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.
@@ -49,39 +49,35 @@ 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.
+Reference: \agoref{gentoo-council}{cbfe572adb090dfba1cc004b1cca6979} (sadly the
+actual text proposal is in an attachment)
+
+\dev{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.
+\dev{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.
+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.
@@ -89,13 +85,13 @@ 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.
+\dev{lu_zero} asked whether we had anything to do about baselayout-2 since
+\dev{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.
+\dev{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.
diff --git a/decisions/summary-20071213.tex b/decisions/summary-20071213.tex
index 9853688..6472b32 100644
--- a/decisions/summary-20071213.tex
+++ b/decisions/summary-20071213.tex
@@ -1,98 +1,89 @@
\summary{2007}{12}{13}
+Agenda call: \agoref{gentoo-dev}{ba2cdfa0060c1a2b7583e19185564855}
-\agendaitem{New USE documentation}
-\index{USE}\index{global changes}
-Reference: http://archives.gentoo.org/gentoo-dev/msg_149120.xml (dead link)
+\agendaitem{New USE documentation}
+\index{USE}\index{global changes}\index{metadata.xml}
-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?
+Reference: http://archives.gentoo.org/gentoo-dev/msg_149120.xml (dead
+link)\footnote{This is likely the
+\agoref{gentoo-dev}{dcc6227eceaa2a4999e6a2a256dcddbc}.}
-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}
+Considering the precedent set by how the documentation of use flags in
+metadata.xml was implemented, what should we do? Should we leave it in place or
+revert it? Should we require a GLEP?
-Result of the discussion:
+The result of the discussion was:
\begin{enumerate}
- \item
- We're leaving it, and considering further changes
- \item
- It should have been posted to -dev before committing for discussion
+\item
+We're leaving this improvement in place, and are considering further changes.
+\item
+It should have been posted to the gentoo-dev mailing list before committing
+for discussion.
\end{enumerate}
-General process for global changes:
+The general process for global changes shall be:\footnote{This algorithm isn't
+really spelled out that clearly in the log. It's kinda common sense though.}
\begin{itemize}
- \item
- 1. Post to -dev for discussion
- \item
- 2a. Consensus for implementing your idea as-is. No GLEP, no council.
+\item 1. Post to gentoo-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.
+\item 2b. Consensus for a GLEP for your idea, maybe disagreement over the idea.
+Write a GLEP. Discuss it on gentoo-dev. Submit the GLEP to the 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. The 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.
-
+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 are recommitted without council approval, the
+developer in question gets kicked out.
\agendaitem{Code of Conduct enforcement}
\index{Code of Conduct}\index{mailing list!gentoo-dev}
-\index{irc!channel!\#gentoo-dev}
+\index{irc!channel!\#gentoo-dev}\index{project!userrel}\index{project!devrel}
References:
\begin{itemize}
\item
- http://thread.gmane.org/gmane.linux.gentoo.council/82 (broken link)
+ \agoref{gentoo-council}{cbfe572adb090dfba1cc004b1cca6979}
\item
- \url{http://www.gentoo.org/proj/en/council/meeting-logs/20071108-summary.txt}
+ November 2007 council meeting summary
\end{itemize}
-
-Christy Fullam (musikc) made some valuable suggestions:
-
+\dev{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.
+\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?
+\dev{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.
+\dev{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
+Wulf Krüger (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.
+had not. \dev{kingtaco} 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. Some discussion ensued.