[FD.io TSC] Re: Please review Project Proposal and Mature Release Process mechanics for tomorrows TSC Call
|
Its a list you can subscribe to. I'd encourage TSC members to do so. Its purpose is to provide a channel that only handles such requests. Its not the *only* way to skin this cat. Some definitive 'Project actually proposed event' needs to occur. Mailing lists are good for events, often bad for state ;) Other alternatives we could consider is having those proposal emails go to the TSC mailer. This has the pro that you can get a single thread for proposal and scheduling, but the con that sometimes things get lost in the shuffle. I'd be incredibly open to discussing alternatives if folks would like :) Ed On Wed, Feb 17, 2016 at 11:19 AM, Joel Halpern <joel.halpern@...> wrote:
|
|
|
|
Joel Halpern
Unless there is someone we know of who specifically needs to see these propsoals, and does not care about the rest of the TSC work, I am inclined to tell them to send both the initial announcement and the formal “please review” message to the TSC list. We as TSC members should try to look early, and will look when the formal request is received.
If the TSC list gets overloaded, we can split things out later.
Just my take. Joel
From: Edward Warnicke [mailto:hagbard@...]
Sent: Wednesday, February 17, 2016 2:19 PM To: Joel Halpern Cc: tsc@... Subject: Re: [FD.io TSC] Please review Project Proposal and Mature Release Process mechanics for tomorrows TSC Call
Its a list you can subscribe to. I'd encourage TSC members to do so. Its purpose is to provide a channel that only handles such requests.
Its not the *only* way to skin this cat. Some definitive 'Project actually proposed event' needs to occur. Mailing lists are good for events, often bad for state ;)
Other alternatives we could consider is having those proposal emails go to the TSC mailer. This has the pro that you can get a single thread for proposal and scheduling, but the con that sometimes things get lost in the shuffle. I'd be incredibly open to discussing alternatives if folks would like :)
Ed
On Wed, Feb 17, 2016 at 11:19 AM, Joel Halpern <joel.halpern@...> wrote: The Project Proposal process says that the proposal should be sent to mailto:project-lifecycle@.... What does that actually translate to? Is it something we on the TSC need to subscribe to separately, something that copies to the TSC, something purely for LF staff?
Thanks, Joel
From: Edward Warnicke [mailto:hagbard@...]
As part of tomorrows fd.io TSC Agenda: https://wiki.fd.io/view/TSC#Agenda
We have: - Consideration of mechanics of Project Proposals - Consideration of mechanics of Mature Release Process I would ask folks to review these before the meeting, to facilitate conversation and expeditiously closing on them. This is particularly important and urgent as we have folks talking about bringing projects, and VPP has started conversations about releases. Ed
|
|
|