From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-council <gentoo-council@lists.gentoo.org>
Cc: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Subject: [gentoo-council] Agenda for the council meeting of February 8th 2010 at 2000UTC
Date: Sun, 7 Feb 2010 07:20:45 -0700 [thread overview]
Message-ID: <7c612fc61002070620s2c66496eyec0fab65713b7fb4@mail.gmail.com> (raw)
Please find below the agenda for the council meeting of 8 February
2010 at 2000UTC. Note that the time is one hour later than usual, i.e.
21:00 in western Europe, 3:00PM US east coast and noon for US west
coast
Denis.
----------.
1. Intro (5 minutes, including late arrivals)
1.1. Make sure somebody is logging
1.2. Roll call
1.3 Who wants to chair?
1.4. Last chance for remarks on the agenda
2. GLEP 58 (5 minutes)
Make sure you have read the latest version of GLEP 58 [1] and vote.
Proposed plan, see [2]:
1. Council approves GLEP58.
2. Portage support is added, we add MetaManifests everywhere needed
(top-level, categories, metadata, eclass etc) in the tree.
3. Old Portage versions still work at this point, because they ignore
the other Manifest files.
4. Wait 6-12 months for Portage upgrade cycle.
Then when and if desired we can proceed to dropping the per-package
Manifests but that will have to be the subject of an additional GLEP
at a later time (and we do have quite some time to come up with that
due to the above timeline):
5. Change the content of the MetaManifests to be per solar's proposal.
6. Drop per-package Manifests from the tree.
3. GLEP 59 (5 minutes)
Make sure you have read the latest version of GLEP 59 [3] and vote.
Note that due to Robin having had some issues with his flight to
FOSDEM the changes in [4] may not be in there yet, but vote as if they
were committed.
Proposed plan (see [2]):
- Can add new hashes right now.
- Some of the old hashes we can remove right now.
- Have to keep just one old hash for old Portage to still work.
4. GLEP 60 (5 minutes)
Make sure you have read the latest version of GLEP 60 [5] and vote.
Proposed plan (see [2]):
- Can add new types right now.
- Cannot remove ANY types for a full upgrade cycle.
5. GLEP 61 (5 minutes)
Make sure you have read the latest version of GLEP 61 [6] and vote.
Proposed plan (see [2]):
- (unconfirmed) Cannot add the compressed files in per-package locations until
the upgrade cycle is done, as old Portage will complain about their existence.
6. Open-ended discussion on VDB (30 minutes)
See the thread at [7]. Here's a non-exhaustive list of topics to
discuss (please try and keep technical details of potential
implementations for the end of the discussion):
Do we care about VDB caches currently not being compatible across
package managers?
Do we want to develop a way to work with more than one type of VDB
cache (similar to Brian's proposal or not) or do we prefer investing
our time into developing a new VDB?
What do you think about Brian's proposal in general?
Is a VDB cache EAPI material, i.e. should it be defined in PMS?
(currently PMS says explicitly that it shouldn't)
7. Conclusion (5 minutes)
11.1 Action list. Who does what and when?
11.2 Who takes care of the summary and log for this meeting? When?
11.3 Next meeting date/time.
11.4 Who will follow-up discussions and prepare the agenda for the
next meeting?
8. Open floor (ad libitum)
[1] http://www.gentoo.org/proj/en/glep/glep-0058.html
[2] http://archives.gentoo.org/gentoo-dev/msg_e55ccdc31273afb01baf156c682d1cfe.xml
[3] http://www.gentoo.org/proj/en/glep/glep-0059.html
[4] http://archives.gentoo.org/gentoo-dev/msg_506e7a7fd3147b49ce1394b88c67293b.xml
[5] http://www.gentoo.org/proj/en/glep/glep-0060.html
[6] http://www.gentoo.org/proj/en/glep/glep-0061.html
[7] http://archives.gentoo.org/gentoo-dev/msg_6b3e00049a1bf35fbf7a5e66d1449553.xml
next reply other threads:[~2010-02-07 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 14:20 Denis Dupeyron [this message]
2010-02-07 15:53 ` [gentoo-council] Agenda for the council meeting of February 8th 2010 at 2000UTC Robin H. Johnson
2010-02-08 18:01 ` Tobias Scherbaum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c612fc61002070620s2c66496eyec0fab65713b7fb4@mail.gmail.com \
--to=calchan@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox