summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Alexander <wired@gentoo.org>2010-11-24 21:48:37 +0000
committerAlex Alexander <wired@gentoo.org>2010-11-24 21:48:37 +0000
commit20759e0fb93327224f889f17fa2f589f9d3c9e2e (patch)
tree86ba4ff7847aa2ed84e1e84921862b9b2ab37118 /meeting-logs/20101026-summary.txt
parentAdded log for the 20101026 meeting. (diff)
downloadcouncil-20759e0fb93327224f889f17fa2f589f9d3c9e2e.tar.gz
council-20759e0fb93327224f889f17fa2f589f9d3c9e2e.tar.bz2
council-20759e0fb93327224f889f17fa2f589f9d3c9e2e.zip
20101026 council meeting details and summary
Diffstat (limited to 'meeting-logs/20101026-summary.txt')
-rw-r--r--meeting-logs/20101026-summary.txt40
1 files changed, 40 insertions, 0 deletions
diff --git a/meeting-logs/20101026-summary.txt b/meeting-logs/20101026-summary.txt
new file mode 100644
index 0000000..d825254
--- /dev/null
+++ b/meeting-logs/20101026-summary.txt
@@ -0,0 +1,40 @@
+2010-10-26 Council meeting summary
+==================================
+
+All members present:
+ betelgeuse, chainsaw, ferringb, jmbsvicetto, halcyon, scarabeus, wired
+
+Agenda:
+ ferringb forgot to send meeting related mail, so there was no
+ announced agenda.
+
+Topics discussed:
+
+ la files
+ --------
+
+ The council decided that removing la files is the right thing to do,
+ but the whole thing will be taken to the -dev ML to allow devs to
+ express their opinions/objections, if any. Jorge will handle this.
+
+ The removal will only happen after portage-2.1.9 or later is
+ stabilized, since this is the first version that can fix la files
+ automatically.
+
+ At that time, a news item will be released to inform users on how to
+ fix any issues that may arise from the removal.
+
+ EAPI 4
+ ------
+
+ few_ suggested finalizing EAPI 4 with the features currently
+ implemented in portage (bug #273620).
+
+ we agreed that this is a good idea, as long as a spec list is built
+ and PMS patches are written for all the features.
+
+ ferringb will write documentation for REQUIRED_USE.
+
+ the council will finalize things in the next meeting. people
+ responsible for EAPI 4 should be pinged beforehand so they can attend
+ that meeting.