public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Agenda for September 14th meeting
Date: Sat, 12 Sep 2009 23:56:26 +0000	[thread overview]
Message-ID: <4AAC352A.50008@gentoo.org> (raw)
In-Reply-To: <20090912160801.2d679976@snowcone>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ciaran McCreesh wrote:
> On Sat, 12 Sep 2009 14:14:09 +0200
> Tobias Scherbaum <dertobi123@gentoo.org> wrote:
>> 3. EAPI/PMS (30 Minutes)
>>
>>   3.1. A process to modify PMS standard that doesn't directly involve
>>   the EAPI process.
>>   As requested by "Joshua Jackson" <tsunam@tsunam.org> / User
>> relations: Required people: tsuname, ulm
>>
>> "Per bug http://bugs.gentoo.org/show_bug.cgi?id=273261 I'm requesting
>> an AOB for the decision that was made by the PMS team about a process
>> or system to modify the PMS standard that doesn't directly involve
>> the EAPI process currently.
>>
>> I've set the hard date for them for the sept 10th meeting and this
>> gives them 3 weeks to work on this so it should be no issue for them
>> to come to this. I'm expecting them to be able to have a result by
>> then."
>
> I asked Joshua to retract this request because he was basing it on the
> mistaken impression that profiles weren't EAPI controlled (the Council
> voted to put profiles under EAPI control a while ago). Unfortunately he
> hasn't responded, so instead I'll ask the Council to disregard this
> since between the EAPI mechanism and the way we've used previously of
> not introducing changes that will break older things (by not reusing
> names, and not requiring support except on EAPI change) we've already
> got the whole thing covered.
>
Ciaran,

it isn't a "mistaken impression". Both Joshua and me think there are
alternatives and that the choice to put profiles/* under EAPI was
unfortunate and should be reviewed. It's also my opinion that what the
council approved was the use of a EAPI file under each profile to mark
the type of atoms that can be used in the profile files (slots, etc).

- --
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / SPARC / KDE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqsNSoACgkQcAWygvVEyAIrNgCcCGPWrj68Om56L3+vxpwnxWmF
VGwAnj+m1ay8F84C9YDBumJQu7Ihv9iQ
=osL8
-----END PGP SIGNATURE-----




  reply	other threads:[~2009-09-12 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 12:14 [gentoo-council] Agenda for September 14th meeting Tobias Scherbaum
2009-09-12 15:08 ` Ciaran McCreesh
2009-09-12 23:56   ` Jorge Manuel B. S. Vicetto [this message]
2009-09-13  0:05     ` Ciaran McCreesh
2009-09-13  0:16       ` Jorge Manuel B. S. Vicetto
2009-09-13  0:25   ` Jorge Manuel B. S. Vicetto
2009-09-12 16:45 ` Andrew D Kirch
2009-09-12 18:16   ` Ciaran McCreesh
2009-09-12 21:49     ` Andrew D Kirch
2009-09-12 21:58       ` Ciaran McCreesh

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=4AAC352A.50008@gentoo.org \
    --to=jmbsvicetto@gentoo.org \
    --cc=gentoo-council@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