Re: Vote on personal matters: majority vote vs consensus
On Thu, Mar 28, 2013 at 5:01 PM, Joe Schaefer joe_schae...@yahoo.com wrote: As Doug points out, votes are structured away from the status quo- we don't ever vote to continue on with previously agreed to issues just to circumvent the voting process. Ok thanks Joe and Doug. So to be absolutely clear, the wording of votes is important and votes need to be structured the right way. You can tell how to do it by looking at if the resulting action changes the status quo. Using the previous example if Joe wants to send an email to me to saying I'm now not a mentor, or remove me from a status file, etc then thats changing the status quo so now requires a 75% vote. Right? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Vote on personal matters: majority vote vs consensus
On Fri, Mar 29, 2013 at 8:47 AM, Matthias Friedrich m...@mafr.de wrote: As someone who is relatively new to the ASF and who's first behind the scenes contact with Apache was the incubation process, I can tell that this is absolutely true. Podlings find themselves in a kafkaesque world where many rules are undocumented or can only be found in old mailing list discussions. Apache and this list especially can feel like a really hostile place for newbies. Regards, Matthias Unfortunately it can feel quite hostile to even not so newbies too. Once out of the Incubator its a much more friendly place though. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Creating announce@ lists by default
Thanks Greg. Sane advice. I'll add this to my todo list and see if I can come up with a patch for the docs. On 28 March 2013 06:50, Greg Stein gst...@gmail.com wrote: On Wed, Mar 27, 2013 at 2:46 PM, Noah Slater nsla...@apache.org wrote: ... I don't believe we should force an announce@ list on anybody. But I do think it might be a good idea to mention a few of the standard lists that projects might consider requesting. No strong opinion. Generally, I don't think podlings have much to announce. A few releases, at most, before they graduate. IMO, just put those on announce@ and be done with it. Large communities arriving at the Incubator could certainly do well with an announce@. But new/small projects? Not so much. user@, dev@, announce@, etc. commits@ is required. When you're community grows, you may want to consider tickets@, and general@, etc. CloudStack had marketing@ before we graduated, even. Note: as mentioned else-thread, we strongly discourage a users@ mailing list for podlings. (or more precisely, those building *new* communities) Oh, and while we are at it: some a.o projects have users@project.a.o(plural) and others have user@project.a.o(singular). We should at least unify this for the upcoming podlings pretty please ;) Sounds sensible. Agreed. I took a quick look on mail-archive.a.o, and it appears that user@ is more popular than users@ (185 vs 76). (bummer, cuz svn uses users@ ...) Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS
Re: Creating announce@ lists by default
On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater nsla...@apache.org wrote: Thanks Greg. Sane advice. I'll add this to my todo list and see if I can come up with a patch for the docs. The obvious place to patch is the descriptive paragraph here: http://incubator.apache.org/guides/proposal.html#template-mailing-lists However, I question whether decisions about mailing lists should be made by the small group that typically works up a proposal. Why not start off with just a dev list and have the entire community participate in discussions about what additional mailing lists to add? * Do we need a user@ list yet? * Where should commit notifications be sent? * Where should issue tracker notifications be sent? * Should we add an announce@ list? These questions all have interesting implications with regard to community dynamics, and I think it would benefit podlings to be considering them early on. So, I'd like to propose a page describing the various mailing list choices that top-level Apache projects have made and the tradeoffs, which I volunteer to write and which I think ought to live on community.a.o rather than incubator.a.o. Once that page is live, I propose that we modify the proposal template so that the default is only a dev list. Mailing list expansion then becomes part of the incubation curriculum, along with code import, header change, preparation of a release management procedure, making a release, recruiting new contributors/committers/PMC-members, and so on. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Creating announce@ lists by default
I really like this idea, Marvin. If you're gonna run with it, I'll take a step back. On 30 March 2013 15:39, Marvin Humphrey mar...@rectangular.com wrote: On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater nsla...@apache.org wrote: Thanks Greg. Sane advice. I'll add this to my todo list and see if I can come up with a patch for the docs. The obvious place to patch is the descriptive paragraph here: http://incubator.apache.org/guides/proposal.html#template-mailing-lists However, I question whether decisions about mailing lists should be made by the small group that typically works up a proposal. Why not start off with just a dev list and have the entire community participate in discussions about what additional mailing lists to add? * Do we need a user@ list yet? * Where should commit notifications be sent? * Where should issue tracker notifications be sent? * Should we add an announce@ list? These questions all have interesting implications with regard to community dynamics, and I think it would benefit podlings to be considering them early on. So, I'd like to propose a page describing the various mailing list choices that top-level Apache projects have made and the tradeoffs, which I volunteer to write and which I think ought to live on community.a.o rather than incubator.a.o. Once that page is live, I propose that we modify the proposal template so that the default is only a dev list. Mailing list expansion then becomes part of the incubation curriculum, along with code import, header change, preparation of a release management procedure, making a release, recruiting new contributors/committers/PMC-members, and so on. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS
[VOTE] recommend Apache DeltaSpike for graduating out of the incubator
Hi!
The Apache DeltaSpike podling is a project which contains common CDI Extensions
which are portable among many different Java EE containers and even run on
standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a big
majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is final and
switches to maintenance, but that it is vital and there is an active community
around it. And this is certainly the case as shown by the 21 votes we got the
last days.
Our status file [2] got updated recently and I consider the podling namesearch
task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation
proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracek gpetracek at apache.org
Mark Struberg struberg at apache.org
Pete Muir pmuir at redhat.com
Jason Porter lightguard.jp at gmail.com
Shane Bryzak sbryzak at gmail.com
Rudy de Busscher rdebusscher at apache.org
Christian Kaltepoth christian at kaltepoth.de
Arne Limburg arne.limburg at openknowledge.de
Charles Moulliard cmoulliard at gmail.com
Cody Lerum cody.lerum at gmail.com
Romain Mannu-Buccau rmannibucau at gmail.com
Matthew Jason Benson mbenson at apache.org
Jim Jagielski jim at apache.org
David Blevins dblevins at apache.org
Ken Finnigan ken at kenfinnigan.me
John D. Ament johndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator DeltaSpike podling encumbered upon the Apache Incubator
Project are hereafter discharged.
https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator
here is my
+1 (binding)
LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: general@incubator.apache.org general@incubator.apache.org
Cc:
Sent: Saturday, March 30, 2013 5:54 PM
Subject: [VOTE] recommend Apache DeltaSpike for graduating out of the
incubator
Hi!
The Apache DeltaSpike podling is a project which contains common CDI
Extensions
which are portable among many different Java EE containers and even run on
standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a big
majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is
final and switches to maintenance, but that it is vital and there is an
active
community around it. And this is certainly the case as shown by the 21 votes
we
got the last days.
Our status file [2] got updated recently and I consider the podling
namesearch
task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached
graduation proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracek gpetracek at apache.org
Mark Struberg struberg at apache.org
Pete Muir pmuir at redhat.com
Jason Porter lightguard.jp at gmail.com
Shane Bryzak sbryzak at gmail.com
Rudy de Busscher rdebusscher at apache.org
Christian Kaltepoth christian at kaltepoth.de
Arne Limburg arne.limburg at openknowledge.de
Charles Moulliard cmoulliard at gmail.com
Cody Lerum cody.lerum at gmail.com
Romain Mannu-Buccau rmannibucau at gmail.com
Matthew Jason Benson mbenson at apache.org
Jim Jagielski jim at apache.org
David Blevins dblevins at apache.org
Ken Finnigan ken at kenfinnigan.me
John D. Ament johndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator DeltaSpike podling encumbered upon the Apache Incubator
Project are hereafter discharged.
https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator
+1
regards,
gerhard
2013/3/30 Mark Struberg strub...@yahoo.de
Hi!
The Apache DeltaSpike podling is a project which contains common CDI
Extensions which are portable among many different Java EE containers and
even run on standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a
big majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is final and
switches to maintenance, but that it is vital and there is an active
community around it. And this is certainly the case as shown by the 21
votes we got the last days.
Our status file [2] got updated recently and I consider the podling
namesearch task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached
graduation proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracek gpetracek at apache.org
Mark Struberg struberg at apache.org
Pete Muir pmuir at redhat.com
Jason Porter lightguard.jp at gmail.com
Shane Bryzak sbryzak at gmail.com
Rudy de Busscher rdebusscher at apache.org
Christian Kaltepoth christian at kaltepoth.de
Arne Limburg arne.limburg at openknowledge.de
Charles Moulliard cmoulliard at gmail.com
Cody Lerum cody.lerum at gmail.com
Romain Mannu-Buccau rmannibucau at gmail.com
Matthew Jason Benson mbenson at apache.org
Jim Jagielski jim at apache.org
David Blevins dblevins at apache.org
Ken Finnigan ken at kenfinnigan.me
John D. Ament johndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator DeltaSpike podling encumbered upon the Apache Incubator
Project are hereafter discharged.
https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator
+1 (binding) from me.
Good luck!
Cheers,
Chris
++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++
-Original Message-
From: Mark Struberg strub...@yahoo.de
Reply-To: general@incubator.apache.org general@incubator.apache.org,
Mark Struberg strub...@yahoo.de
Date: Saturday, March 30, 2013 9:54 AM
To: general@incubator.apache.org general@incubator.apache.org
Subject: [VOTE] recommend Apache DeltaSpike for graduating out of the
incubator
Hi!
The Apache DeltaSpike podling is a project which contains common CDI
Extensions which are portable among many different Java EE containers and
even run on standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a
big majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is final and
switches to maintenance, but that it is vital and there is an active
community around it. And this is certainly the case as shown by the 21
votes we got the last days.
Our status file [2] got updated recently and I consider the podling
namesearch task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached
graduation proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracek gpetracek at apache.org
Mark Struberg struberg at apache.org
Pete Muir pmuir at redhat.com
Jason Porter lightguard.jp at gmail.com
Shane Bryzak sbryzak at gmail.com
Rudy de Busscher rdebusscher at apache.org
Christian Kaltepoth christian at kaltepoth.de
Arne Limburg arne.limburg at openknowledge.de
Charles Moulliard cmoulliard at gmail.com
Cody Lerum cody.lerum at gmail.com
Romain Mannu-Buccau rmannibucau at gmail.com
Matthew Jason Benson mbenson at apache.org
Jim Jagielski jim at apache.org
David Blevins dblevins at apache.org
Ken Finnigan ken at kenfinnigan.me
John D. Ament johndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator
+1 (binding)
Cheers
Christian
On Sat, Mar 30, 2013 at 5:54 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
The Apache DeltaSpike podling is a project which contains common CDI
Extensions which are portable among many different Java EE containers and
even run on standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a big
majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is final and
switches to maintenance, but that it is vital and there is an active
community around it. And this is certainly the case as shown by the 21 votes
we got the last days.
Our status file [2] got updated recently and I consider the podling
namesearch task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation
proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracek gpetracek at apache.org
Mark Struberg struberg at apache.org
Pete Muir pmuir at redhat.com
Jason Porter lightguard.jp at gmail.com
Shane Bryzak sbryzak at gmail.com
Rudy de Busscher rdebusscher at apache.org
Christian Kaltepoth christian at kaltepoth.de
Arne Limburg arne.limburg at openknowledge.de
Charles Moulliard cmoulliard at gmail.com
Cody Lerum cody.lerum at gmail.com
Romain Mannu-Buccau rmannibucau at gmail.com
Matthew Jason Benson mbenson at apache.org
Jim Jagielski jim at apache.org
David Blevins dblevins at apache.org
Ken Finnigan ken at kenfinnigan.me
John D. Ament johndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator DeltaSpike podling encumbered upon the Apache Incubator
Project are hereafter discharged.
https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
http://www.grobmeier.de
https://www.timeandbill.de
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] recommend Apache DeltaSpike for graduating out of the incubator
+1 (non-binding)
On 30/03/13 17:54, Mark Struberg wrote:
Hi!
The Apache DeltaSpike podling is a project which contains common CDI Extensions
which are portable among many different Java EE containers and even run on
standalone CDI containers.
We are now incubating since December 2011 and believe we are ready for
graduation. We've shipped 3 releases and already see wide adoption in the
industry.
We've already done an internal VOTE on the proposal which passed with a big
majority [1].
The voices who raised concerns were mainly afraid of DeltaSpike not being
'finished' yet. But graduation doesn't mean that the product is final and
switches to maintenance, but that it is vital and there is an active community
around it. And this is certainly the case as shown by the 21 votes we got the
last days.
Our status file [2] got updated recently and I consider the podling namesearch
task as completed [3].
Thus I'd like to ask the IPMC to VOTE on recommending the attached graduation
proposal to the board.
[+1] yes, go forward
[+0] meh, don't care
[-1] nope, because there's a blocker ${blocker_reason}
The VOTE is open for 72h
txs and LieGrue,
strub
[1] http://markmail.org/message/bmhr5woxidmgheco
[2] http://incubator.apache.org/projects/deltaspike.html
[3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-31
Proposed Board Resolution Report
X. Establish the Apache DeltaSpike 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 related to creating a set
of portable CDI (JSR-299) Extensions
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache DeltaSpike Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby is
responsible for the creation and maintenance of open-source
software related to creating a set of portable CDI Extensions;
and be it further
RESOLVED, that the office of Vice President, Apache DeltaSpike 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 DeltaSpike Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache DeltaSpike 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 DeltaSpike Project:
Gerhard Petracekgpetracek at apache.org
Mark Strubergstruberg at apache.org
Pete Muirpmuir at redhat.com
Jason Porterlightguard.jp at gmail.com
Shane Bryzaksbryzak at gmail.com
Rudy de Busscherrdebusscher at apache.org
Christian Kaltepothchristian at kaltepoth.de
Arne Limburgarne.limburg at openknowledge.de
Charles Moulliardcmoulliard at gmail.com
Cody Lerumcody.lerum at gmail.com
Romain Mannu-Buccaurmannibucau at gmail.com
Matthew Jason Bensonmbenson at apache.org
Jim Jagielskijim at apache.org
David Blevinsdblevins at apache.org
Ken Finniganken at kenfinnigan.me
John D. Amentjohndament at apache.org
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mark Struberg
be appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike 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 DeltaSpike Project; and be it further
RESOLVED, that the Apache DeltaSpike Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator DeltaSpike podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator DeltaSpike podling encumbered upon the Apache Incubator
Project are hereafter discharged.
https://cwiki.apache.org/confluence/display/DeltaSpike/Graduation+Proposal
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
