[gentoo-dev] Monthly Gentoo Council Reminder for February
This is your monthly friendly reminder ! Same bat time (typically the 3rd Thursday at 1800 UTC / 2000 CET / 1400 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/
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
On Mon, Feb 1, 2010 at 4:30 PM, Mike Frysinger vap...@gentoo.org wrote: This is your monthly friendly reminder ! Same bat time (typically the 3rd Thursday at 1800 UTC / 2000 CET / 1400 EST), same bat channel (#gentoo-council @ irc.freenode.net) ! Uh... no. The meeting is actually next Monday (January 8th) at 2000UTC / 2100CET / 1500 EST. We now adapt the date and time to suit our schedules and maximize everybody's chance to be available. Mike, could you please stop your cron job? It's now useless as I have to send the reminder email manually, which I do more or less two weeks in advance. Thanks, Denis.
[gentoo-dev] Monthly Gentoo Council Reminder for February
This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday 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/
[gentoo-dev] Monthly Gentoo Council Reminder for February
This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday 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/ -- gentoo-dev@lists.gentoo.org mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
On 01 Feb 2007 05:30:01 Mike Frysinger [EMAIL PROTECTED] wrote: This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday at 2000 UTC), 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. Some people requested that the acceptance of GLEP 23 gets reconfirmed by the council before I merge it into portage due to the changes it has received. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better. signature.asc Description: PGP signature
[gentoo-dev] Monthly Gentoo Council Reminder for February
This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday at 2000 UTC), 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/ -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
Vapier wrote: [Wed Jan 31 2007, 11:30:01PM CST] 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. Care to weigh-in on the tr1 issue? Due to the lack of really good ideas, it may be that a not-so-good one will need to be enacted by fiat. -g2boojum- -- Grant Goodyear Gentoo Developer [EMAIL PROTECTED] http://www.gentoo.org/~g2boojum GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76 pgp0vUValY5Wz.pgp Description: PGP signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
Mike Frysinger wrote: This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday at 2000 UTC), 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. I would like the council to discuss if we should have a policy on how long to wait for a developer to respond to a non critical bug before you can fix it yourself. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
On Thu, 01 Feb 2007 20:36:29 +0200 Petteri Räty [EMAIL PROTECTED] wrote: | I would like the council to discuss if we should have a policy on how | long to wait for a developer to respond to a non critical bug before | you can fix it yourself. Wouldn't that depend highly upon the bug? -- Ciaran McCreesh Mail: ciaranm at ciaranm.org Web : http://ciaranm.org/ Paludis, the secure package manager : http://paludis.pioto.org/ signature.asc Description: PGP signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
Ciaran McCreesh wrote: On Thu, 01 Feb 2007 20:36:29 +0200 Petteri Räty [EMAIL PROTECTED] wrote: | I would like the council to discuss if we should have a policy on how | long to wait for a developer to respond to a non critical bug before | you can fix it yourself. Wouldn't that depend highly upon the bug? It would but having some kind of deadline after which you are for example free to take over the package if you want to would be nice. Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
On Thursday 01 February 2007, Petteri Räty wrote: It would but having some kind of deadline after which you are for example free to take over the package if you want to would be nice. uhh this is certainly no good ... i wouldnt want someone looking at an old bug and going shit he hasnt fixed it, this package is now MINE i feel like a little more communication between people would address this ... you want to help fix a bug package, ask the maintainer if it's ok this isnt for dealing with MIA devs -mike pgpnx6j1RCjiU.pgp Description: PGP signature
Re: [gentoo-dev] Monthly Gentoo Council Reminder for February
On Thu, 01 Feb 2007 22:19:57 +0200 Petteri Räty [EMAIL PROTECTED] wrote: Ciaran McCreesh wrote: On Thu, 01 Feb 2007 20:36:29 +0200 Petteri Räty [EMAIL PROTECTED] wrote: | I would like the council to discuss if we should have a policy on how | long to wait for a developer to respond to a non critical bug before | you can fix it yourself. Wouldn't that depend highly upon the bug? It would but having some kind of deadline after which you are for example free to take over the package if you want to would be nice. That's going too far; there's certainly no need to take over a package just to get a fix in. If you want to take over a package, asking the current maintainer has to be the first step, not to quietly wait for a timeout then just grab it. Similarly asking the current maintainer if they mind you putting a fix in. If that approach doesn't succeed, it should then be put in the hands of devrel to arbitrate. I don't see that anything more is needed. -- Kevin F. Quinn signature.asc Description: PGP signature
[gentoo-dev] Monthly Gentoo Council Reminder for February
This is your monthly friendly reminder ! Same bat time (typically the 2nd Thursday once a month), 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 *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/ -- gentoo-dev@gentoo.org mailing list
