[gentoo-dev] Gentoo Council Reminder for October 23

[gentoo-dev] Gentoo Council Reminder for October 23

[Donnie Berkholz]

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

This is your friendly reminder !  Same bat time (typically the 2nd & 4th
Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @
irc.freenode.net) !

If you have something you'd wish for us to chat about, maybe even vote
on, let us know!  Simply reply to this e-mail for the whole Gentoo dev
list to see.

Keep in mind that every GLEP *re*submission to the council for review
must first be sent to the gentoo-dev mailing list 7 days (minimum)
before being submitted as an agenda item which itself occurs 7 days
before the meeting.  Simply put, the gentoo-dev mailing list must be
notified at least 14 days before the meeting itself.

For more info on the Gentoo Council, feel free to browse our homepage:
http://www.gentoo.org/proj/en/council/

-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-dev] Gentoo Council Reminder for October 23

[Doug Goldstein]

Donnie Berkholz wrote:
> This is your friendly reminder !  Same bat time (typically the 2nd & 4th
> Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @
> irc.freenode.net) !
>
> If you have something you'd wish for us to chat about, maybe even vote
> on, let us know!  Simply reply to this e-mail for the whole Gentoo dev
> list to see.
>
> Keep in mind that every GLEP *re*submission to the council for review
> must first be sent to the gentoo-dev mailing list 7 days (minimum)
> before being submitted as an agenda item which itself occurs 7 days
> before the meeting.  Simply put, the gentoo-dev mailing list must be
> notified at least 14 days before the meeting itself.
>
> For more info on the Gentoo Council, feel free to browse our homepage:
> http://www.gentoo.org/proj/en/council/
>
>   
I'd like us to sit down and discuss the 10 opened bugs assigned to the
council and what we can do to resolve them.

--
Doug Goldstein