Re: [gentoo-dev] Gentoo Council Reminder for May 7
Tiziano Müller wrote: Am Montag, den 04.05.2009, 00:25 +0100 schrieb Roy Bamford: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2009.05.03 22:47, Tiziano Müller 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) ! [snip] Tiziano, The 7th is the first Thursday this month. Has there been a change to the meeting dates ? We usually have the meeting every two weeks, so the next meeting would be the next Thursday. Unless someone has objections I'd propose to hold the meeting then. I guess I have to change the template a little :) Isn't it second and fourth Thursday? Regards, Petteri signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Gentoo Council Reminder for May 7
On Mon, May 04, 2009 at 02:06:47PM +0300, Petteri R??ty wrote: Isn't it second and fourth Thursday? Regards, Petteri That's an oversimplification. That varies because of when we have some holidays and skip meetings, throughing the schedule off. It's easiest to remember it as every other thursday. Thomas -- - Thomas Anderson Gentoo Developer / Areas of responsibility: AMD64, Secretary to the Gentoo Council -
Re: [gentoo-dev] Gentoo Council Reminder for May 7
On 08:34 Mon 04 May , Thomas Anderson wrote: On Mon, May 04, 2009 at 02:06:47PM +0300, Petteri R??ty wrote: Isn't it second and fourth Thursday? Regards, Petteri That's an oversimplification. That varies because of when we have some holidays and skip meetings, throughing the schedule off. It's easiest to remember it as every other thursday. As a rule, it is the 2nd and 4th Thursday of each month. This is announced in every meeting email. Of course there are occasional exceptions, but they are exceptions and not the rule. I don't see why this would be one because I haven't heard anything about next week being bad. -- Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com pgpbKkCr9mxIL.pgp Description: PGP signature
Re: [gentoo-dev] Gentoo Council Reminder for May 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2009.05.04 10:20, Tiziano Müller wrote: [snip] We usually have the meeting every two weeks, so the next meeting would be the next Thursday. Unless someone has objections I'd propose to hold the meeting then. I guess I have to change the template a little :) -- Tiziano Müller Gentoo Linux Developer, Council Member Areas of responsibility: Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor E-Mail : dev-z...@gentoo.org GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 Tiziano, Every two weeks works 12 weeks out of 13 because months run in a 4,4,5 week cycle. That is, once every three months, there is three weeks between meetings. Is the council changing from meeting on the second and fourth Thursdays of the month to meetings every two weeks? The two are not quite the same. - -- Regards, Roy Bamford (NeddySeagoon) a member of gentoo-ops forum-mods treecleaners trustees -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkn/BEcACgkQTE4/y7nJvatKZwCdHz916Uh2Tz0IRPMkQ0fQ2NvL z3cAoJKf1daMoriN09IXFMOHkin1vXfu =0Njd -END PGP SIGNATURE-
[gentoo-dev] Gentoo Council Reminder for May 7
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. For more info on the Gentoo Council, feel free to browse our homepage: http://www.gentoo.org/proj/en/council/ Following is the preliminary meeting agenda. It consists of two EAPI-3 related topics as well as two almost rusty topics where we should finally make a decision to be able to move on. EAPI 3: Short discussion of the progress zmedico will provide an update on the progress of the implementation. Short discussion of problems and implementation decisions if needed. EAPI 3: PMS approval Goal: Approve EAPI-3 extension of the PMS. Any open questions should be on the mailing list before the meeting. GLEP 54: Dealing with live SCM packages --- Goal: Since no consensus is reached or progress has been made voting seems appropriate. Handling EAPI versioning in a forwards-compatible way - Goal: Since no consensus is reached vote on the implementation for the problem solved in GLEP 55. Handling static libraries more flexibly --- Goal: Decision-making by consensus. Should we move forward with USE=static-libs to control building of static libraries? Should/Must this be an EAPI feature? Define EAPI development/deployment cycles - Goal: Start discussion about EAPI development/deployment. For example: Collect problems of eapi introductions in the past, like reverting ebuilds to former eapis to get them stable, not waiting for the pm support a certain eapi before requesting stable keywords for ebuilds using the new eapi, Collect problems of EAPI development like feature-freeze, late feature removals (due to implementation problems). Eventually develop a lightweight EAPI development model. Cheers, Tiziano -- Tiziano Müller Gentoo Linux Developer, Council Member Areas of responsibility: Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor E-Mail : dev-z...@gentoo.org GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: [gentoo-dev] Gentoo Council Reminder for May 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2009.05.03 22:47, Tiziano Müller 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) ! [snip] Tiziano, The 7th is the first Thursday this month. Has there been a change to the meeting dates ? - -- Regards, Roy Bamford (NeddySeagoon) a member of gentoo-ops forum-mods treecleaners trustees -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkn+J/IACgkQTE4/y7nJvauidQCfeGBXSXYU6jqrOk3pYD3uBTiR PrcAoPb7BLme4fQvv2HMyPeAlV87MqL8 =2pDM -END PGP SIGNATURE-
