From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-dev] One-Day Gentoo Council Reminder for April
Date: Thu, 10 Apr 2008 00:56:50 -0700 [thread overview]
Message-ID: <20080410075650.GB32329@comet> (raw)
In-Reply-To: <20080409070321.7768866A28@smtp.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On 03:03 Wed 09 Apr , Mike Frysinger wrote:
> This is your one-day friendly reminder ! The monthly Gentoo Council
> meeting is tomorrow in #gentoo-council on irc.freenode.net. See the
> channel topic for the exact time (but it's probably 2000 UTC).
>
> If you're supposed to show up, please show up. If you're not supposed
> to show up, then show up anyways and watch your Council monkeys dance
> for you.
>
> For more info on the Gentoo Council, feel free to browse our homepage:
> http://www.gentoo.org/proj/en/council/
Here's the proposed agenda. Added CC for the council list.
Thanks,
Donnie
[-- Attachment #2: 20080410-summary.txt --]
[-- Type: text/plain, Size: 1834 bytes --]
Requested attendees
===================
GLEP 46: vanquirius, ciaranm, dev-zero
PMS: ciaranm, halcy0n
Roll call
=========
(here, proxy [by whom] or slacker?)
amne
betelgeuse
dberkholz
flameeyes
lu_zero
vapier
jokey
Updates to last month's topics
==============================
http://www.gentoo.org/proj/en/council/meeting-logs/20080313-summary.txt
Document of being an active developer
-------------------------------------
Last month:
No updates
Updates:
Slacker arches
--------------
3 months ago:
vapier will work on rich0's suggestion and repost it for
discussion on -dev ML
Last month:
vapier said he was going to work on it this weekend.
Updates:
GLEP 46: Allow upstream tags in metadata.xml
--------------------------------------------
http://www.gentoo.org/proj/en/glep/glep-0046.html
2 months ago:
Caveat on approval about allowed protocols
Updates:
Restriction to http/https has been dropped as pointed out by
council members (amne and Flameeyes if I'm right). The point
for restricting the URLs to the mentioned protocols was that
they shouldn't link to automatically updated ressources. This
has been replaced by an explicit specification and a
recommendation that http/http should be favoured over
ftp/svn/gopher/etc to make the implementation for automated
update discovery tools easier (they should of course ignore URLs
they can't handle).
Ready for confirmation, which should be mainly a formality.
New topics
==========
Minimal activity for ebuild devs
--------------------------------
Current is 1 commit every 60 days. Should it be higher?
Initial comments on PMS
-----------------------
http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git
Are there any major changes needed, or just tuning details?
next prev parent reply other threads:[~2008-04-10 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 3:03 [gentoo-dev] One-Day Gentoo Council Reminder for April Mike Frysinger
2008-04-10 7:56 ` Donnie Berkholz [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-08 3:00 Mike Frysinger
2009-04-08 14:36 ` Rémi Cardona
2009-04-09 18:38 ` Donnie Berkholz
2009-04-09 22:25 ` Rémi Cardona
2009-04-08 16:31 ` Tobias Scherbaum
2009-04-08 23:44 ` Brian Harring
2009-04-08 21:39 ` Donnie Berkholz
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=20080410075650.GB32329@comet \
--to=dberkholz@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoo-dev@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