You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary Martin <ga...@wandisco.com> on 2013/03/04 17:55:24 UTC
[VOTE] Graduate Apache Bloodhound
Hi,
I would like to invite the Bloodhound community to vote on whether
Apache Bloodhound is ready to graduate to top-level project status. The
result of this vote will demonstrate whether the community is willing to
govern itself which is a required step for graduation. If the community
votes for the resolution, then we will drawn up a charter for the
project and the IPMC will be asked to vote on recommending graduation to
the Apache Board of Directors.
Please vote:
[ ] +1 Graduate Apache Bloodhound from Incubator
[ ] +0 Indifferent to graduation status of Apache Bloodhound
[ ] -1 Reject graduation of Apache Bloodhound from Incubator
This vote will run for a minimum of 72 hours.
See https://incubator.apache.org/guides/graduation.html#toplevel for
more details of the process.
Cheers,
Gary
Re: [VOTE] Graduate Apache Bloodhound
Posted by Andrej Golcov <an...@digiverse.si>.
+1
On 5 March 2013 07:17, Gavin McDonald <ga...@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Gary Martin [mailto:gary.martin@wandisco.com]
>> Sent: Tuesday, 5 March 2013 3:25 AM
>> To: bloodhound-dev@incubator.apache.org
>> Subject: [VOTE] Graduate Apache Bloodhound
>>
>> Hi,
>>
>> I would like to invite the Bloodhound community to vote on whether Apache
>> Bloodhound is ready to graduate to top-level project status. The result of
> this
>> vote will demonstrate whether the community is willing to govern itself
>> which is a required step for graduation. If the community votes for the
>> resolution, then we will drawn up a charter for the project and the IPMC
> will
>> be asked to vote on recommending graduation to the Apache Board of
>> Directors.
>>
>> Please vote:
>>
>
>
> [ X ] +1 Graduate Apache Bloodhound from Incubator
>
> Gav...
>
>
> [ ] +0 Indifferent to
>> graduation status of Apache Bloodhound [ ] -1 Reject graduation of Apache
>> Bloodhound from Incubator
>>
>> This vote will run for a minimum of 72 hours.
>>
>> See https://incubator.apache.org/guides/graduation.html#toplevel for more
>> details of the process.
>>
>> Cheers,
>> Gary
>
>
RE: [VOTE] Graduate Apache Bloodhound
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Gary Martin [mailto:gary.martin@wandisco.com]
> Sent: Tuesday, 5 March 2013 3:25 AM
> To: bloodhound-dev@incubator.apache.org
> Subject: [VOTE] Graduate Apache Bloodhound
>
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether Apache
> Bloodhound is ready to graduate to top-level project status. The result of
this
> vote will demonstrate whether the community is willing to govern itself
> which is a required step for graduation. If the community votes for the
> resolution, then we will drawn up a charter for the project and the IPMC
will
> be asked to vote on recommending graduation to the Apache Board of
> Directors.
>
> Please vote:
>
[ X ] +1 Graduate Apache Bloodhound from Incubator
Gav...
[ ] +0 Indifferent to
> graduation status of Apache Bloodhound [ ] -1 Reject graduation of Apache
> Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
> See https://incubator.apache.org/guides/graduation.html#toplevel for more
> details of the process.
>
> Cheers,
> Gary
Re: [VOTE] Graduate Apache Bloodhound
Posted by Jure Zitnik <ju...@digiverse.si>.
On 3/4/13 5:55 PM, Gary Martin wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether
> Apache Bloodhound is ready to graduate to top-level project status.
> The result of this vote will demonstrate whether the community is
> willing to govern itself which is a required step for graduation. If
> the community votes for the resolution, then we will drawn up a
> charter for the project and the IPMC will be asked to vote on
> recommending graduation to the Apache Board of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
+1
Re: [VOTE] Graduate Apache Bloodhound
Posted by Jose Angel Franco Navarro <ja...@gmail.com>.
2013/3/5, Gary Martin <ga...@wandisco.com>:
>
>> [ ] +1 Graduate Apache Bloodhound from Incubator
>> [ ] +0 Indifferent to graduation status of Apache Bloodhound
>> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>>
>
> +1
>
>
[ X ] +1 Graduate Apache Bloodhound from Incubator
Regards,
Franco
Re: [VOTE] Graduate Apache Bloodhound
Posted by Gary Martin <ga...@wandisco.com>.
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
+1
Re: [VOTE] Graduate Apache Bloodhound
Posted by Mark Poole <ma...@poole.im>.
+1
On Mon, Mar 4, 2013 at 8:55 AM, Gary Martin <ga...@wandisco.com>wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether Apache
> Bloodhound is ready to graduate to top-level project status. The result of
> this vote will demonstrate whether the community is willing to govern
> itself which is a required step for graduation. If the community votes for
> the resolution, then we will drawn up a charter for the project and the
> IPMC will be asked to vote on recommending graduation to the Apache Board
> of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
> See https://incubator.apache.org/**guides/graduation.html#**toplevel<https://incubator.apache.org/guides/graduation.html#toplevel>for more details of the process.
>
> Cheers,
> Gary
>
>
Re: [VOTE] Graduate Apache Bloodhound
Posted by Olemis Lang <ol...@gmail.com>.
On 3/4/13, Gary Martin <ga...@wandisco.com> wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether
> Apache Bloodhound is ready to graduate to top-level project status. The
> result of this vote will demonstrate whether the community is willing to
> govern itself which is a required step for graduation. If the community
> votes for the resolution, then we will drawn up a charter for the
> project and the IPMC will be asked to vote on recommending graduation to
> the Apache Board of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
+1 ... fwiw (non-binding) in case that matters
;)
--
Regards,
Olemis.
Re: [VOTE] Graduate Apache Bloodhound
Posted by Matevž Bradač <ma...@gmail.com>.
On 4. Mar, 2013, at 17:55, Gary Martin wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether Apache Bloodhound is ready to graduate to top-level project status. The result of this vote will demonstrate whether the community is willing to govern itself which is a required step for graduation. If the community votes for the resolution, then we will drawn up a charter for the project and the IPMC will be asked to vote on recommending graduation to the Apache Board of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
> See https://incubator.apache.org/guides/graduation.html#toplevel for more details of the process.
>
> Cheers,
> Gary
>
+1
--
matevz
Re: [VOTE] Graduate Apache Bloodhound
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mar 4, 2013 8:56 AM, "Gary Martin" <ga...@wandisco.com> wrote:
>
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether Apache
Bloodhound is ready to graduate to top-level project status. The result of
this vote will demonstrate whether the community is willing to govern
itself which is a required step for graduation. If the community votes for
the resolution, then we will drawn up a charter for the project and the
IPMC will be asked to vote on recommending graduation to the Apache Board
of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
> See https://incubator.apache.org/guides/graduation.html#toplevel for more
details of the process.
>
> Cheers,
> Gary
>
+1
Re: [VOTE] Graduate Apache Bloodhound
Posted by Peter Koželj <pe...@digiverse.si>.
+1
Peter
On 4 March 2013 17:55, Gary Martin <ga...@wandisco.com> wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether Apache
> Bloodhound is ready to graduate to top-level project status. The result of
> this vote will demonstrate whether the community is willing to govern
> itself which is a required step for graduation. If the community votes for
> the resolution, then we will drawn up a charter for the project and the
> IPMC will be asked to vote on recommending graduation to the Apache Board
> of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> This vote will run for a minimum of 72 hours.
>
> See https://incubator.apache.org/**guides/graduation.html#**toplevel<https://incubator.apache.org/guides/graduation.html#toplevel>for more details of the process.
>
> Cheers,
> Gary
>
>
Re: [VOTE] Graduate Apache Bloodhound
Posted by Joe Dreimann <jo...@wandisco.com>.
+1
________________________
@jdreimann - Twitter
Sent from my phone
On 4 Mar 2013, at 17:03, Branko Čibej <br...@wandisco.com> wrote:
> On 04.03.2013 17:55, Gary Martin wrote:
>> Hi,
>>
>> I would like to invite the Bloodhound community to vote on whether
>> Apache Bloodhound is ready to graduate to top-level project status.
>> The result of this vote will demonstrate whether the community is
>> willing to govern itself which is a required step for graduation. If
>> the community votes for the resolution, then we will drawn up a
>> charter for the project and the IPMC will be asked to vote on
>> recommending graduation to the Apache Board of Directors.
>>
>> Please vote:
>>
>> [ ] +1 Graduate Apache Bloodhound from Incubator
>> [ ] +0 Indifferent to graduation status of Apache Bloodhound
>> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
>
> +1
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
Re: [VOTE] Graduate Apache Bloodhound
Posted by Branko Čibej <br...@wandisco.com>.
On 04.03.2013 17:55, Gary Martin wrote:
> Hi,
>
> I would like to invite the Bloodhound community to vote on whether
> Apache Bloodhound is ready to graduate to top-level project status.
> The result of this vote will demonstrate whether the community is
> willing to govern itself which is a required step for graduation. If
> the community votes for the resolution, then we will drawn up a
> charter for the project and the IPMC will be asked to vote on
> recommending graduation to the Apache Board of Directors.
>
> Please vote:
>
> [ ] +1 Graduate Apache Bloodhound from Incubator
> [ ] +0 Indifferent to graduation status of Apache Bloodhound
> [ ] -1 Reject graduation of Apache Bloodhound from Incubator
+1
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Charter preparation
Posted by Branko Čibej <br...@wandisco.com>.
On 08.03.2013 16:42, Gary Martin wrote:
> Hi Joe,
>
> I would say that committers indicating approval or otherwise would
> seem to be appropriate, particularly if we want to get the
> general@incubator vote started soon.
This all looks good to me. I propose you post this to general@incubator
as the graduation vote thread now. Don't forget to include links to our
community vote thread in the ASF list archives.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Charter preparation
Posted by Gary Martin <ga...@wandisco.com>.
Hi Joe,
I would say that committers indicating approval or otherwise would seem
to be appropriate, particularly if we want to get the general@incubator
vote started soon.
Cheers,
Gary
On 08/03/13 10:54, Joachim Dreimann wrote:
> Not sure whether we're supposed to vote on this, but..
>
> +1
>
>
> On 7 March 2013 11:52, Gary Martin <ga...@wandisco.com> wrote:
>
>> On 07/03/13 01:41, Greg Stein wrote:
>>
>>> On Wed, Mar 6, 2013 at 4:10 PM, Gary Martin <ga...@wandisco.com>
>>> wrote:
>>>
>>>> ...
>>>>
>>>>> We can take all current BH committers and put them onto the PMC
>>>>> roster. Individuals can remove themselves.
>>>>>
>>>> In which case shall we skip the invitation to mentors, put them all on
>>>> the
>>>> PMC and let them remove themselves if they wish? Just to speed things
>>>> along!
>>>>
>>> Yeah. None of the mentors (active or not) are going to mess up the
>>> PMC, so it can't hurt. And if they don't get their name off the list
>>> before the Board votes on it, then they can also be removed later. Not
>>> hard.
>>>
>>> The Board does like to see at least one ASF Member on every PMC(*),
>>> and by my count you'll have four (myself, Brane, Hyrum, and Gavin).
>>>
>>> Cheers,
>>> -g
>>>
>>> (*) even this isn't an absolute requirement, but close to it; a PMC
>>> with no ASF Members generally doesn't have a way to nominate PMC
>>> Members for ASF Membership; that is very bad for the long term, as we
>>> want to see projects better overseen by ASF Members; the Board usually
>>> finds a Director that is willing to volunteer to be added to the
>>> roster, fulfilling its desire for "at least one".
>>>
>> Excellent.
>>
>> So, given what has been discussed so far, at the end of this message is a
>> draft of the resolution based on a template with the following
>> substitutions:
>>
>> ${PROJECT} = "Bloodhound"
>> ${DESCRIPTION-AND-SCOPE} = "a software development collaboration tool,
>> including issue tracking, wiki and repository browsing"
>>
>> I have also added all mentors and current Bloodhound committers to the
>> list of initial PMC members (alphabetical by surname) and put my name as
>> the chair. Obviously all these details remain subject to change (I don't
>> mean this to cement my position as chair - please do volunteer if you want
>> this role and please do not consider it as ruffling feathers or being too
>> much trouble to make the change to the resolution.)
>>
>> I lifted the description and scope directly from the description on the
>> incubation status page (http://incubator.apache.org/**
>> projects/bloodhound.html<http://incubator.apache.org/projects/bloodhound.html>).
>> Is there any need to adjust this? (Note that the phrase appears twice in
>> the text if any change is necessary.)
>>
>> Cheers,
>> Gary
>>
>>
>> X. Establish the Apache Bloodhound Project
>>
>> WHEREAS, the Board of Directors deems it to be in the best
>> interests of the Foundation and consistent with the
>> Foundation's purpose to establish a Project Management
>> Committee charged with the creation and maintenance of
>> open-source software, for distribution at no charge to
>> the public, related to a software development collaboration
>> tool, including issue tracking, wiki and repository browsing.
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>> Committee (PMC), to be known as the "Apache Bloodhound Project",
>> be and hereby is established pursuant to Bylaws of the
>> Foundation; and be it further
>>
>> RESOLVED, that the Apache Bloodhound Project be and hereby is
>> responsible for the creation and maintenance of software
>> related to a software development collaboration tool, including
>> issue tracking, wiki and repository browsing; and be it further
>>
>> RESOLVED, that the office of "Vice President, Apache Bloodhound" be
>> and hereby is created, the person holding such office to
>> serve at the direction of the Board of Directors as the chair
>> of the Apache Bloodhound Project, and to have primary responsibility
>> for management of the projects within the scope of
>> responsibility of the Apache Bloodhound Project; and be it further
>>
>> RESOLVED, that the persons listed immediately below be and
>> hereby are appointed to serve as the initial members of the
>> Apache Bloodhound Project:
>>
>> * Mat Booth <mb...@apache.org>
>> * Matevž Bradač <ma...@apache.org>
>> * John Chambers <ch...@apache.org>
>> * Branko Čibej <br...@apache.org>
>> * Joachim Dreimann <jd...@apache.org>
>> * Andrej Golcov <an...@apache.org>
>> * Peter Koželj <pe...@apache.org>
>> * Gary Martin <gj...@apache.org>
>> * Gavin McDonald <gm...@apache.org>
>> * Ryan Ollos <rj...@apache.org>
>> * Mark Poole <mp...@apache.org>
>> * Greg Stein <gs...@apache.org>
>> * Hyrum K. Wright <hw...@apache.org>
>> * Jure Žitnik <ju...@apache.org>
>>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary Martin
>> be appointed to the office of Vice President, Apache Bloodhound, to
>> serve in accordance with and subject to the direction of the
>> Board of Directors and the Bylaws of the Foundation until
>> death, resignation, retirement, removal or disqualification,
>> or until a successor is appointed; and be it further
>>
>> RESOLVED, that the initial Apache Bloodhound PMC be and hereby is
>> tasked with the creation of a set of bylaws intended to
>> encourage open development and increased participation in the
>> Apache Bloodhound Project; and be it further
>>
>> RESOLVED, that the Apache Bloodhound Project be and hereby
>> is tasked with the migration and rationalization of the Apache
>> Incubator Bloodhound podling; and be it further
>>
>> RESOLVED, that all responsibilities pertaining to the Apache
>> Incubator Bloodhound podling encumbered upon the Apache Incubator
>> Project are hereafter discharged.
>>
>>
>
Re: Charter preparation
Posted by Joachim Dreimann <jo...@wandisco.com>.
Not sure whether we're supposed to vote on this, but..
+1
On 7 March 2013 11:52, Gary Martin <ga...@wandisco.com> wrote:
> On 07/03/13 01:41, Greg Stein wrote:
>
>> On Wed, Mar 6, 2013 at 4:10 PM, Gary Martin <ga...@wandisco.com>
>> wrote:
>>
>>> ...
>>>
>>>> We can take all current BH committers and put them onto the PMC
>>>> roster. Individuals can remove themselves.
>>>>
>>> In which case shall we skip the invitation to mentors, put them all on
>>> the
>>> PMC and let them remove themselves if they wish? Just to speed things
>>> along!
>>>
>> Yeah. None of the mentors (active or not) are going to mess up the
>> PMC, so it can't hurt. And if they don't get their name off the list
>> before the Board votes on it, then they can also be removed later. Not
>> hard.
>>
>> The Board does like to see at least one ASF Member on every PMC(*),
>> and by my count you'll have four (myself, Brane, Hyrum, and Gavin).
>>
>> Cheers,
>> -g
>>
>> (*) even this isn't an absolute requirement, but close to it; a PMC
>> with no ASF Members generally doesn't have a way to nominate PMC
>> Members for ASF Membership; that is very bad for the long term, as we
>> want to see projects better overseen by ASF Members; the Board usually
>> finds a Director that is willing to volunteer to be added to the
>> roster, fulfilling its desire for "at least one".
>>
>
> Excellent.
>
> So, given what has been discussed so far, at the end of this message is a
> draft of the resolution based on a template with the following
> substitutions:
>
> ${PROJECT} = "Bloodhound"
> ${DESCRIPTION-AND-SCOPE} = "a software development collaboration tool,
> including issue tracking, wiki and repository browsing"
>
> I have also added all mentors and current Bloodhound committers to the
> list of initial PMC members (alphabetical by surname) and put my name as
> the chair. Obviously all these details remain subject to change (I don't
> mean this to cement my position as chair - please do volunteer if you want
> this role and please do not consider it as ruffling feathers or being too
> much trouble to make the change to the resolution.)
>
> I lifted the description and scope directly from the description on the
> incubation status page (http://incubator.apache.org/**
> projects/bloodhound.html<http://incubator.apache.org/projects/bloodhound.html>).
> Is there any need to adjust this? (Note that the phrase appears twice in
> the text if any change is necessary.)
>
> Cheers,
> Gary
>
>
> X. Establish the Apache Bloodhound Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a software development collaboration
> tool, including issue tracking, wiki and repository browsing.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Bloodhound Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Bloodhound Project be and hereby is
> responsible for the creation and maintenance of software
> related to a software development collaboration tool, including
> issue tracking, wiki and repository browsing; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Bloodhound" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Bloodhound Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Bloodhound Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Bloodhound Project:
>
> * Mat Booth <mb...@apache.org>
> * Matevž Bradač <ma...@apache.org>
> * John Chambers <ch...@apache.org>
> * Branko Čibej <br...@apache.org>
> * Joachim Dreimann <jd...@apache.org>
> * Andrej Golcov <an...@apache.org>
> * Peter Koželj <pe...@apache.org>
> * Gary Martin <gj...@apache.org>
> * Gavin McDonald <gm...@apache.org>
> * Ryan Ollos <rj...@apache.org>
> * Mark Poole <mp...@apache.org>
> * Greg Stein <gs...@apache.org>
> * Hyrum K. Wright <hw...@apache.org>
> * Jure Žitnik <ju...@apache.org>
>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary Martin
> be appointed to the office of Vice President, Apache Bloodhound, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache Bloodhound PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache Bloodhound Project; and be it further
>
> RESOLVED, that the Apache Bloodhound Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Bloodhound podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Bloodhound podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *
Re: Charter preparation
Posted by Gary Martin <ga...@wandisco.com>.
On 07/03/13 01:41, Greg Stein wrote:
> On Wed, Mar 6, 2013 at 4:10 PM, Gary Martin <ga...@wandisco.com> wrote:
>> ...
>>> We can take all current BH committers and put them onto the PMC
>>> roster. Individuals can remove themselves.
>> In which case shall we skip the invitation to mentors, put them all on the
>> PMC and let them remove themselves if they wish? Just to speed things along!
> Yeah. None of the mentors (active or not) are going to mess up the
> PMC, so it can't hurt. And if they don't get their name off the list
> before the Board votes on it, then they can also be removed later. Not
> hard.
>
> The Board does like to see at least one ASF Member on every PMC(*),
> and by my count you'll have four (myself, Brane, Hyrum, and Gavin).
>
> Cheers,
> -g
>
> (*) even this isn't an absolute requirement, but close to it; a PMC
> with no ASF Members generally doesn't have a way to nominate PMC
> Members for ASF Membership; that is very bad for the long term, as we
> want to see projects better overseen by ASF Members; the Board usually
> finds a Director that is willing to volunteer to be added to the
> roster, fulfilling its desire for "at least one".
Excellent.
So, given what has been discussed so far, at the end of this message is
a draft of the resolution based on a template with the following
substitutions:
${PROJECT} = "Bloodhound"
${DESCRIPTION-AND-SCOPE} = "a software development collaboration tool,
including issue tracking, wiki and repository browsing"
I have also added all mentors and current Bloodhound committers to the
list of initial PMC members (alphabetical by surname) and put my name as
the chair. Obviously all these details remain subject to change (I don't
mean this to cement my position as chair - please do volunteer if you
want this role and please do not consider it as ruffling feathers or
being too much trouble to make the change to the resolution.)
I lifted the description and scope directly from the description on the
incubation status page
(http://incubator.apache.org/projects/bloodhound.html). Is there any
need to adjust this? (Note that the phrase appears twice in the text if
any change is necessary.)
Cheers,
Gary
X. Establish the Apache Bloodhound Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a software development collaboration
tool, including issue tracking, wiki and repository browsing.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Bloodhound Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Bloodhound Project be and hereby is
responsible for the creation and maintenance of software
related to a software development collaboration tool, including
issue tracking, wiki and repository browsing; and be it further
RESOLVED, that the office of "Vice President, Apache Bloodhound" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Bloodhound Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Bloodhound Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Bloodhound Project:
* Mat Booth <mb...@apache.org>
* Matevž Bradač <ma...@apache.org>
* John Chambers <ch...@apache.org>
* Branko Čibej <br...@apache.org>
* Joachim Dreimann <jd...@apache.org>
* Andrej Golcov <an...@apache.org>
* Peter Koželj <pe...@apache.org>
* Gary Martin <gj...@apache.org>
* Gavin McDonald <gm...@apache.org>
* Ryan Ollos <rj...@apache.org>
* Mark Poole <mp...@apache.org>
* Greg Stein <gs...@apache.org>
* Hyrum K. Wright <hw...@apache.org>
* Jure Žitnik <ju...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gary Martin
be appointed to the office of Vice President, Apache Bloodhound, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Bloodhound PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Bloodhound Project; and be it further
RESOLVED, that the Apache Bloodhound Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Bloodhound podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Bloodhound podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Re: Charter preparation
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Mar 6, 2013 at 4:10 PM, Gary Martin <ga...@wandisco.com> wrote:
>...
>> We can take all current BH committers and put them onto the PMC
>> roster. Individuals can remove themselves.
>
> In which case shall we skip the invitation to mentors, put them all on the
> PMC and let them remove themselves if they wish? Just to speed things along!
Yeah. None of the mentors (active or not) are going to mess up the
PMC, so it can't hurt. And if they don't get their name off the list
before the Board votes on it, then they can also be removed later. Not
hard.
The Board does like to see at least one ASF Member on every PMC(*),
and by my count you'll have four (myself, Brane, Hyrum, and Gavin).
Cheers,
-g
(*) even this isn't an absolute requirement, but close to it; a PMC
with no ASF Members generally doesn't have a way to nominate PMC
Members for ASF Membership; that is very bad for the long term, as we
want to see projects better overseen by ASF Members; the Board usually
finds a Director that is willing to volunteer to be added to the
roster, fulfilling its desire for "at least one".
Re: Charter preparation
Posted by Gary Martin <ga...@wandisco.com>.
On 06/03/13 20:44, Greg Stein wrote:
> On Wed, Mar 6, 2013 at 3:25 PM, Branko Čibej <br...@wandisco.com> wrote:
>> ...
>> The resolution is mostly boilerplate, but the community must decide
>> several things which have bearing on the resolution:
>>
>> * The composition of the new PMC
>> * The proposed PMC chairman
>>
>> For the PMC, I propose that all current committers become PMC members
>> when the project graduates. I also propose we adopt the "committer ==
>> PMC member" model after graduation, as given the number of active
>> developers, it makes little sense to maintain that artificial barrier. I
>> also propose you invite the mentors onto the PMC.
>>
>> N.B., Subversion has the concept of "partial committer", i.e., a
>> contributor with ASF committer status but whose commit rights are
>> restricted to a branch or a specific area of the code (this restriction
>> is not enforced via access control). It's IMO too early to complicate
>> matters on this project by emulating this practice.
> Yup. All sounds good.
Yes, I agree with all that.
>
>> Regarding the PMC chair, given that a TLP no longer has mentors, it's
>> usually a good idea at least initially to give the funny hat to someone
>> who has a bit more mileage with the ASF. But that's by no means a
>> requirement. All the PMC chair really does is submit reports to the board.
> I think that I just heard a nomination for Brane to be PMC chair :-P
>
> Seriously, though... this isn't much of a rule. Most VPs are not ASF
> Members. I look at them more as "liaisons", and the parameters/needs
> of that role are fairly easy to learn. So in that sense, any of the
> existing PPMC members can be a candidate.
>
>>> A quick look at the guidelines do not suggest that anything in
>>> particular needs to be restricted to the private list but I will be
>>> happy to accept advice on that.
>> I see no reason to keep anything private, except for the actual
>> invitations to the PMC, which I believe should remain private (i.e., on
>> the private list) (Greg, I'd appreciate your insight on that topic).
> I don't see anything that needs to be private right now.
> (post-graduation: yeah, "people discussions" ought to remain private;
> e.g. committer/PMC invitations)
>
> We can take all current BH committers and put them onto the PMC
> roster. Individuals can remove themselves.
In which case shall we skip the invitation to mentors, put them all on
the PMC and let them remove themselves if they wish? Just to speed
things along!
> If somebody has a desire to be the Chair, then I would recommend they
> self-nominate. If we get more than one, then we discuss that on
> -private.
>
> Cheers,
> -g
Well, I am prepared to take it on and, equally, I would be prepared to
stand down if there are others who desire it more. I am not sure that
desire is exactly the right word here anyway.
Cheers,
Gary
Re: Charter preparation
Posted by Gary Martin <ga...@wandisco.com>.
On 06/03/13 21:04, Branko Čibej wrote:
> On 06.03.2013 21:44, Greg Stein wrote:
>> I think that I just heard a nomination for Brane to be PMC chair :-P
> Plaintext has a hard time rendering the flashing neon-pink double-sized
> bold italic of "by no means a requirement." But I admit I had you in
> mind when I wrote that ... :)
>
> -- Brane
>
>
Another good suggestion! :)
Cheers,
Gary
Re: Charter preparation
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Mar 6, 2013 at 4:04 PM, Branko Čibej <br...@wandisco.com> wrote:
> On 06.03.2013 21:44, Greg Stein wrote:
>> I think that I just heard a nomination for Brane to be PMC chair :-P
>
> Plaintext has a hard time rendering the flashing neon-pink double-sized
> bold italic of "by no means a requirement." But I admit I had you in
> mind when I wrote that ... :)
haha! Can't get me that easy, young one. I already wear a VP hat, so
I'm gonna make up a rule that says I can't wear two. So there!
:-P
Strictly speaking, we've got people in multiple VP positions, *but* no
multi-PMC VPs. No rule against it. Sam is our only multi VP, I believe
(Infra and Legal). Chris Mattmann may have been a double PMC VP for a
bit, but has traded away one or both.
*shrug*
Gary has volunteered. If anybody else is interested, then please throw
your name in the ring.
Cheers,
-g
Re: Charter preparation
Posted by Branko Čibej <br...@wandisco.com>.
On 06.03.2013 21:44, Greg Stein wrote:
> I think that I just heard a nomination for Brane to be PMC chair :-P
Plaintext has a hard time rendering the flashing neon-pink double-sized
bold italic of "by no means a requirement." But I admit I had you in
mind when I wrote that ... :)
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: Charter preparation
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Mar 6, 2013 at 3:25 PM, Branko Čibej <br...@wandisco.com> wrote:
>...
> The resolution is mostly boilerplate, but the community must decide
> several things which have bearing on the resolution:
>
> * The composition of the new PMC
> * The proposed PMC chairman
>
> For the PMC, I propose that all current committers become PMC members
> when the project graduates. I also propose we adopt the "committer ==
> PMC member" model after graduation, as given the number of active
> developers, it makes little sense to maintain that artificial barrier. I
> also propose you invite the mentors onto the PMC.
>
> N.B., Subversion has the concept of "partial committer", i.e., a
> contributor with ASF committer status but whose commit rights are
> restricted to a branch or a specific area of the code (this restriction
> is not enforced via access control). It's IMO too early to complicate
> matters on this project by emulating this practice.
Yup. All sounds good.
> Regarding the PMC chair, given that a TLP no longer has mentors, it's
> usually a good idea at least initially to give the funny hat to someone
> who has a bit more mileage with the ASF. But that's by no means a
> requirement. All the PMC chair really does is submit reports to the board.
I think that I just heard a nomination for Brane to be PMC chair :-P
Seriously, though... this isn't much of a rule. Most VPs are not ASF
Members. I look at them more as "liaisons", and the parameters/needs
of that role are fairly easy to learn. So in that sense, any of the
existing PPMC members can be a candidate.
>> A quick look at the guidelines do not suggest that anything in
>> particular needs to be restricted to the private list but I will be
>> happy to accept advice on that.
>
> I see no reason to keep anything private, except for the actual
> invitations to the PMC, which I believe should remain private (i.e., on
> the private list) (Greg, I'd appreciate your insight on that topic).
I don't see anything that needs to be private right now.
(post-graduation: yeah, "people discussions" ought to remain private;
e.g. committer/PMC invitations)
We can take all current BH committers and put them onto the PMC
roster. Individuals can remove themselves.
If somebody has a desire to be the Chair, then I would recommend they
self-nominate. If we get more than one, then we discuss that on
-private.
Cheers,
-g
Re: Charter preparation
Posted by Branko Čibej <br...@wandisco.com>.
On 06.03.2013 21:14, Gary Martin wrote:
> On 06/03/13 19:38, Gary Martin wrote:
>>
>> OK, I'll see if I can work out what goes on with creating the
>> charter/resolution which I think the guidelines suggest should be
>> done prior to the vote. It will be worth trying to get this done
>> quickly but obviously it will be as quick as the community allows.
>>
>> Cheers,
>> Gary
>
> So, the resolution looks pretty straight forward to write.
The resolution is mostly boilerplate, but the community must decide
several things which have bearing on the resolution:
* The composition of the new PMC
* The proposed PMC chairman
For the PMC, I propose that all current committers become PMC members
when the project graduates. I also propose we adopt the "committer ==
PMC member" model after graduation, as given the number of active
developers, it makes little sense to maintain that artificial barrier. I
also propose you invite the mentors onto the PMC.
N.B., Subversion has the concept of "partial committer", i.e., a
contributor with ASF committer status but whose commit rights are
restricted to a branch or a specific area of the code (this restriction
is not enforced via access control). It's IMO too early to complicate
matters on this project by emulating this practice.
Regarding the PMC chair, given that a TLP no longer has mentors, it's
usually a good idea at least initially to give the funny hat to someone
who has a bit more mileage with the ASF. But that's by no means a
requirement. All the PMC chair really does is submit reports to the board.
> A quick look at the guidelines do not suggest that anything in
> particular needs to be restricted to the private list but I will be
> happy to accept advice on that.
I see no reason to keep anything private, except for the actual
invitations to the PMC, which I believe should remain private (i.e., on
the private list) (Greg, I'd appreciate your insight on that topic).
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Charter preparation (Was Re: [RESULT][VOTE] Graduate Apache Bloodhound)
Posted by Gary Martin <ga...@wandisco.com>.
On 06/03/13 19:38, Gary Martin wrote:
>
> OK, I'll see if I can work out what goes on with creating the
> charter/resolution which I think the guidelines suggest should be done
> prior to the vote. It will be worth trying to get this done quickly
> but obviously it will be as quick as the community allows.
>
> Cheers,
> Gary
So, the resolution looks pretty straight forward to write. A quick look
at the guidelines do not suggest that anything in particular needs to be
restricted to the private list but I will be happy to accept advice on that.
Cheers,
Gary
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Greg Stein <gs...@gmail.com>.
I'd suggest just looking at the general@ archives for prior graduation votes.
The "charter" is really just that fragment of the opening paragraph of
the resolution. For example:
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to [issue tracking].
Fill in whatever on that sentence (i.e. BH is a bit more than just
issue tracking).
I dunno where a template is for the resolution, but you could use
Apache Wink, in 7B, from:
http://www.apache.org/foundation/records/minutes/2012/board_minutes_2012_12_19.txt
Cheers,
-g
On Wed, Mar 6, 2013 at 2:38 PM, Gary Martin <ga...@wandisco.com> wrote:
> On 06/03/13 19:30, Branko Čibej wrote:
>>
>> On 06.03.2013 20:13, Greg Stein wrote:
>>>
>>> On Wed, Mar 6, 2013 at 1:47 PM, Branko Čibej <br...@wandisco.com> wrote:
>>>>
>>>> On 06.03.2013 19:41, Joe Dreimann wrote:
>>>>>
>>>>> Seems relevant for the report today as well, could someone please add
>>>>> this result while I'm still waiting on my edit permissions?
>>>>
>>>> Already done, I went through the report and noted this fact and also
>>>> made a few minor tweaks, so please review the result.
>>>
>>> The Incubator report is not due to the Board until Friday, March 15.
>>> If the wider IPMC votes to graduate Bloodhound, then we can get that
>>> into the report, and a resolution sent to the Board.
>>>
>>> And then I'll get to vote twice: once as an IPMC Member, and once as a
>>> Director. :-D
>>
>> In that case, Gary, launch the Incubator vote sooner rather than later. :)
>>
>> -- Brane
>>
>
> OK, I'll see if I can work out what goes on with creating the
> charter/resolution which I think the guidelines suggest should be done prior
> to the vote. It will be worth trying to get this done quickly but obviously
> it will be as quick as the community allows.
>
> Cheers,
> Gary
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Gary Martin <ga...@wandisco.com>.
On 06/03/13 19:30, Branko Čibej wrote:
> On 06.03.2013 20:13, Greg Stein wrote:
>> On Wed, Mar 6, 2013 at 1:47 PM, Branko Čibej <br...@wandisco.com> wrote:
>>> On 06.03.2013 19:41, Joe Dreimann wrote:
>>>> Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
>>> Already done, I went through the report and noted this fact and also
>>> made a few minor tweaks, so please review the result.
>> The Incubator report is not due to the Board until Friday, March 15.
>> If the wider IPMC votes to graduate Bloodhound, then we can get that
>> into the report, and a resolution sent to the Board.
>>
>> And then I'll get to vote twice: once as an IPMC Member, and once as a
>> Director. :-D
> In that case, Gary, launch the Incubator vote sooner rather than later. :)
>
> -- Brane
>
OK, I'll see if I can work out what goes on with creating the
charter/resolution which I think the guidelines suggest should be done
prior to the vote. It will be worth trying to get this done quickly but
obviously it will be as quick as the community allows.
Cheers,
Gary
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Branko Čibej <br...@wandisco.com>.
On 06.03.2013 20:13, Greg Stein wrote:
> On Wed, Mar 6, 2013 at 1:47 PM, Branko Čibej <br...@wandisco.com> wrote:
>> On 06.03.2013 19:41, Joe Dreimann wrote:
>>> Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
>> Already done, I went through the report and noted this fact and also
>> made a few minor tweaks, so please review the result.
> The Incubator report is not due to the Board until Friday, March 15.
> If the wider IPMC votes to graduate Bloodhound, then we can get that
> into the report, and a resolution sent to the Board.
>
> And then I'll get to vote twice: once as an IPMC Member, and once as a
> Director. :-D
In that case, Gary, launch the Incubator vote sooner rather than later. :)
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Mar 6, 2013 at 1:47 PM, Branko Čibej <br...@wandisco.com> wrote:
> On 06.03.2013 19:41, Joe Dreimann wrote:
>> Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
>
> Already done, I went through the report and noted this fact and also
> made a few minor tweaks, so please review the result.
The Incubator report is not due to the Board until Friday, March 15.
If the wider IPMC votes to graduate Bloodhound, then we can get that
into the report, and a resolution sent to the Board.
And then I'll get to vote twice: once as an IPMC Member, and once as a
Director. :-D
Cheers,
-g
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Gary Martin <ga...@wandisco.com>.
On 06/03/13 18:47, Branko Čibej wrote:
> On 06.03.2013 19:41, Joe Dreimann wrote:
>> Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
> Already done, I went through the report and noted this fact and also
> made a few minor tweaks, so please review the result.
>
> -- Brane
The slightest of tweaks from me.. hopefully nothing anyone else would
notice :)
I may consider going through it again but it looks pretty good really.
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Branko Čibej <br...@wandisco.com>.
On 06.03.2013 19:41, Joe Dreimann wrote:
> Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
Already done, I went through the report and noted this fact and also
made a few minor tweaks, so please review the result.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Joe Dreimann <jo...@wandisco.com>.
Seems relevant for the report today as well, could someone please add this result while I'm still waiting on my edit permissions?
- Joe
________________________
@jdreimann - Twitter
Sent from my phone
On 6 Mar 2013, at 18:21, Branko Čibej <br...@wandisco.com> wrote:
> After 72-and-a-bit hours, these are the results of the Bloodhound
> community vote on graduation readiness:
>
> +1:
>
> Andrej Golcov (andrej)
> Branko Čibej (brane, mentor/IPMC)
> Gavin McDonald (gmcdonald, PPMC)
> Gary Martin (gjm, PPMC)
> Joachim Dreimann (jdreimann)
> Jose Angel Franco Navarro
> Jure Žitnik (jure)
> Mark Poole (mpoole, PPMC)
> Matevž Bradač (matevz)
> Olemis Lang
> Peter Koželj (peter)
> Ryan Ollos (rjollos)
>
> +0: none
> -1: none
>
>
> -- Brane
>
> --
> Branko Čibej
> Director of Subversion | WANdisco | www.wandisco.com
>
Re: [RESULT][VOTE] Graduate Apache Bloodhound
Posted by Branko Čibej <br...@wandisco.com>.
After 72-and-a-bit hours, these are the results of the Bloodhound
community vote on graduation readiness:
+1:
Andrej Golcov (andrej)
Branko Čibej (brane, mentor/IPMC)
Gavin McDonald (gmcdonald, PPMC)
Gary Martin (gjm, PPMC)
Joachim Dreimann (jdreimann)
Jose Angel Franco Navarro
Jure Žitnik (jure)
Mark Poole (mpoole, PPMC)
Matevž Bradač (matevz)
Olemis Lang
Peter Koželj (peter)
Ryan Ollos (rjollos)
+0: none
-1: none
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com