From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Working Group established to evaluate the stable tree
Date: Sun, 14 Aug 2016 22:45:07 +0100 [thread overview]
Message-ID: <20160814224507.2b4e07b6@snowflex> (raw)
In-Reply-To: <6046d13b-1a54-aa5e-ab16-df448b0f8c59@gentoo.org>
On Sun, 14 Aug 2016 23:35:58 +0200
Kristian Fiskerstrand <k_f@gentoo.org> wrote:
> During the latest Council meeting it was determined to set up a new
> Working Group to come up with recommendations for improving the state
> of the stable tree at a later Council meeting.
What's a Working Group, and how is it related to a Project? Shouldn't
there be a GLEP to define what a Working Group is first?
--
Ciaran McCreesh
next prev parent reply other threads:[~2016-08-14 21:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 21:35 [gentoo-dev] New Working Group established to evaluate the stable tree Kristian Fiskerstrand
2016-08-14 21:45 ` Ciaran McCreesh [this message]
2016-08-14 21:49 ` Kristian Fiskerstrand
2016-08-14 21:49 ` Kent Fredric
2016-08-14 21:52 ` M. J. Everitt
2016-08-14 22:06 ` Chris Reffett
2016-08-14 21:50 ` Anthony G. Basile
2016-08-14 21:57 ` Ciaran McCreesh
2016-08-14 22:01 ` Kent Fredric
2016-08-15 19:18 ` Andreas K. Hüttel
2016-08-15 19:19 ` Michael Orlitzky
2016-08-15 3:45 ` Jason Zaman
2016-08-15 3:53 ` Kent Fredric
2016-08-15 4:05 ` Jason Zaman
2016-08-15 7:55 ` Brian Dolbec
2016-08-15 8:50 ` Kent Fredric
2016-08-15 10:21 ` Kristian Fiskerstrand
2016-08-18 6:33 ` Daniel Campbell
2016-08-15 13:40 ` Rich Freeman
2016-08-15 15:48 ` Brian Dolbec
2016-08-15 4:29 ` #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree) Kent Fredric
2016-08-15 4:37 ` Kent Fredric
2016-08-15 12:22 ` james
2016-08-15 12:49 ` Dirkjan Ochtman
2016-08-15 13:03 ` Kristian Fiskerstrand
2016-08-15 13:15 ` Dirkjan Ochtman
2016-08-15 13:25 ` Kristian Fiskerstrand
2016-08-15 14:28 ` james
2016-08-15 18:24 ` Dirkjan Ochtman
2016-08-15 19:30 ` Andreas K. Hüttel
2016-08-15 19:42 ` Rich Freeman
2016-08-21 0:30 ` Daniel Campbell
2016-10-04 17:25 ` Ian Stakenvicius
2016-10-07 2:40 ` Daniel Campbell
2016-08-15 23:00 ` Kent Fredric
2016-08-15 22:50 ` Kent Fredric
2016-08-15 8:00 ` [gentoo-dev] New Working Group established to evaluate the stable tree Pacho Ramos
2016-08-15 8:15 ` Pacho Ramos
2016-08-15 14:19 ` William Hubbs
2016-08-15 14:49 ` Kristian Fiskerstrand
2016-08-15 14:50 ` Kristian Fiskerstrand
2016-08-15 16:12 ` William Hubbs
2016-08-15 17:31 ` William Hubbs
2016-08-15 18:33 ` Rich Freeman
2016-08-15 19:12 ` William Hubbs
2016-08-15 19:27 ` Rich Freeman
2016-08-15 20:01 ` William Hubbs
2016-08-15 20:05 ` Rich Freeman
2016-08-16 8:02 ` [gentoo-dev] " Duncan
2016-08-16 13:52 ` William Hubbs
2016-08-17 8:52 ` [gentoo-dev] " Pacho Ramos
2016-08-17 8:50 ` Pacho Ramos
2016-08-17 13:07 ` Rich Freeman
2016-08-17 14:25 ` Pacho Ramos
2016-08-18 7:32 ` Raymond Jennings
2016-08-15 11:36 ` Kristian Fiskerstrand
2016-08-15 12:24 ` Michael Orlitzky
2016-08-15 13:37 ` Rich Freeman
2016-08-15 23:19 ` Kent Fredric
2016-08-15 19:33 ` Markus Meier
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=20160814224507.2b4e07b6@snowflex \
--to=ciaran.mccreesh@googlemail.com \
--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