You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Ulrich Stärk <ul...@spielviel.de> on 2010/05/27 19:56:24 UTC
[VOTE] Tapestry bylaws
I believe that it is a good idea to give us some guidelines, document how we work, what roles there
are in our community and generally make some things more transparent that were formerly only known
as hearsay or documented in different places.
The document attached below is the result we came up with. If the vote is successful, the Tapestry
project will give itself the following bylaws. Concensus vote to run for 72 hours.
Ulrich Stärk: +1 (non-binding)
Introduction
The Tapestry Project Management Committee is the governing body of the Apache Tapestry project. The
PMC as a whole controls the project by being responsible for the direction and the success of the
project. The chairperson of the PMC is also a Vice President of the Apache Software Foundation and
serves as an interface between the Board of Directors and the project. The current chairman is
Howard Lewis Ship. A list of the current PMC members and committers can be found [here].
Roles
Everybody can help, regardless of their role. We differentiate roles inside the Tapestry community
by how committed people are to the project, how much they have contributed and how well they have
proven to be able to collaborate with the rest of the community. Long term community members with a
backlog of valuable contributions may obtain the right to commit to the source code repository and vote.
Users
This group is by far the largest and most important one. Users are the actual users of the Tapestry
framework. Without the users there would be no Tapestry project. Users use our product, ask and
answer questions on the mailing lists and submit bug reports and feature requests.
Contributors
Contributors are users that contribute to the project in the form of patches and documentation. They
are also participating in discussions on the developer mailing list and are providing suggestions
and criticism.
Committers
If a contributor contributes frequently to the project he may be granted write access to the source
code repository. In order for a contributor to become a committer, any other committer may nominate
him or the contributor himself may ask for it, resulting in a vote. If there are at least 3 binding
positive votes and no binding negative vote (concensus vote), the contributor is converted into a
committer. If a committer doesn't participate in the project anymore and shows so by not posting to
the mailing lists for 6 months or more, his write access to the source code repository will be
revoked. It may be re-requested at any point in the future by writing an email to the developer
mailing list.
PMC Members
A committer that has proven to be truely committed to the project and has proven to be able to work
well together with the rest of the developer community, especially in conflict situations, may be
invited to become part of the Project Management Committee. Every PMC member may nominate a
committer to become a PMC member. The nominee has to be approved by a concensus vote (i.e. at least
3 binding +1 votes, no binding vetos). A PMC member may resign from his position at any time,
maintaining his status as a committer. PMC members may also be removed from the PMC by a 3/4
concensus vote (i.e. at least 3 binding +1 votes and at least 3/4 of all binding votes, no binding
vetos). If a PMC member doesn't participate in the project anymore and shows so by not posting to
the mailing lists for 6 months or more, his status is converted to that of a committer.
PMC Chair
The chairperson of the PMC serves as a liaison to the Board of Directors of the ASF. The PMC chair
is elected with a 3/4 concensus vote and may resign from his position at any time, maintaining his
status as a PMC member.
Decision Making
Decisions are made by voting. Votes are expressed as numbers with +1 meaning 'yes', 0 meaning 'I
don't agree but I also won't veto it' or 'I don't have an opinion' and -1 meaning 'no' and in some
cases representing a veto. We differentiate two kinds of votes and three kinds of voting styles.
Votes: Binding votes are votes cast by members of the PMC. They are the ones that count since it is
the PMC that governs the project and answers to the Board of Directors. Votes by committers and
contributors are non-binding and are indicative or advisory.
Voting styles:
Majority vote: There are at least 3 binding +1 votes and more +1 than -1 votes.
Concensus vote: There are at least 3 binding +1 votes and no binding veto (-1). If a veto is cast,
the person casting it has to immediately explain the reason for his veto. An unexplained veto is
invalid. A veto cannot be overruled.
Lazy concensus: If there are no objections against a decision within a given period, the decision
counts as accepted
Votes may be changed during the voting period.
When to vote with what voting style
A change to the codebase or the documentation, i.e. a commit message or a wiki diff message on the
developer mailing list automatically triggers a lazy consensus vote. If there are no objections
within 72 hours, the change counts as agreed on.
Changes to the codebase affecting backwards compatibility or altering the current expected behaviour
of the product should be discussed on the developer mailing list first and should be voted on with a
majority vote. The same holds for major changes to the codebase that don't affect the user.
Committers and PMC members will be voted in as explained above.
A release always requires a concensus vote.
Changes to this document need a 3/4 concensus vote (i.e. at least 3 binding +1 votes and at least
3/4 of all binding votes, no binding vetos).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Howard Lewis Ship <hl...@gmail.com>.
Howard M. Lewis Ship: +1 (binding)
I agree with Andreas note; we may need to put this on hold, and run
vote(s) to clear out inactive PMC members first.
On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Take a look at the "When to vote with what voting style" section. I agree
> that most of it is just how Apache project work, but there are some parts
> that are specific for Tapestry.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Kristian Marinkovic <kr...@porsche.co.at>.
+1 (non-binding)
Von: Ulrich Stärk <ul...@spielviel.de>
An: Tapestry development <de...@tapestry.apache.org>
Datum: 28.05.2010 10:16
Betreff: Re: [VOTE] Tapestry bylaws
That's nothing to do with bureaucracy. It's meant to be a summary of how
we do things here anyways,
to make our processes more transparent to others and thus encouraging them
to participate. Without
that recorded knowledge it might take outsiders months to fully understand
how we work and in that
time distracting them from contributing. Additionally I hoped to clarify
some things for ourselves
as well since there seemed to be some misunderstandings among us e.g.
concerning binding and
non-binding votes and who is allowed to cast them and what they mean.
Uli
On 28.05.2010 04:08, Jesse Kuhnert wrote:
> Yeah geez, you guys sound like a bunch of beurocrats right now. Who
> cares? How is the project doing?
>
> On Thursday, May 27, 2010, Kalle Korhonen<ka...@gmail.com>
wrote:
>> I did take a look at it earlier. Before I was thinking that it doesn't
>> really change anything because technically any change triggers a lazy
>> consensus vote, but still, it seems a little voting happy. What
>> happens if somebody votes -1 +71 hours after commit? The commit needs
>> to be automatically reverted back? The issue with automated triggering
>> of lazy consensus votes is that there's nobody to gather the results.
>> Of course, most of the time it doesn't matter but then again, what's
>> the point of spelling it out explicitly? The existing Apache rules are
>> minimal but good enough and worked for multiple projects for years.
>> Overall, I'd say I prefer not voting for everything but "just get it
>> done" attitude and explicit voting when needed. However, if community
>> finds these rules are needed that's ok with me, thus still +0
>> (non-binding).
>>
>> Kalle
>>
>>
>> On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
>> <th...@gmail.com> wrote:
>>> Take a look at the "When to vote with what voting style" section. I
agree
>>> that most of it is just how Apache project work, but there are some
parts
>>> that are specific for Tapestry.
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Independent Java, Apache Tapestry 5 and Hibernate consultant,
developer, and
>>> instructor
>>> Owner, Ars Machina Tecnologia da Informação Ltda.
>>> http://www.arsmachina.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Ulrich Stärk <ul...@spielviel.de>.
That's nothing to do with bureaucracy. It's meant to be a summary of how we do things here anyways,
to make our processes more transparent to others and thus encouraging them to participate. Without
that recorded knowledge it might take outsiders months to fully understand how we work and in that
time distracting them from contributing. Additionally I hoped to clarify some things for ourselves
as well since there seemed to be some misunderstandings among us e.g. concerning binding and
non-binding votes and who is allowed to cast them and what they mean.
Uli
On 28.05.2010 04:08, Jesse Kuhnert wrote:
> Yeah geez, you guys sound like a bunch of beurocrats right now. Who
> cares? How is the project doing?
>
> On Thursday, May 27, 2010, Kalle Korhonen<ka...@gmail.com> wrote:
>> I did take a look at it earlier. Before I was thinking that it doesn't
>> really change anything because technically any change triggers a lazy
>> consensus vote, but still, it seems a little voting happy. What
>> happens if somebody votes -1 +71 hours after commit? The commit needs
>> to be automatically reverted back? The issue with automated triggering
>> of lazy consensus votes is that there's nobody to gather the results.
>> Of course, most of the time it doesn't matter but then again, what's
>> the point of spelling it out explicitly? The existing Apache rules are
>> minimal but good enough and worked for multiple projects for years.
>> Overall, I'd say I prefer not voting for everything but "just get it
>> done" attitude and explicit voting when needed. However, if community
>> finds these rules are needed that's ok with me, thus still +0
>> (non-binding).
>>
>> Kalle
>>
>>
>> On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
>> <th...@gmail.com> wrote:
>>> Take a look at the "When to vote with what voting style" section. I agree
>>> that most of it is just how Apache project work, but there are some parts
>>> that are specific for Tapestry.
>>>
>>> --
>>> Thiago H. de Paula Figueiredo
>>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
>>> instructor
>>> Owner, Ars Machina Tecnologia da Informação Ltda.
>>> http://www.arsmachina.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Charith Madusanka <ch...@gmail.com>.
This is great ......... This will great help to newcomer...
Charith Madusanka : +1 (non-binding)
On Fri, May 28, 2010 at 7:38 AM, Jesse Kuhnert <jk...@gmail.com> wrote:
> Yeah geez, you guys sound like a bunch of beurocrats right now. Who
> cares? How is the project doing?
>
> On Thursday, May 27, 2010, Kalle Korhonen <ka...@gmail.com>
> wrote:
> > I did take a look at it earlier. Before I was thinking that it doesn't
> > really change anything because technically any change triggers a lazy
> > consensus vote, but still, it seems a little voting happy. What
> > happens if somebody votes -1 +71 hours after commit? The commit needs
> > to be automatically reverted back? The issue with automated triggering
> > of lazy consensus votes is that there's nobody to gather the results.
> > Of course, most of the time it doesn't matter but then again, what's
> > the point of spelling it out explicitly? The existing Apache rules are
> > minimal but good enough and worked for multiple projects for years.
> > Overall, I'd say I prefer not voting for everything but "just get it
> > done" attitude and explicit voting when needed. However, if community
> > finds these rules are needed that's ok with me, thus still +0
> > (non-binding).
> >
> > Kalle
> >
> >
> > On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
> > <th...@gmail.com> wrote:
> >> Take a look at the "When to vote with what voting style" section. I
> agree
> >> that most of it is just how Apache project work, but there are some
> parts
> >> that are specific for Tapestry.
> >>
> >> --
> >> Thiago H. de Paula Figueiredo
> >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and
> >> instructor
> >> Owner, Ars Machina Tecnologia da Informação Ltda.
> >> http://www.arsmachina.com.br
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [VOTE] Tapestry bylaws
Posted by Jesse Kuhnert <jk...@gmail.com>.
Yeah geez, you guys sound like a bunch of beurocrats right now. Who
cares? How is the project doing?
On Thursday, May 27, 2010, Kalle Korhonen <ka...@gmail.com> wrote:
> I did take a look at it earlier. Before I was thinking that it doesn't
> really change anything because technically any change triggers a lazy
> consensus vote, but still, it seems a little voting happy. What
> happens if somebody votes -1 +71 hours after commit? The commit needs
> to be automatically reverted back? The issue with automated triggering
> of lazy consensus votes is that there's nobody to gather the results.
> Of course, most of the time it doesn't matter but then again, what's
> the point of spelling it out explicitly? The existing Apache rules are
> minimal but good enough and worked for multiple projects for years.
> Overall, I'd say I prefer not voting for everything but "just get it
> done" attitude and explicit voting when needed. However, if community
> finds these rules are needed that's ok with me, thus still +0
> (non-binding).
>
> Kalle
>
>
> On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
> <th...@gmail.com> wrote:
>> Take a look at the "When to vote with what voting style" section. I agree
>> that most of it is just how Apache project work, but there are some parts
>> that are specific for Tapestry.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
>> instructor
>> Owner, Ars Machina Tecnologia da Informação Ltda.
>> http://www.arsmachina.com.br
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Kalle Korhonen <ka...@gmail.com>.
I did take a look at it earlier. Before I was thinking that it doesn't
really change anything because technically any change triggers a lazy
consensus vote, but still, it seems a little voting happy. What
happens if somebody votes -1 +71 hours after commit? The commit needs
to be automatically reverted back? The issue with automated triggering
of lazy consensus votes is that there's nobody to gather the results.
Of course, most of the time it doesn't matter but then again, what's
the point of spelling it out explicitly? The existing Apache rules are
minimal but good enough and worked for multiple projects for years.
Overall, I'd say I prefer not voting for everything but "just get it
done" attitude and explicit voting when needed. However, if community
finds these rules are needed that's ok with me, thus still +0
(non-binding).
Kalle
On Thu, May 27, 2010 at 4:01 PM, Thiago H. de Paula Figueiredo
<th...@gmail.com> wrote:
> Take a look at the "When to vote with what voting style" section. I agree
> that most of it is just how Apache project work, but there are some parts
> that are specific for Tapestry.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Take a look at the "When to vote with what voting style" section. I agree
that most of it is just how Apache project work, but there are some parts
that are specific for Tapestry.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Kalle Korhonen <ka...@gmail.com>.
+0. Sorry I must be a bit slow, but Ulrich can you clarify the purpose
for me? Looks to me these are just re-hashing the existing Apache
rules. Do these differ in any way? Whether this vote is successful or
not, the project is still bound by the governing rules for all Apache
projects. Is the main purpose to clarify out-voting rules for PMC
members and committers? I'd link to the documents below and clearly
spell out the differences if any:
http://www.apache.org/foundation/voting.html
http://www.apache.org/dev/pmc.html
Kalle
On Thu, May 27, 2010 at 10:56 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I believe that it is a good idea to give us some guidelines, document how we
> work, what roles there are in our community and generally make some things
> more transparent that were formerly only known as hearsay or documented in
> different places.
>
> The document attached below is the result we came up with. If the vote is
> successful, the Tapestry project will give itself the following bylaws.
> Concensus vote to run for 72 hours.
>
> Ulrich Stärk: +1 (non-binding)
>
> Introduction
>
> The Tapestry Project Management Committee is the governing body of the
> Apache Tapestry project. The PMC as a whole controls the project by being
> responsible for the direction and the success of the project. The
> chairperson of the PMC is also a Vice President of the Apache Software
> Foundation and serves as an interface between the Board of Directors and the
> project. The current chairman is Howard Lewis Ship. A list of the current
> PMC members and committers can be found [here].
>
> Roles
>
> Everybody can help, regardless of their role. We differentiate roles inside
> the Tapestry community by how committed people are to the project, how much
> they have contributed and how well they have proven to be able to
> collaborate with the rest of the community. Long term community members with
> a backlog of valuable contributions may obtain the right to commit to the
> source code repository and vote.
>
> Users
>
> This group is by far the largest and most important one. Users are the
> actual users of the Tapestry framework. Without the users there would be no
> Tapestry project. Users use our product, ask and answer questions on the
> mailing lists and submit bug reports and feature requests.
>
> Contributors
>
> Contributors are users that contribute to the project in the form of patches
> and documentation. They are also participating in discussions on the
> developer mailing list and are providing suggestions and criticism.
>
> Committers
>
> If a contributor contributes frequently to the project he may be granted
> write access to the source code repository. In order for a contributor to
> become a committer, any other committer may nominate him or the contributor
> himself may ask for it, resulting in a vote. If there are at least 3 binding
> positive votes and no binding negative vote (concensus vote), the
> contributor is converted into a committer. If a committer doesn't
> participate in the project anymore and shows so by not posting to the
> mailing lists for 6 months or more, his write access to the source code
> repository will be revoked. It may be re-requested at any point in the
> future by writing an email to the developer mailing list.
>
> PMC Members
>
> A committer that has proven to be truely committed to the project and has
> proven to be able to work well together with the rest of the developer
> community, especially in conflict situations, may be invited to become part
> of the Project Management Committee. Every PMC member may nominate a
> committer to become a PMC member. The nominee has to be approved by a
> concensus vote (i.e. at least 3 binding +1 votes, no binding vetos). A PMC
> member may resign from his position at any time, maintaining his status as a
> committer. PMC members may also be removed from the PMC by a 3/4 concensus
> vote (i.e. at least 3 binding +1 votes and at least 3/4 of all binding
> votes, no binding vetos). If a PMC member doesn't participate in the project
> anymore and shows so by not posting to the mailing lists for 6 months or
> more, his status is converted to that of a committer.
>
>
> PMC Chair
>
> The chairperson of the PMC serves as a liaison to the Board of Directors of
> the ASF. The PMC chair is elected with a 3/4 concensus vote and may resign
> from his position at any time, maintaining his status as a PMC member.
>
> Decision Making
>
> Decisions are made by voting. Votes are expressed as numbers with +1 meaning
> 'yes', 0 meaning 'I don't agree but I also won't veto it' or 'I don't have
> an opinion' and -1 meaning 'no' and in some cases representing a veto. We
> differentiate two kinds of votes and three kinds of voting styles.
>
> Votes: Binding votes are votes cast by members of the PMC. They are the ones
> that count since it is the PMC that governs the project and answers to the
> Board of Directors. Votes by committers and contributors are non-binding and
> are indicative or advisory.
>
> Voting styles:
>
> Majority vote: There are at least 3 binding +1 votes and more +1 than -1
> votes.
>
> Concensus vote: There are at least 3 binding +1 votes and no binding veto
> (-1). If a veto is cast, the person casting it has to immediately explain
> the reason for his veto. An unexplained veto is invalid. A veto cannot be
> overruled.
>
> Lazy concensus: If there are no objections against a decision within a given
> period, the decision counts as accepted
>
> Votes may be changed during the voting period.
>
>
> When to vote with what voting style
>
> A change to the codebase or the documentation, i.e. a commit message or a
> wiki diff message on the developer mailing list automatically triggers a
> lazy consensus vote. If there are no objections within 72 hours, the change
> counts as agreed on.
>
> Changes to the codebase affecting backwards compatibility or altering the
> current expected behaviour of the product should be discussed on the
> developer mailing list first and should be voted on with a majority vote.
> The same holds for major changes to the codebase that don't affect the user.
>
> Committers and PMC members will be voted in as explained above.
>
> A release always requires a concensus vote.
>
> Changes to this document need a 3/4 concensus vote (i.e. at least 3 binding
> +1 votes and at least 3/4 of all binding votes, no binding vetos).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Christian Edward Gruber <ch...@gmail.com>.
+1 (non-binding)
These is a pretty clear codification of what I've seen as the actual
behaviour of this group.
Christian.
On May 27, 2010, at 1:56 PM, Ulrich Stärk wrote:
> I believe that it is a good idea to give us some guidelines,
> document how we work, what roles there are in our community and
> generally make some things more transparent that were formerly only
> known as hearsay or documented in different places.
>
> The document attached below is the result we came up with. If the
> vote is successful, the Tapestry project will give itself the
> following bylaws. Concensus vote to run for 72 hours.
>
> Ulrich Stärk: +1 (non-binding)
>
> Introduction
>
> The Tapestry Project Management Committee is the governing body of
> the Apache Tapestry project. The PMC as a whole controls the project
> by being responsible for the direction and the success of the
> project. The chairperson of the PMC is also a Vice President of the
> Apache Software Foundation and serves as an interface between the
> Board of Directors and the project. The current chairman is Howard
> Lewis Ship. A list of the current PMC members and committers can be
> found [here].
>
> Roles
>
> Everybody can help, regardless of their role. We differentiate roles
> inside the Tapestry community by how committed people are to the
> project, how much they have contributed and how well they have
> proven to be able to collaborate with the rest of the community.
> Long term community members with a backlog of valuable contributions
> may obtain the right to commit to the source code repository and vote.
>
> Users
>
> This group is by far the largest and most important one. Users are
> the actual users of the Tapestry framework. Without the users there
> would be no Tapestry project. Users use our product, ask and answer
> questions on the mailing lists and submit bug reports and feature
> requests.
>
> Contributors
>
> Contributors are users that contribute to the project in the form of
> patches and documentation. They are also participating in
> discussions on the developer mailing list and are providing
> suggestions and criticism.
>
> Committers
>
> If a contributor contributes frequently to the project he may be
> granted write access to the source code repository. In order for a
> contributor to become a committer, any other committer may nominate
> him or the contributor himself may ask for it, resulting in a vote.
> If there are at least 3 binding positive votes and no binding
> negative vote (concensus vote), the contributor is converted into a
> committer. If a committer doesn't participate in the project anymore
> and shows so by not posting to the mailing lists for 6 months or
> more, his write access to the source code repository will be
> revoked. It may be re-requested at any point in the future by
> writing an email to the developer mailing list.
>
> PMC Members
>
> A committer that has proven to be truely committed to the project
> and has proven to be able to work well together with the rest of the
> developer community, especially in conflict situations, may be
> invited to become part of the Project Management Committee. Every
> PMC member may nominate a committer to become a PMC member. The
> nominee has to be approved by a concensus vote (i.e. at least 3
> binding +1 votes, no binding vetos). A PMC member may resign from
> his position at any time, maintaining his status as a committer. PMC
> members may also be removed from the PMC by a 3/4 concensus vote
> (i.e. at least 3 binding +1 votes and at least 3/4 of all binding
> votes, no binding vetos). If a PMC member doesn't participate in the
> project anymore and shows so by not posting to the mailing lists for
> 6 months or more, his status is converted to that of a committer.
>
>
> PMC Chair
>
> The chairperson of the PMC serves as a liaison to the Board of
> Directors of the ASF. The PMC chair is elected with a 3/4 concensus
> vote and may resign from his position at any time, maintaining his
> status as a PMC member.
>
> Decision Making
>
> Decisions are made by voting. Votes are expressed as numbers with +1
> meaning 'yes', 0 meaning 'I don't agree but I also won't veto it' or
> 'I don't have an opinion' and -1 meaning 'no' and in some cases
> representing a veto. We differentiate two kinds of votes and three
> kinds of voting styles.
>
> Votes: Binding votes are votes cast by members of the PMC. They are
> the ones that count since it is the PMC that governs the project and
> answers to the Board of Directors. Votes by committers and
> contributors are non-binding and are indicative or advisory.
>
> Voting styles:
>
> Majority vote: There are at least 3 binding +1 votes and more +1
> than -1 votes.
>
> Concensus vote: There are at least 3 binding +1 votes and no binding
> veto (-1). If a veto is cast, the person casting it has to
> immediately explain the reason for his veto. An unexplained veto is
> invalid. A veto cannot be overruled.
>
> Lazy concensus: If there are no objections against a decision within
> a given period, the decision counts as accepted
>
> Votes may be changed during the voting period.
>
>
> When to vote with what voting style
>
> A change to the codebase or the documentation, i.e. a commit message
> or a wiki diff message on the developer mailing list automatically
> triggers a lazy consensus vote. If there are no objections within 72
> hours, the change counts as agreed on.
>
> Changes to the codebase affecting backwards compatibility or
> altering the current expected behaviour of the product should be
> discussed on the developer mailing list first and should be voted on
> with a majority vote. The same holds for major changes to the
> codebase that don't affect the user.
>
> Committers and PMC members will be voted in as explained above.
>
> A release always requires a concensus vote.
>
> Changes to this document need a 3/4 concensus vote (i.e. at least 3
> binding +1 votes and at least 3/4 of all binding votes, no binding
> vetos).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Andreas Andreou <an...@di.uoa.gr>.
Andreas Andreou: +1 (binding)
On Fri, May 28, 2010 at 00:57, Andreas Andreou <an...@di.uoa.gr> wrote:
> +1 (binding)
>
> On Thu, May 27, 2010 at 23:57, Piero Sartini <li...@pierosartini.de> wrote:
>> +1 (non-binding)
>> This will help new users to quickly find their way around.
>>
>> Piero
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Andreas Andreou <an...@di.uoa.gr>.
+1 (binding)
On Thu, May 27, 2010 at 23:57, Piero Sartini <li...@pierosartini.de> wrote:
> +1 (non-binding)
> This will help new users to quickly find their way around.
>
> Piero
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Piero Sartini <li...@pierosartini.de>.
+1 (non-binding)
This will help new users to quickly find their way around.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[FAILURE] Tapestry bylaws
Posted by Ulrich Stärk <ul...@spielviel.de>.
The justified concern was raised that we can't pass bylaws that need a 3/4 majority for changes with
a "normal" concensus vote. Since we currently won't get a 3/4 participation of all PMC members due
to inactivity we started a vote to clean up the list of PMC members and convert inactive PMC members
to normal committers. Once this vote is over, we will re-run the vote for these bylaws.
Cheers,
Uli
binding votes:
Thiago H. de Paula Figueiredo: +1 (binding)
Andreas Andreou: +1 (binding)
Howard M. Lewis Ship: +1 (binding)
non-binding votes:
Ulrich Stärk: +1 (non-binding)
Christian Edward Gruber: +1 (non-binding)
Daniel Jue: +1 (non binding)
Piero Sartini: +1 (non-binding)
Kalle Korhonnen: +0 (non-binding)
Charith Madusanka: +1 (non-binding)
Kristian Marinkovic: +1 (non-binding)
On 27.05.2010 19:56, Ulrich Stärk wrote:
> I believe that it is a good idea to give us some guidelines, document
> how we work, what roles there are in our community and generally make
> some things more transparent that were formerly only known as hearsay or
> documented in different places.
>
> The document attached below is the result we came up with. If the vote
> is successful, the Tapestry project will give itself the following
> bylaws. Concensus vote to run for 72 hours.
>
> Ulrich Stärk: +1 (non-binding)
>
> Introduction
>
> The Tapestry Project Management Committee is the governing body of the
> Apache Tapestry project. The PMC as a whole controls the project by
> being responsible for the direction and the success of the project. The
> chairperson of the PMC is also a Vice President of the Apache Software
> Foundation and serves as an interface between the Board of Directors and
> the project. The current chairman is Howard Lewis Ship. A list of the
> current PMC members and committers can be found [here].
>
> Roles
>
> Everybody can help, regardless of their role. We differentiate roles
> inside the Tapestry community by how committed people are to the
> project, how much they have contributed and how well they have proven to
> be able to collaborate with the rest of the community. Long term
> community members with a backlog of valuable contributions may obtain
> the right to commit to the source code repository and vote.
>
> Users
>
> This group is by far the largest and most important one. Users are the
> actual users of the Tapestry framework. Without the users there would be
> no Tapestry project. Users use our product, ask and answer questions on
> the mailing lists and submit bug reports and feature requests.
>
> Contributors
>
> Contributors are users that contribute to the project in the form of
> patches and documentation. They are also participating in discussions on
> the developer mailing list and are providing suggestions and criticism.
>
> Committers
>
> If a contributor contributes frequently to the project he may be granted
> write access to the source code repository. In order for a contributor
> to become a committer, any other committer may nominate him or the
> contributor himself may ask for it, resulting in a vote. If there are at
> least 3 binding positive votes and no binding negative vote (concensus
> vote), the contributor is converted into a committer. If a committer
> doesn't participate in the project anymore and shows so by not posting
> to the mailing lists for 6 months or more, his write access to the
> source code repository will be revoked. It may be re-requested at any
> point in the future by writing an email to the developer mailing list.
>
> PMC Members
>
> A committer that has proven to be truely committed to the project and
> has proven to be able to work well together with the rest of the
> developer community, especially in conflict situations, may be invited
> to become part of the Project Management Committee. Every PMC member may
> nominate a committer to become a PMC member. The nominee has to be
> approved by a concensus vote (i.e. at least 3 binding +1 votes, no
> binding vetos). A PMC member may resign from his position at any time,
> maintaining his status as a committer. PMC members may also be removed
> from the PMC by a 3/4 concensus vote (i.e. at least 3 binding +1 votes
> and at least 3/4 of all binding votes, no binding vetos). If a PMC
> member doesn't participate in the project anymore and shows so by not
> posting to the mailing lists for 6 months or more, his status is
> converted to that of a committer.
>
>
> PMC Chair
>
> The chairperson of the PMC serves as a liaison to the Board of Directors
> of the ASF. The PMC chair is elected with a 3/4 concensus vote and may
> resign from his position at any time, maintaining his status as a PMC
> member.
>
> Decision Making
>
> Decisions are made by voting. Votes are expressed as numbers with +1
> meaning 'yes', 0 meaning 'I don't agree but I also won't veto it' or 'I
> don't have an opinion' and -1 meaning 'no' and in some cases
> representing a veto. We differentiate two kinds of votes and three kinds
> of voting styles.
>
> Votes: Binding votes are votes cast by members of the PMC. They are the
> ones that count since it is the PMC that governs the project and answers
> to the Board of Directors. Votes by committers and contributors are
> non-binding and are indicative or advisory.
>
> Voting styles:
>
> Majority vote: There are at least 3 binding +1 votes and more +1 than -1
> votes.
>
> Concensus vote: There are at least 3 binding +1 votes and no binding
> veto (-1). If a veto is cast, the person casting it has to immediately
> explain the reason for his veto. An unexplained veto is invalid. A veto
> cannot be overruled.
>
> Lazy concensus: If there are no objections against a decision within a
> given period, the decision counts as accepted
>
> Votes may be changed during the voting period.
>
>
> When to vote with what voting style
>
> A change to the codebase or the documentation, i.e. a commit message or
> a wiki diff message on the developer mailing list automatically triggers
> a lazy consensus vote. If there are no objections within 72 hours, the
> change counts as agreed on.
>
> Changes to the codebase affecting backwards compatibility or altering
> the current expected behaviour of the product should be discussed on the
> developer mailing list first and should be voted on with a majority
> vote. The same holds for major changes to the codebase that don't affect
> the user.
>
> Committers and PMC members will be voted in as explained above.
>
> A release always requires a concensus vote.
>
> Changes to this document need a 3/4 concensus vote (i.e. at least 3
> binding +1 votes and at least 3/4 of all binding votes, no binding vetos).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [VOTE] Tapestry bylaws
Posted by Daniel Jue <te...@gmail.com>.
Daniel Jue: +1 (non binding)
Nice to have it all the rules in one spot.
On Thu, May 27, 2010 at 4:33 PM, Thiago H. de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> Thiago H. de Paula Figueiredo: +1 (binding)
>
> Very well-written. ;)
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> and instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: [VOTE] Tapestry bylaws
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Thiago H. de Paula Figueiredo: +1 (binding)
Very well-written. ;)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org