You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Frank W. Zammetti" <fz...@omnytex.com> on 2006/04/25 05:10:17 UTC

Proposal for change

Dear Struts community,


We have seen a rash of what most people consider "noise" on these lists 
recently, and I can't deny that I was even part of some of it (although 
I hope somewhat more constructively than some).  However, underlying the 
"noise" I feel were a few valid points worth considering.  I for one have.

What I've come away with is a proposal I would like to make.  It would 
represent a procedural change of sorts, or addition to be more accurate. 
  I ask that anyone who has a thought on it please feel free to comment, 
but I ask that you try and do so constructively.  It is not my intention 
to start another 200-post thread that quickly devolves into name-calling 
and insults.

Also, please try not to get hung up on all the details, because they are 
debatable and negotiable (although I have tried to make them reasonable 
to start with).  The two principles described in the conclusion are what 
is really important.  The details of how this would work can be adjusted 
to make everyone happy.


A proposal for community-based committer nominations
----------------------------------------------------

* Rationale
One of the issues that a number of people seem to have with the way 
Struts has progressed is the seeming inability (or difficulty at least) 
of getting "new blood" involved.  There seems to be a perception by many 
that there is a bit of a "closed club" mentality with regard to being 
invited in as a committer and that the Struts community at large has no 
say in the matter.

* Proposed Change:
First, let me make clear that this proposal does NOT change the existing 
mechanism by which someone is invited to be a committer.  That decision 
still rests soley with the PMC.  This proposal only seeks to build on 
top of that mechanism.  I propose that a community-based nomination 
process be instituted.  For the sake of discussion, a "qualified" person 
is anyone that has been on the Struts Dev and/or User mailing lists for 
at least 6 months and has been relatively active (say, at minimum, 2 
posts per week total).  Any qualified person is eligible for nomination, 
or to nominate someone else.  Naturally, a person could never nominate 
themselves.  A nomination must then be seconded by another qualified 
person.  At that point, a voting period of one week commences, where any 
non-committer and non-PMC member, "qualified" or not, may vote (the 
usual +1, 0, -1).  The original nominator is responsible for tallying 
the vote.  A person must receive at least 60% +1's (i.e., 6 out of 10 
must be +1) and no more than half of the remainder may be negative.  At 
the end of that one week period, the vote results will be posted to the 
Dev list and a similar one week period will commence where existing 
Struts team members vote for the nominee.  Also note that at any point, 
the nominee can decline the nomination.  We wouldn't want to offer 
someone up that doesn't want to job!

* Conclusion:
Once again, let me make perfectly clear that the existing PMC still 
retains 100% control over who is invited to join.  This proposal only 
serves to introduce a mechanism by which members of the community can be 
nominated and force a vote by the PMC.  That is of course the first 
important principle of this proposal.  The other important principle is 
taking the will of the community into account.  By having the PMC not 
vote until AFTER the community has voted, the "will of the community" 
should be apparent, and the idea is that the PMC will take that into 
account when voting.  The community will then have a clear indication 
whether they have been listened to or not based on the outcome of the 
vote (and the comments made during the vote because, after all, there 
ould be legitimate reasons not to adhere to the community's vote, and 
hose reasons should come out in discussion).  But, at the end of the 
day, who is invited to join is still decided by the PMC, as it is today.


I look forward to feedback.  Thanks for listening!

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Proposal for change

Posted by Kimani Darisha <kd...@gmail.com>.
The only thing assinine here is that people keep repying to these damn
trolls!!!!

If you ignore trolls, they go away.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
What is stupid or assinine is to suggest that the problem is that I cannot
count.  That is typical of you snipers.  You do everything to avoid the real
issues.  Look at the entries for Reddin and look at the entries for other
people.  In my opinion you have to be addled not to see that he is brought
on for Shale and not for Struts.

On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>
> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> >
> > This is the kind of stupid, assinine comment
>
>
> What is stupid or assinine about pointing out that your count is
> incorrect?
> It *is* incorrect. You counted 4 posts to the dev list. To quote you
> directly:
>
> "I count four (4) posts to the dev list in Greg Reddin's history"
>
> I provided a URL which demonstrates that that statement is incorrect.
>
> --
> Martin Cooper
>
>
> that is really what trolling is
> > all about. There are clearly more than I found by doing a general search
> > for
> > Redding.  Try doing one for Frank and see what happens, Martin.  I
> really
> > could vomit when I hear that feminine English "pity".
> >
> > On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
> > >
> > > On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> > > >
> > > > Here is a case in point:  I count four (4) posts to the dev list in
> > Greg
> > > > Reddin's history.
> > >
> > >
> > > Pity you can't count.
> > >
> > > http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > >   He is a committer.  On the user list there is also
> > > > virtually nothing.  What stands out is that he was interested in a
> > > couple
> > > > of
> > > > posts in Shale.  What is the possible reason he is a committer and
> > Frank
> > > > is
> > > > not?  Is this the Way Different Struts-Apache Way.  This is
> crazy!  Do
> > > > people actually believe Ted and Craig?
> > > >
> > > > On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
> > > > >
> > > > >
> > > > > On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
> > > > >
> > > > > > That depends entirely on your meaning of the word "closed".  You
> > > > > > make the
> > > > > > argument that the number of new committers means it isn't
> closed,
> > > > > > and I
> > > > > > agree with you to a degree.  But that's not the only meaning of
> > > > > > "closed"... the invitations to those people came *soley* from
> the
> > > PMC
> > > > > > AFAIK... the community had no say in it.  That's the thing my
> > > proposal
> > > > > > seeks to address, that the initiation of someone being invited
> > > doesn't
> > > > > > necessarily have to come from those already there (although they
> > > would
> > > > > > still have the final say-so).
> > > > >
> > > > > I have some serious concerns about this.  Let me just use myself
> as
> > > > > an example.  I've been a committer for about 6 months or so.  I
> have
> > > > > absolutely no idea what sort of discussion took place before I
> > > > > received that invitation.  If there was someone among the PMC who
> > was
> > > > > vehemently opposed to my nomination I'm glad they had a
> confidential
> > > > > forum in which to discuss their concerns.  Now that I am a
> committer
> > > > > I can have an unbiased conversation with anybody else in the group
> > > > > without any preconceived notion of what that individual's opinion
> of
> > > > > me might be.  Truly, I don't have confidence that either user@ or
> > > > > dev@ is a place where concerns can be expressed openly without
> fear
> > > > > of unprofessional response.  It's just too easy for this kind of
> > > > > discussion to turn into personal attacks in a forum such as user@
> or
> > > > > even dev@.
> > > > >
> > > > > When Struts was a Jakarta subproject I remember committer votes
> > > > > taking place on dev@.  I always felt just a little uneasy about
> it.
> > > > > 99 times out of 100 it was a unanimous +1 with no discussion.  But
> I
> > > > > seem to recall at least one case when concerns were expressed
> > (sorry,
> > > > > I don't remember the specifics, please correct me if I'm
> wrong).  I
> > > > > feel really bad that this person's personal merit would have to be
> > > > > discussed in a public forum.  I understand some others' concerns
> > > > > about the community appearing to be closed, but I think there
> should
> > > > > be a barrier to entry.  Maybe it's too high, but it seems to me
> that
> > > > > it should exist.  After all it's basically a lifetime appointment
> > and
> > > > > revocations are very rare if one has ever happened at all.
> > > > >
> > > > > Greg
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > > > For additional commands, e-mail: dev-help@struts.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > "You can lead a horse to water but you cannot make it float on its
> > > back."
> > > > ~Dakota Jack~
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > "You can lead a horse to water but you cannot make it float on its
> back."
> > ~Dakota Jack~
> >
> >
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Wed, April 26, 2006 8:01 am, Jonathan Revusky said:
> On Frank Z., the equivalent numbers I get are:
>
> 1231 on struts-user and 381 on struts-devel  1612 total.
>
> To see how I searched, see, for example:
>
> http://search.gmane.org/?query=&email=Frank+Zammetti&group=gmane.comp.jakarta.struts.devel&sort=date&DEFAULTOP=and&xFILTERS=Gcomp.jakarta.struts.user-Afrank+zammetti---A
>
> Dakota's point, that Frank was much more active in the community does
> seem to stand. We're talking 3 binary orders of magnitude here.
>
> Note that I'm not saying that this is some definitive proof of anything
> either. But I think it's fair to say that there is a real lack of
> clarity as to who gets admitted to the club and who doesn't.

I really don't want this to be a discussion about me per se, but... it
should be noted in fairness that none of my submitted patches (or
preliminary code that would have lead to patches) has ever been accepted. 
One could argue that since none of my code has ever been committed, it
makes sense that I would not have been invited.  I can live with that, it
seems logical to me.

I'm really not interested in comparing myself to anyone else... I looked
at my own numbers out of curiosity rather than wanting to make a point...
I am more than comfortable with my contributions to this community, and I
think anyone looking at what I've done over the past two years with a
subjective eye would see that my influence and input has been far more
positive than negative (overall... I'm not perfect mind you!)

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Kimani Darisha <kd...@gmail.com>.
The only thing assinine here is that people keep repying to these damn
trolls!!!!

If you ignore trolls, they go away.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Jonathan Revusky <re...@wanadoo.es>.
Jonathan Revusky wrote:
> Martin Cooper wrote:
> 
>> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>>
>>> This is the kind of stupid, assinine comment
>>
>>
>>
>>
>> What is stupid or assinine about pointing out that your count is 
>> incorrect?
>> It *is* incorrect. You counted 4 posts to the dev list. To quote you
>> directly:
>>
>> "I count four (4) posts to the dev list in Greg Reddin's history"
>>
>> I provided a URL which demonstrates that that statement is incorrect.
> 
> 
> <ROTFL>
> 
> But if the actual count is 3 instead of 4, that reinforces Dakota's 
> point, doesn't it? (And even if it was 7 or 8....sheesh....

Oops, I made a mistake. I misread the page Martin pointed to. Greg has 
posted quite a bit more than 3 or 4 posts. So I have to retract the 
above comment.

Using search.gmane.org, I get for Greg:

102 on struts-user and 108 on struts-devel -- 210 total (I'm not sure 
I'm not double-counting here since some might be cross-posts.)

On Frank Z., the equivalent numbers I get are:

1231 on struts-user and 381 on struts-devel  1612 total.

To see how I searched, see, for example:

http://search.gmane.org/?query=&email=Frank+Zammetti&group=gmane.comp.jakarta.struts.devel&sort=date&DEFAULTOP=and&xFILTERS=Gcomp.jakarta.struts.user-Afrank+zammetti---A

Dakota's point, that Frank was much more active in the community does 
seem to stand. We're talking 3 binary orders of magnitude here.

Note that I'm not saying that this is some definitive proof of anything 
either. But I think it's fair to say that there is a real lack of 
clarity as to who gets admitted to the club and who doesn't. Also, the 
point stands that, whatever has been happening up until now has 
basically yielded dismal results and it makes perfect sense to ask 
certain questions about what has been going on.

> 
> You guys.... <sigh>
> 
> Jonathan Revusky
> -- 
> lead developer, FreeMarker project, http://freemarker.org/
> 
>>
>> -- 
>> Martin Cooper
>>
>>
>> that is really what trolling is
>>
>>> all about. There are clearly more than I found by doing a general search
>>> for
>>> Redding.  Try doing one for Frank and see what happens, Martin.  I 
>>> really
>>> could vomit when I hear that feminine English "pity".
>>>
>>> On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>>>
>>>> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>>>>
>>>>> Here is a case in point:  I count four (4) posts to the dev list in
>>>
>>>
>>> Greg
>>>
>>>>> Reddin's history.
>>>>
>>>>
>>>>
>>>> Pity you can't count.
>>>>
>>>> http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
>>>>
>>>> -- 
>>>> Martin Cooper
>>>>
>>>>
>>>>  He is a committer.  On the user list there is also
>>>>
>>>>> virtually nothing.  What stands out is that he was interested in a
>>>>
>>>>
>>>> couple
>>>>
>>>>> of
>>>>> posts in Shale.  What is the possible reason he is a committer and
>>>
>>>
>>> Frank
>>>
>>>>> is
>>>>> not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
>>>>> people actually believe Ted and Craig?
>>>>>
>>>>> On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
>>>>>
>>>>>>
>>>>>> On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
>>>>>>
>>>>>>
>>>>>>> That depends entirely on your meaning of the word "closed".  You
>>>>>>> make the
>>>>>>> argument that the number of new committers means it isn't closed,
>>>>>>> and I
>>>>>>> agree with you to a degree.  But that's not the only meaning of
>>>>>>> "closed"... the invitations to those people came *soley* from the
>>>>
>>>>
>>>> PMC
>>>>
>>>>>>> AFAIK... the community had no say in it.  That's the thing my
>>>>
>>>>
>>>> proposal
>>>>
>>>>>>> seeks to address, that the initiation of someone being invited
>>>>
>>>>
>>>> doesn't
>>>>
>>>>>>> necessarily have to come from those already there (although they
>>>>
>>>>
>>>> would
>>>>
>>>>>>> still have the final say-so).
>>>>>>
>>>>>>
>>>>>> I have some serious concerns about this.  Let me just use myself as
>>>>>> an example.  I've been a committer for about 6 months or so.  I have
>>>>>> absolutely no idea what sort of discussion took place before I
>>>>>> received that invitation.  If there was someone among the PMC who
>>>
>>>
>>> was
>>>
>>>>>> vehemently opposed to my nomination I'm glad they had a confidential
>>>>>> forum in which to discuss their concerns.  Now that I am a committer
>>>>>> I can have an unbiased conversation with anybody else in the group
>>>>>> without any preconceived notion of what that individual's opinion of
>>>>>> me might be.  Truly, I don't have confidence that either user@ or
>>>>>> dev@ is a place where concerns can be expressed openly without fear
>>>>>> of unprofessional response.  It's just too easy for this kind of
>>>>>> discussion to turn into personal attacks in a forum such as user@ or
>>>>>> even dev@.
>>>>>>
>>>>>> When Struts was a Jakarta subproject I remember committer votes
>>>>>> taking place on dev@.  I always felt just a little uneasy about it.
>>>>>> 99 times out of 100 it was a unanimous +1 with no discussion.  But I
>>>>>> seem to recall at least one case when concerns were expressed
>>>
>>>
>>> (sorry,
>>>
>>>>>> I don't remember the specifics, please correct me if I'm wrong).  I
>>>>>> feel really bad that this person's personal merit would have to be
>>>>>> discussed in a public forum.  I understand some others' concerns
>>>>>> about the community appearing to be closed, but I think there should
>>>>>> be a barrier to entry.  Maybe it's too high, but it seems to me that
>>>>>> it should exist.  After all it's basically a lifetime appointment
>>>
>>>
>>> and
>>>
>>>>>> revocations are very rare if one has ever happened at all.
>>>>>>
>>>>>> Greg
>>>>>>
>>>>>>
>>>
>>> ---------------------------------------------------------------------
>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> "You can lead a horse to water but you cannot make it float on its
>>>>
>>>>
>>>> back."
>>>>
>>>>> ~Dakota Jack~
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> -- 
>>> "You can lead a horse to water but you cannot make it float on its 
>>> back."
>>> ~Dakota Jack~
>>>
>>>
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Jonathan Revusky <re...@wanadoo.es>.
Martin Cooper wrote:
> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> 
>>This is the kind of stupid, assinine comment
> 
> 
> 
> What is stupid or assinine about pointing out that your count is incorrect?
> It *is* incorrect. You counted 4 posts to the dev list. To quote you
> directly:
> 
> "I count four (4) posts to the dev list in Greg Reddin's history"
> 
> I provided a URL which demonstrates that that statement is incorrect.

<ROTFL>

But if the actual count is 3 instead of 4, that reinforces Dakota's 
point, doesn't it? (And even if it was 7 or 8....sheesh....)

You guys.... <sigh>

Jonathan Revusky
--
lead developer, FreeMarker project, http://freemarker.org/

> 
> --
> Martin Cooper
> 
> 
> that is really what trolling is
> 
>>all about. There are clearly more than I found by doing a general search
>>for
>>Redding.  Try doing one for Frank and see what happens, Martin.  I really
>>could vomit when I hear that feminine English "pity".
>>
>>On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>>
>>>On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>>>
>>>>Here is a case in point:  I count four (4) posts to the dev list in
>>
>>Greg
>>
>>>>Reddin's history.
>>>
>>>
>>>Pity you can't count.
>>>
>>>http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
>>>
>>>--
>>>Martin Cooper
>>>
>>>
>>>  He is a committer.  On the user list there is also
>>>
>>>>virtually nothing.  What stands out is that he was interested in a
>>>
>>>couple
>>>
>>>>of
>>>>posts in Shale.  What is the possible reason he is a committer and
>>
>>Frank
>>
>>>>is
>>>>not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
>>>>people actually believe Ted and Craig?
>>>>
>>>>On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
>>>>
>>>>>
>>>>>On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
>>>>>
>>>>>
>>>>>>That depends entirely on your meaning of the word "closed".  You
>>>>>>make the
>>>>>>argument that the number of new committers means it isn't closed,
>>>>>>and I
>>>>>>agree with you to a degree.  But that's not the only meaning of
>>>>>>"closed"... the invitations to those people came *soley* from the
>>>
>>>PMC
>>>
>>>>>>AFAIK... the community had no say in it.  That's the thing my
>>>
>>>proposal
>>>
>>>>>>seeks to address, that the initiation of someone being invited
>>>
>>>doesn't
>>>
>>>>>>necessarily have to come from those already there (although they
>>>
>>>would
>>>
>>>>>>still have the final say-so).
>>>>>
>>>>>I have some serious concerns about this.  Let me just use myself as
>>>>>an example.  I've been a committer for about 6 months or so.  I have
>>>>>absolutely no idea what sort of discussion took place before I
>>>>>received that invitation.  If there was someone among the PMC who
>>
>>was
>>
>>>>>vehemently opposed to my nomination I'm glad they had a confidential
>>>>>forum in which to discuss their concerns.  Now that I am a committer
>>>>>I can have an unbiased conversation with anybody else in the group
>>>>>without any preconceived notion of what that individual's opinion of
>>>>>me might be.  Truly, I don't have confidence that either user@ or
>>>>>dev@ is a place where concerns can be expressed openly without fear
>>>>>of unprofessional response.  It's just too easy for this kind of
>>>>>discussion to turn into personal attacks in a forum such as user@ or
>>>>>even dev@.
>>>>>
>>>>>When Struts was a Jakarta subproject I remember committer votes
>>>>>taking place on dev@.  I always felt just a little uneasy about it.
>>>>>99 times out of 100 it was a unanimous +1 with no discussion.  But I
>>>>>seem to recall at least one case when concerns were expressed
>>
>>(sorry,
>>
>>>>>I don't remember the specifics, please correct me if I'm wrong).  I
>>>>>feel really bad that this person's personal merit would have to be
>>>>>discussed in a public forum.  I understand some others' concerns
>>>>>about the community appearing to be closed, but I think there should
>>>>>be a barrier to entry.  Maybe it's too high, but it seems to me that
>>>>>it should exist.  After all it's basically a lifetime appointment
>>
>>and
>>
>>>>>revocations are very rare if one has ever happened at all.
>>>>>
>>>>>Greg
>>>>>
>>>>>
>>
>>---------------------------------------------------------------------
>>
>>>>>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>--
>>>>"You can lead a horse to water but you cannot make it float on its
>>>
>>>back."
>>>
>>>>~Dakota Jack~
>>>>
>>>>
>>>
>>>
>>
>>--
>>"You can lead a horse to water but you cannot make it float on its back."
>>~Dakota Jack~
>>
>>
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Martin Cooper <ma...@apache.org>.
On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>
> This is the kind of stupid, assinine comment


What is stupid or assinine about pointing out that your count is incorrect?
It *is* incorrect. You counted 4 posts to the dev list. To quote you
directly:

"I count four (4) posts to the dev list in Greg Reddin's history"

I provided a URL which demonstrates that that statement is incorrect.

--
Martin Cooper


that is really what trolling is
> all about. There are clearly more than I found by doing a general search
> for
> Redding.  Try doing one for Frank and see what happens, Martin.  I really
> could vomit when I hear that feminine English "pity".
>
> On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
> >
> > On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> > >
> > > Here is a case in point:  I count four (4) posts to the dev list in
> Greg
> > > Reddin's history.
> >
> >
> > Pity you can't count.
> >
> > http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
> >
> > --
> > Martin Cooper
> >
> >
> >   He is a committer.  On the user list there is also
> > > virtually nothing.  What stands out is that he was interested in a
> > couple
> > > of
> > > posts in Shale.  What is the possible reason he is a committer and
> Frank
> > > is
> > > not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
> > > people actually believe Ted and Craig?
> > >
> > > On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
> > > >
> > > >
> > > > On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
> > > >
> > > > > That depends entirely on your meaning of the word "closed".  You
> > > > > make the
> > > > > argument that the number of new committers means it isn't closed,
> > > > > and I
> > > > > agree with you to a degree.  But that's not the only meaning of
> > > > > "closed"... the invitations to those people came *soley* from the
> > PMC
> > > > > AFAIK... the community had no say in it.  That's the thing my
> > proposal
> > > > > seeks to address, that the initiation of someone being invited
> > doesn't
> > > > > necessarily have to come from those already there (although they
> > would
> > > > > still have the final say-so).
> > > >
> > > > I have some serious concerns about this.  Let me just use myself as
> > > > an example.  I've been a committer for about 6 months or so.  I have
> > > > absolutely no idea what sort of discussion took place before I
> > > > received that invitation.  If there was someone among the PMC who
> was
> > > > vehemently opposed to my nomination I'm glad they had a confidential
> > > > forum in which to discuss their concerns.  Now that I am a committer
> > > > I can have an unbiased conversation with anybody else in the group
> > > > without any preconceived notion of what that individual's opinion of
> > > > me might be.  Truly, I don't have confidence that either user@ or
> > > > dev@ is a place where concerns can be expressed openly without fear
> > > > of unprofessional response.  It's just too easy for this kind of
> > > > discussion to turn into personal attacks in a forum such as user@ or
> > > > even dev@.
> > > >
> > > > When Struts was a Jakarta subproject I remember committer votes
> > > > taking place on dev@.  I always felt just a little uneasy about it.
> > > > 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> > > > seem to recall at least one case when concerns were expressed
> (sorry,
> > > > I don't remember the specifics, please correct me if I'm wrong).  I
> > > > feel really bad that this person's personal merit would have to be
> > > > discussed in a public forum.  I understand some others' concerns
> > > > about the community appearing to be closed, but I think there should
> > > > be a barrier to entry.  Maybe it's too high, but it seems to me that
> > > > it should exist.  After all it's basically a lifetime appointment
> and
> > > > revocations are very rare if one has ever happened at all.
> > > >
> > > > Greg
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > > For additional commands, e-mail: dev-help@struts.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > "You can lead a horse to water but you cannot make it float on its
> > back."
> > > ~Dakota Jack~
> > >
> > >
> >
> >
>
>
> --
> "You can lead a horse to water but you cannot make it float on its back."
> ~Dakota Jack~
>
>

Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
I come up with 2073 for me since 4/2004 (yeah, and I Google myself every 
now and again too... so shoot me! LOL)

I wouldn't put much stock in these numbers frankly... I don't really 
believe I've posted *only* 2073 messages in two years... hell, I 
probably posted that many LAST MONTH! :-)

Frank

Dakota Jack wrote:
> This is the kind of stupid, assinine comment that is really what trolling is
> all about. There are clearly more than I found by doing a general search for
> Redding.  Try doing one for Frank and see what happens, Martin.  I really
> could vomit when I hear that feminine English "pity".
> 
> On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>>> Here is a case in point:  I count four (4) posts to the dev list in Greg
>>> Reddin's history.
>>
>> Pity you can't count.
>>
>> http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
>>
>> --
>> Martin Cooper
>>
>>
>>   He is a committer.  On the user list there is also
>>> virtually nothing.  What stands out is that he was interested in a
>> couple
>>> of
>>> posts in Shale.  What is the possible reason he is a committer and Frank
>>> is
>>> not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
>>> people actually believe Ted and Craig?
>>>
>>> On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
>>>>
>>>> On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
>>>>
>>>>> That depends entirely on your meaning of the word "closed".  You
>>>>> make the
>>>>> argument that the number of new committers means it isn't closed,
>>>>> and I
>>>>> agree with you to a degree.  But that's not the only meaning of
>>>>> "closed"... the invitations to those people came *soley* from the
>> PMC
>>>>> AFAIK... the community had no say in it.  That's the thing my
>> proposal
>>>>> seeks to address, that the initiation of someone being invited
>> doesn't
>>>>> necessarily have to come from those already there (although they
>> would
>>>>> still have the final say-so).
>>>> I have some serious concerns about this.  Let me just use myself as
>>>> an example.  I've been a committer for about 6 months or so.  I have
>>>> absolutely no idea what sort of discussion took place before I
>>>> received that invitation.  If there was someone among the PMC who was
>>>> vehemently opposed to my nomination I'm glad they had a confidential
>>>> forum in which to discuss their concerns.  Now that I am a committer
>>>> I can have an unbiased conversation with anybody else in the group
>>>> without any preconceived notion of what that individual's opinion of
>>>> me might be.  Truly, I don't have confidence that either user@ or
>>>> dev@ is a place where concerns can be expressed openly without fear
>>>> of unprofessional response.  It's just too easy for this kind of
>>>> discussion to turn into personal attacks in a forum such as user@ or
>>>> even dev@.
>>>>
>>>> When Struts was a Jakarta subproject I remember committer votes
>>>> taking place on dev@.  I always felt just a little uneasy about it.
>>>> 99 times out of 100 it was a unanimous +1 with no discussion.  But I
>>>> seem to recall at least one case when concerns were expressed (sorry,
>>>> I don't remember the specifics, please correct me if I'm wrong).  I
>>>> feel really bad that this person's personal merit would have to be
>>>> discussed in a public forum.  I understand some others' concerns
>>>> about the community appearing to be closed, but I think there should
>>>> be a barrier to entry.  Maybe it's too high, but it seems to me that
>>>> it should exist.  After all it's basically a lifetime appointment and
>>>> revocations are very rare if one has ever happened at all.
>>>>
>>>> Greg
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>> --
>>> "You can lead a horse to water but you cannot make it float on its
>> back."
>>> ~Dakota Jack~
>>>
>>>
>>
> 
> 
> --
> "You can lead a horse to water but you cannot make it float on its back."
> ~Dakota Jack~
> 

-- 
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: fzammetti@hotmail.com
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
This is the kind of stupid, assinine comment that is really what trolling is
all about. There are clearly more than I found by doing a general search for
Redding.  Try doing one for Frank and see what happens, Martin.  I really
could vomit when I hear that feminine English "pity".

On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>
> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> >
> > Here is a case in point:  I count four (4) posts to the dev list in Greg
> > Reddin's history.
>
>
> Pity you can't count.
>
> http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
>
> --
> Martin Cooper
>
>
>   He is a committer.  On the user list there is also
> > virtually nothing.  What stands out is that he was interested in a
> couple
> > of
> > posts in Shale.  What is the possible reason he is a committer and Frank
> > is
> > not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
> > people actually believe Ted and Craig?
> >
> > On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
> > >
> > >
> > > On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
> > >
> > > > That depends entirely on your meaning of the word "closed".  You
> > > > make the
> > > > argument that the number of new committers means it isn't closed,
> > > > and I
> > > > agree with you to a degree.  But that's not the only meaning of
> > > > "closed"... the invitations to those people came *soley* from the
> PMC
> > > > AFAIK... the community had no say in it.  That's the thing my
> proposal
> > > > seeks to address, that the initiation of someone being invited
> doesn't
> > > > necessarily have to come from those already there (although they
> would
> > > > still have the final say-so).
> > >
> > > I have some serious concerns about this.  Let me just use myself as
> > > an example.  I've been a committer for about 6 months or so.  I have
> > > absolutely no idea what sort of discussion took place before I
> > > received that invitation.  If there was someone among the PMC who was
> > > vehemently opposed to my nomination I'm glad they had a confidential
> > > forum in which to discuss their concerns.  Now that I am a committer
> > > I can have an unbiased conversation with anybody else in the group
> > > without any preconceived notion of what that individual's opinion of
> > > me might be.  Truly, I don't have confidence that either user@ or
> > > dev@ is a place where concerns can be expressed openly without fear
> > > of unprofessional response.  It's just too easy for this kind of
> > > discussion to turn into personal attacks in a forum such as user@ or
> > > even dev@.
> > >
> > > When Struts was a Jakarta subproject I remember committer votes
> > > taking place on dev@.  I always felt just a little uneasy about it.
> > > 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> > > seem to recall at least one case when concerns were expressed (sorry,
> > > I don't remember the specifics, please correct me if I'm wrong).  I
> > > feel really bad that this person's personal merit would have to be
> > > discussed in a public forum.  I understand some others' concerns
> > > about the community appearing to be closed, but I think there should
> > > be a barrier to entry.  Maybe it's too high, but it seems to me that
> > > it should exist.  After all it's basically a lifetime appointment and
> > > revocations are very rare if one has ever happened at all.
> > >
> > > Greg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
> > --
> > "You can lead a horse to water but you cannot make it float on its
> back."
> > ~Dakota Jack~
> >
> >
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
Also, by the way, it is mostly about getting tiles to shale, etc, and
clearly is not based on Struts.

On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>
> On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
> >
> > Here is a case in point:  I count four (4) posts to the dev list in Greg
> > Reddin's history.
>
>
> Pity you can't count.
>
> http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a
>
> --
> Martin Cooper
>
>
>   He is a committer.  On the user list there is also
> > virtually nothing.  What stands out is that he was interested in a
> couple
> > of
> > posts in Shale.  What is the possible reason he is a committer and Frank
> > is
> > not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
> > people actually believe Ted and Craig?
> >
> > On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
> > >
> > >
> > > On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
> > >
> > > > That depends entirely on your meaning of the word "closed".  You
> > > > make the
> > > > argument that the number of new committers means it isn't closed,
> > > > and I
> > > > agree with you to a degree.  But that's not the only meaning of
> > > > "closed"... the invitations to those people came *soley* from the
> PMC
> > > > AFAIK... the community had no say in it.  That's the thing my
> proposal
> > > > seeks to address, that the initiation of someone being invited
> doesn't
> > > > necessarily have to come from those already there (although they
> would
> > > > still have the final say-so).
> > >
> > > I have some serious concerns about this.  Let me just use myself as
> > > an example.  I've been a committer for about 6 months or so.  I have
> > > absolutely no idea what sort of discussion took place before I
> > > received that invitation.  If there was someone among the PMC who was
> > > vehemently opposed to my nomination I'm glad they had a confidential
> > > forum in which to discuss their concerns.  Now that I am a committer
> > > I can have an unbiased conversation with anybody else in the group
> > > without any preconceived notion of what that individual's opinion of
> > > me might be.  Truly, I don't have confidence that either user@ or
> > > dev@ is a place where concerns can be expressed openly without fear
> > > of unprofessional response.  It's just too easy for this kind of
> > > discussion to turn into personal attacks in a forum such as user@ or
> > > even dev@.
> > >
> > > When Struts was a Jakarta subproject I remember committer votes
> > > taking place on dev@.  I always felt just a little uneasy about it.
> > > 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> > > seem to recall at least one case when concerns were expressed (sorry,
> > > I don't remember the specifics, please correct me if I'm wrong).  I
> > > feel really bad that this person's personal merit would have to be
> > > discussed in a public forum.  I understand some others' concerns
> > > about the community appearing to be closed, but I think there should
> > > be a barrier to entry.  Maybe it's too high, but it seems to me that
> > > it should exist.  After all it's basically a lifetime appointment and
> > > revocations are very rare if one has ever happened at all.
> > >
> > > Greg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
> > --
> > "You can lead a horse to water but you cannot make it float on its
> back."
> > ~Dakota Jack~
> >
> >
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Martin Cooper <ma...@apache.org>.
On 4/25/06, Dakota Jack <da...@gmail.com> wrote:
>
> Here is a case in point:  I count four (4) posts to the dev list in Greg
> Reddin's history.


Pity you can't count.

http://marc.theaimsgroup.com/?w=2&r=1&s=greg.reddin&q=a

--
Martin Cooper


  He is a committer.  On the user list there is also
> virtually nothing.  What stands out is that he was interested in a couple
> of
> posts in Shale.  What is the possible reason he is a committer and Frank
> is
> not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
> people actually believe Ted and Craig?
>
> On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
> >
> >
> > On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
> >
> > > That depends entirely on your meaning of the word "closed".  You
> > > make the
> > > argument that the number of new committers means it isn't closed,
> > > and I
> > > agree with you to a degree.  But that's not the only meaning of
> > > "closed"... the invitations to those people came *soley* from the PMC
> > > AFAIK... the community had no say in it.  That's the thing my proposal
> > > seeks to address, that the initiation of someone being invited doesn't
> > > necessarily have to come from those already there (although they would
> > > still have the final say-so).
> >
> > I have some serious concerns about this.  Let me just use myself as
> > an example.  I've been a committer for about 6 months or so.  I have
> > absolutely no idea what sort of discussion took place before I
> > received that invitation.  If there was someone among the PMC who was
> > vehemently opposed to my nomination I'm glad they had a confidential
> > forum in which to discuss their concerns.  Now that I am a committer
> > I can have an unbiased conversation with anybody else in the group
> > without any preconceived notion of what that individual's opinion of
> > me might be.  Truly, I don't have confidence that either user@ or
> > dev@ is a place where concerns can be expressed openly without fear
> > of unprofessional response.  It's just too easy for this kind of
> > discussion to turn into personal attacks in a forum such as user@ or
> > even dev@.
> >
> > When Struts was a Jakarta subproject I remember committer votes
> > taking place on dev@.  I always felt just a little uneasy about it.
> > 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> > seem to recall at least one case when concerns were expressed (sorry,
> > I don't remember the specifics, please correct me if I'm wrong).  I
> > feel really bad that this person's personal merit would have to be
> > discussed in a public forum.  I understand some others' concerns
> > about the community appearing to be closed, but I think there should
> > be a barrier to entry.  Maybe it's too high, but it seems to me that
> > it should exist.  After all it's basically a lifetime appointment and
> > revocations are very rare if one has ever happened at all.
> >
> > Greg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> "You can lead a horse to water but you cannot make it float on its back."
> ~Dakota Jack~
>
>

Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
Here is a case in point:  I count four (4) posts to the dev list in Greg
Reddin's history.  He is a committer.  On the user list there is also
virtually nothing.  What stands out is that he was interested in a couple of
posts in Shale.  What is the possible reason he is a committer and Frank is
not?  Is this the Way Different Struts-Apache Way.  This is crazy!  Do
people actually believe Ted and Craig?

On 4/25/06, Greg Reddin <gr...@apache.org> wrote:
>
>
> On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
>
> > That depends entirely on your meaning of the word "closed".  You
> > make the
> > argument that the number of new committers means it isn't closed,
> > and I
> > agree with you to a degree.  But that's not the only meaning of
> > "closed"... the invitations to those people came *soley* from the PMC
> > AFAIK... the community had no say in it.  That's the thing my proposal
> > seeks to address, that the initiation of someone being invited doesn't
> > necessarily have to come from those already there (although they would
> > still have the final say-so).
>
> I have some serious concerns about this.  Let me just use myself as
> an example.  I've been a committer for about 6 months or so.  I have
> absolutely no idea what sort of discussion took place before I
> received that invitation.  If there was someone among the PMC who was
> vehemently opposed to my nomination I'm glad they had a confidential
> forum in which to discuss their concerns.  Now that I am a committer
> I can have an unbiased conversation with anybody else in the group
> without any preconceived notion of what that individual's opinion of
> me might be.  Truly, I don't have confidence that either user@ or
> dev@ is a place where concerns can be expressed openly without fear
> of unprofessional response.  It's just too easy for this kind of
> discussion to turn into personal attacks in a forum such as user@ or
> even dev@.
>
> When Struts was a Jakarta subproject I remember committer votes
> taking place on dev@.  I always felt just a little uneasy about it.
> 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> seem to recall at least one case when concerns were expressed (sorry,
> I don't remember the specifics, please correct me if I'm wrong).  I
> feel really bad that this person's personal merit would have to be
> discussed in a public forum.  I understand some others' concerns
> about the community appearing to be closed, but I think there should
> be a barrier to entry.  Maybe it's too high, but it seems to me that
> it should exist.  After all it's basically a lifetime appointment and
> revocations are very rare if one has ever happened at all.
>
> Greg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Greg Reddin <gr...@apache.org>.
On Apr 25, 2006, at 1:05 PM, Frank W. Zammetti wrote:

> Out of curiosity, does the idea of a nominee accepting a nomination  
> before
> the PMC discusses and votes alleviate your concerns at all?

Not if the discussion occurs on a public list and the concerns don't  
exist if they occur on a private list :-)

Greg


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 1:38 pm, Greg Reddin said:
>
> On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:
>
>> That depends entirely on your meaning of the word "closed".  You
>> make the
>> argument that the number of new committers means it isn't closed,
>> and I
>> agree with you to a degree.  But that's not the only meaning of
>> "closed"... the invitations to those people came *soley* from the PMC
>> AFAIK... the community had no say in it.  That's the thing my proposal
>> seeks to address, that the initiation of someone being invited doesn't
>> necessarily have to come from those already there (although they would
>> still have the final say-so).
>
> I have some serious concerns about this.  Let me just use myself as
> an example.  I've been a committer for about 6 months or so.  I have
> absolutely no idea what sort of discussion took place before I
> received that invitation.  If there was someone among the PMC who was
> vehemently opposed to my nomination I'm glad they had a confidential
> forum in which to discuss their concerns.  Now that I am a committer
> I can have an unbiased conversation with anybody else in the group
> without any preconceived notion of what that individual's opinion of
> me might be.  Truly, I don't have confidence that either user@ or
> dev@ is a place where concerns can be expressed openly without fear
> of unprofessional response.  It's just too easy for this kind of
> discussion to turn into personal attacks in a forum such as user@ or
> even dev@.

I actually echo your concerns, and it gave me a great deal of pause in
writing the proposal.  I certainly don't want to see any embarassment
heaped on someone if it doesn't have to be.  One of course hopes that even
in a private forum, the debate is professional and not hurtful in any way
(and I have every confidence that it always has been)... and I completely
see your point about the lists... if anyone can comment, you never know
who is going to say what, there isn't even the presumed air of
professionalism that I'm sure is present when the committers consider
someone privately.

That being said, I think there is still a place for transparency... Ted I
believe mentioned only recalling two nea votes over the years, and I would
be interested in knowing why they were rejected, if for no other reason
than to learn from it, learn what criteria are being used to decide,
because if they were nominated in the first place, one has to assume there
was sufficient merit on the surface in someone's eyes.

> When Struts was a Jakarta subproject I remember committer votes
> taking place on dev@.  I always felt just a little uneasy about it.
> 99 times out of 100 it was a unanimous +1 with no discussion.  But I
> seem to recall at least one case when concerns were expressed (sorry,
> I don't remember the specifics, please correct me if I'm wrong).  I
> feel really bad that this person's personal merit would have to be
> discussed in a public forum.  I understand some others' concerns
> about the community appearing to be closed, but I think there should
> be a barrier to entry.  Maybe it's too high, but it seems to me that
> it should exist.  After all it's basically a lifetime appointment and
> revocations are very rare if one has ever happened at all.

I don't at all disagree.  I'm not advocating letting anyone in who wants
in, I too agree there has to be a barrier to entry.  And truthfully, I'm
not even sure it's too high right now.  I think this proposal would help
ensure that it isn't though... it would also add some transparency to the
process, which, even though I agree with your concerns, I feel is a good
thing.

Out of curiosity, does the idea of a nominee accepting a nomination before
the PMC discusses and votes alleviate your concerns at all?

And thanks for commenting!

> Greg

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Greg Reddin <gr...@apache.org>.
On Apr 25, 2006, at 9:55 AM, Frank W. Zammetti wrote:

> That depends entirely on your meaning of the word "closed".  You  
> make the
> argument that the number of new committers means it isn't closed,  
> and I
> agree with you to a degree.  But that's not the only meaning of
> "closed"... the invitations to those people came *soley* from the PMC
> AFAIK... the community had no say in it.  That's the thing my proposal
> seeks to address, that the initiation of someone being invited doesn't
> necessarily have to come from those already there (although they would
> still have the final say-so).

I have some serious concerns about this.  Let me just use myself as  
an example.  I've been a committer for about 6 months or so.  I have  
absolutely no idea what sort of discussion took place before I  
received that invitation.  If there was someone among the PMC who was  
vehemently opposed to my nomination I'm glad they had a confidential  
forum in which to discuss their concerns.  Now that I am a committer  
I can have an unbiased conversation with anybody else in the group  
without any preconceived notion of what that individual's opinion of  
me might be.  Truly, I don't have confidence that either user@ or  
dev@ is a place where concerns can be expressed openly without fear  
of unprofessional response.  It's just too easy for this kind of  
discussion to turn into personal attacks in a forum such as user@ or  
even dev@.

When Struts was a Jakarta subproject I remember committer votes  
taking place on dev@.  I always felt just a little uneasy about it.   
99 times out of 100 it was a unanimous +1 with no discussion.  But I  
seem to recall at least one case when concerns were expressed (sorry,  
I don't remember the specifics, please correct me if I'm wrong).  I  
feel really bad that this person's personal merit would have to be  
discussed in a public forum.  I understand some others' concerns  
about the community appearing to be closed, but I think there should  
be a barrier to entry.  Maybe it's too high, but it seems to me that  
it should exist.  After all it's basically a lifetime appointment and  
revocations are very rare if one has ever happened at all.

Greg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 1:17 am, Craig McClanahan said:

> The latter statement is, as mentioned in my previous response, the way
> that
> *all* projects at Apache work -- it is not unique to Struts.  Any claim
> that
> all of Apache is broken in this regard is going to be, umm, unlikely to be
> agreed with :-).  What's more interesting is to examine the former
> statement, and compare it to the facts.

Please don't infer the word broken, I never used it :)  Broken has a
negative connotation.  I'm talking about an improvement.  Unless you
believe the way things are today is 100% perfect, then there is always
room for improvement.  Something doesn't have to be "broken" for a change
to be reasonable.

Also, I'm not talking about all of Apache here, I'm talking only about
Struts.  Granted I'm not a member of every community at Apache, but of the
ones I am (even as just a lurker), Struts seems to be the only one that
evokes these types of criticisms (rightly or wrongly so).  I'm not
suggesting trying to change the way all of Apache works, and in fact, I'm
not trying to change the way Struts works.  Just build on top of it a
little bit.  If this idea were to work, and other projects saw and liked
it, maybe it would change all of Apache eventually.  That's not one of my
goals here today :)

> That is a pretty large
> percentage increase for a single year, even discounting the merger -- and
> have you ever seen other "competing" communities come together like this?
> Hmm ... doesn't seem like the existing community is particularly "closed"
> to
> new blood to me.

That depends entirely on your meaning of the word "closed".  You make the
argument that the number of new committers means it isn't closed, and I
agree with you to a degree.  But that's not the only meaning of
"closed"... the invitations to those people came *soley* from the PMC
AFAIK... the community had no say in it.  That's the thing my proposal
seeks to address, that the initiation of someone being invited doesn't
necessarily have to come from those already there (although they would
still have the final say-so).

> Examining how the new folks got themselves nominated and elected is also
> interesting.  In every case, it was based on continuous contributions of
> code, documentation, user list help, build script maintenance, or whatever
> made a *positive* difference for everyone.

That's the way it *should* work, but I don't believe it is the way it
*has* worked.  There are a number of other names that would have been
invited as well if that is all there was to it.  My proposal seeks to
remove that "something else"... no, actually, it doesn't seek to remove
it, it only seeks to bring it into the light, so to speak.  If someone
were nominated and ultimately not invited to join, the community could
look and see if they believed that person met the criteria you list above.
 If they did and still were not invited, it would be obvious that
something else was at work.  Perhaps it was something completely
legitimate; it probably would come out in discussion during the vote
period then.  Maybe it isn't something legitimate (as judged by the
community).  Either way, we'd know, and could form our opinions
accordingly.

> There is also another interesting observation here -- you don't have to be
> a
> committer to initiate changes to the Struts code base.  What you have to
> do
> is justify your bugfix or RFE to the point where an existing committer is
> willing to take responsibility for cleaning up any messes that committing
> the change might cause.  So, you only have to convince one of the various
> folks to get your patch in.  Failure to succeed in that goal *could* be a
> close minded community, but it also just might be that the proposed change
> doesn't fit with what the committers as a whole have in mind (it only
> takes
> one commiter -1 to make a committed change get reversed, so we pay
> attention
> to this as part of the decision process on accepting a patch).  Just in
> the
> little time I have had to spend on Struts in the last year, I've committed
> patches from at least 20 different people.  Spread across the six years
> that
> Struts has existed, and all the committers who have done the same thing,
> we
> are talking many *hundreds* of people who have contributed at least some
> code or documentation to what is now Struts.

Perfectly fair observation IMO.

> I just don't buy the presumption that the current system is broken.  I
> won't
> presume to convince *you* to think that way -- it's your perogative to
> think
> whatever you want -- but I will certainly take into account whether
> someone
> "gets it" before I would ever vote for them to be a committer.

Again, I never said anything was "broke".  If I were to describe it, I
would probably say "sub-optimal".  Unless you are prepared to say that you
think everything is absolutely perfect just the way it is, then there is
*always* remove for improvement, it doesn't have to be broken.

The "getting it" comment... if this equates to "you have to see things the
way I see it", then I think it it problematic.  I totally understand there
is a certain set of underlying principles that Apache runs on, and someone
should generally believe and adhere to those principles.  I think most of
us around here do, or we probably wouldn't be around! :)  But, how easy it
is to take the phrase "getting it" to an extreme that is unproductive...
does one not "get it" if they question how things work?  Does one not "get
it" if they propose changes?  Does one not "get it" if they mostly agree
with the principles but think one or two could be tweaked a bit?

I for one would very much appreciate a concrete definition of the phrase
"gets it"...  Because if it can't be concretely defined, that frankly
plays into the "closed club" preception IMO... if it's an arbitrary
determination made by those who already "get it", is it really a
legitimate reason?

> Fortunately for those who either don't, or don't want to, buy into this,
> the
> Apache license gives you the freedom to take the code and go start your
> own
> community, operating according to your own rules, if you don't like the
> way
> things work here.  But you are starting from a rationale that does not
> match
> the objective facts, so I'm not even going to be interested in trying to
> hash out details of how to change something that does not need to be
> changed.

Thank you Craig, I do appreciate you taking the time to react.  That last
sentence sums up your feelings I think.  I would only ask you to consider
once again that something does not have to be "broken" for there to be a
way to improve it.  You may still not think that the proposal has merit,
but at least come at it from the right perspective :)

> Craig

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Proposal for change

Posted by Paul Speed <ps...@progeeks.com>.

Frank W. Zammetti wrote:

> However, if I were to come up with one now, I would say it is simply to
> help ensure that Action1 does not die, and more than that, is allowed to
> evolve.  I know it isn't going away, I know support isn't being dropped, I
> know all that.  I also know that Ted has said he intends to follow through
> on the roadmap.  I applaude him for that.  Do the other committers share
> that conviction?  If so, then your right, this is nothing but an issue of
> perception.  The way to fix that, as others have said recently, is simply
> to communicate plans better.  That should do the trick.
> 
> If no one shares Ted's goals though, and there are other non-committers
> that do, let them in to help Ted :)
> 

But they can help Ted without being committers.  And when Ted gets 
annoyed with constantly applying their patches then he will nominate 
them.  I've seen it happen.  I can think of at least a few times when 
nominations were still public that they were accompanied with a "I 
nominate so and so because their patches are of high quality and I'm 
tired of committing them." type of message.  :)

-Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 2:32 pm, Martin Cooper said:
> One thing I'll add, though. The problem appears to be perception, and
> reality doesn't, in my opinion and as evidenced below, match that
> perception. Therefore the solution should be addressing the _perception_
> of
> the way Struts is working, and changing perception does not require
> changes
> to the _reality_ of the way it's working.
>
> And one question I would ask: What, exactly, is the end goal? More
> committers? More nominations? If bringing in a new committer every other
> month, as we've been doing, isn't enough, what is? As other people have
> pointed out elsewhere, more committers doesn't necessarily translate to
> more
> activity on the code base, either, as we've seen in the past.

Speaking for myself, I did not have any specific end goal in mind when I
wrote the proposal.

However, if I were to come up with one now, I would say it is simply to
help ensure that Action1 does not die, and more than that, is allowed to
evolve.  I know it isn't going away, I know support isn't being dropped, I
know all that.  I also know that Ted has said he intends to follow through
on the roadmap.  I applaude him for that.  Do the other committers share
that conviction?  If so, then your right, this is nothing but an issue of
perception.  The way to fix that, as others have said recently, is simply
to communicate plans better.  That should do the trick.

If no one shares Ted's goals though, and there are other non-committers
that do, let them in to help Ted :)

I don't have any specific numbers in mind, and I don't think they matter. 
If 100 new committers are added this month but nothing comes of it, what
was the point?  I say those that really want to contribute can be
identified and invited.  I know now that anyone can nominate someone.  I
didn't know that previously.  That takes a lot of the wind out of the
sails of my proposal.

> On the topic of voting in public, I am very much opposed. It's not just a
> case of saving face for a nominee who is ultimately rejected. A public
> vote
> affects the way people vote, as well. In a private vote, someone might
> object strongly, along the lines of "-1 - that guy's code is a pile of
> crap". But would the same person voice that same opinion in a public vote
> on
> a mailing list of a couple of thousand people, and which will be archived
> for the world to see, forever? Perhaps a few would, but many would not.
> They
> would more likely keep quiet, the end result being that Mr. Pile O'Crap
> becomes a committer because the only people who voted were the ones in
> favour. IMHO, that is A Very Bad Thing.

And as I stated in other replies, I tend to agree with you on this. 
However, without knowing why anyone is ever rejected, how are those of us
that might aspire to some day be invited ever know what we should be
doing?  More importantly than that though, how can we know, FOR SURE, that
the decisions are not made on things that they shouldn't be?  "That guy's
code is a pile of crap" would stike me as an invalid reason... "His code
is hard to follow, would be hard to maintain, does not adhere to our
coding standards and seems to indicate he doesn't know how to use
collections properly" is a much more valid, and far less hurtful, way to
say the same thing.  I would hope that in public or private, basic rules
of decency are followed and that "That guy's code is a pile of crap"
wouldn't be something that would be said anyway.

Thanks for your input Martin!

> Martin Cooper

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Martin Cooper <ma...@apache.org>.
On 4/24/06, Craig McClanahan <cr...@apache.org> wrote:
>
> On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> >
> > * Rationale
> > One of the issues that a number of people seem to have with the way
> > Struts has progressed is the seeming inability (or difficulty at least)
> > of getting "new blood" involved.  There seems to be a perception by many
> > that there is a bit of a "closed club" mentality with regard to being
> > invited in as a committer and that the Struts community at large has no
> > say in the matter.


Having composed a nice long response, I can now delete it, since Craig says
below pretty much everything I was going to say also. ;-)

One thing I'll add, though. The problem appears to be perception, and
reality doesn't, in my opinion and as evidenced below, match that
perception. Therefore the solution should be addressing the _perception_ of
the way Struts is working, and changing perception does not require changes
to the _reality_ of the way it's working.

And one question I would ask: What, exactly, is the end goal? More
committers? More nominations? If bringing in a new committer every other
month, as we've been doing, isn't enough, what is? As other people have
pointed out elsewhere, more committers doesn't necessarily translate to more
activity on the code base, either, as we've seen in the past.

On the topic of voting in public, I am very much opposed. It's not just a
case of saving face for a nominee who is ultimately rejected. A public vote
affects the way people vote, as well. In a private vote, someone might
object strongly, along the lines of "-1 - that guy's code is a pile of
crap". But would the same person voice that same opinion in a public vote on
a mailing list of a couple of thousand people, and which will be archived
for the world to see, forever? Perhaps a few would, but many would not. They
would more likely keep quiet, the end result being that Mr. Pile O'Crap
becomes a committer because the only people who voted were the ones in
favour. IMHO, that is A Very Bad Thing.

--
Martin Cooper


The latter statement is, as mentioned in my previous response, the way that
> *all* projects at Apache work -- it is not unique to Struts.  Any claim
> that
> all of Apache is broken in this regard is going to be, umm, unlikely to be
> agreed with :-).  What's more interesting is to examine the former
> statement, and compare it to the facts.
>
> The "Who We Are" page[1] lists the current folks who are on the PMC (and
> also have committer privileges), and who are committers not on the PMC.
> There's 14 and 13 names, respectively, giving a total of 27 (and this
> doesn't count the 10 previous committers who are now on the emeritus list,
> for a total of 37).  That's a pretty good size number, compared to the
> average at Apache.  But what is really interesting is to look at the
> timing
> of how we got from one committer (me) six years ago, to where we are today
> -- and focus especially on the more recent changes.
>
> In just the last year there have been quite a number of new committers
> added[2] ... six independent of the WebWork merger (Wendy, Gary, Greg,
> Shawn, Laurie, and Richard), two more (Jason and Patrick) directly because
> of the merger, and five more who have commit rights to the WebWork
> incubator
> code and will become Struts committers as soon as it graduates.  There is
> also one outstanding invitation that, for personal reasons fo the
> individual
> involved, will be accepted later rather than now.  That is a pretty large
> percentage increase for a single year, even discounting the merger -- and
> have you ever seen other "competing" communities come together like this?
> Hmm ... doesn't seem like the existing community is particularly "closed"
> to
> new blood to me.
>
> Examining how the new folks got themselves nominated and elected is also
> interesting.  In every case, it was based on continuous contributions of
> code, documentation, user list help, build script maintenance, or whatever
> made a *positive* difference for everyone.  Indeed, if you go back to the
> days when folks like Ted and Martin were added, a lot of it was being
> tired
> of applying all the patches they were contributing :-).  All of these
> folks
> "get it" -- so it is not just a couple of dictatorial snobs sitting on top
> of the mountain dictating who is in and who is out :-).
>
> There is also another interesting observation here -- you don't have to be
> a
> committer to initiate changes to the Struts code base.  What you have to
> do
> is justify your bugfix or RFE to the point where an existing committer is
> willing to take responsibility for cleaning up any messes that committing
> the change might cause.  So, you only have to convince one of the various
> folks to get your patch in.  Failure to succeed in that goal *could* be a
> close minded community, but it also just might be that the proposed change
> doesn't fit with what the committers as a whole have in mind (it only
> takes
> one commiter -1 to make a committed change get reversed, so we pay
> attention
> to this as part of the decision process on accepting a patch).  Just in
> the
> little time I have had to spend on Struts in the last year, I've committed
> patches from at least 20 different people.  Spread across the six years
> that
> Struts has existed, and all the committers who have done the same thing,
> we
> are talking many *hundreds* of people who have contributed at least some
> code or documentation to what is now Struts.
>
> I just don't buy the presumption that the current system is broken.  I
> won't
> presume to convince *you* to think that way -- it's your perogative to
> think
> whatever you want -- but I will certainly take into account whether
> someone
> "gets it" before I would ever vote for them to be a committer.
>
> Fortunately for those who either don't, or don't want to, buy into this,
> the
> Apache license gives you the freedom to take the code and go start your
> own
> community, operating according to your own rules, if you don't like the
> way
> things work here.  But you are starting from a rationale that does not
> match
> the objective facts, so I'm not even going to be interested in trying to
> hash out details of how to change something that does not need to be
> changed.
>
> Craig
>
> [1] http://struts.apache.org/volunteers.html
> [2] http://struts.apache.org/announce.html
>
>

Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 1:17 am, Craig McClanahan said:

> The latter statement is, as mentioned in my previous response, the way
> that
> *all* projects at Apache work -- it is not unique to Struts.  Any claim
> that
> all of Apache is broken in this regard is going to be, umm, unlikely to be
> agreed with :-).  What's more interesting is to examine the former
> statement, and compare it to the facts.

Please don't infer the word broken, I never used it :)  Broken has a
negative connotation.  I'm talking about an improvement.  Unless you
believe the way things are today is 100% perfect, then there is always
room for improvement.  Something doesn't have to be "broken" for a change
to be reasonable.

Also, I'm not talking about all of Apache here, I'm talking only about
Struts.  Granted I'm not a member of every community at Apache, but of the
ones I am (even as just a lurker), Struts seems to be the only one that
evokes these types of criticisms (rightly or wrongly so).  I'm not
suggesting trying to change the way all of Apache works, and in fact, I'm
not trying to change the way Struts works.  Just build on top of it a
little bit.  If this idea were to work, and other projects saw and liked
it, maybe it would change all of Apache eventually.  That's not one of my
goals here today :)

> That is a pretty large
> percentage increase for a single year, even discounting the merger -- and
> have you ever seen other "competing" communities come together like this?
> Hmm ... doesn't seem like the existing community is particularly "closed"
> to
> new blood to me.

That depends entirely on your meaning of the word "closed".  You make the
argument that the number of new committers means it isn't closed, and I
agree with you to a degree.  But that's not the only meaning of
"closed"... the invitations to those people came *soley* from the PMC
AFAIK... the community had no say in it.  That's the thing my proposal
seeks to address, that the initiation of someone being invited doesn't
necessarily have to come from those already there (although they would
still have the final say-so).

> Examining how the new folks got themselves nominated and elected is also
> interesting.  In every case, it was based on continuous contributions of
> code, documentation, user list help, build script maintenance, or whatever
> made a *positive* difference for everyone.

That's the way it *should* work, but I don't believe it is the way it
*has* worked.  There are a number of other names that would have been
invited as well if that is all there was to it.  My proposal seeks to
remove that "something else"... no, actually, it doesn't seek to remove
it, it only seeks to bring it into the light, so to speak.  If someone
were nominated and ultimately not invited to join, the community could
look and see if they believed that person met the criteria you list above.
 If they did and still were not invited, it would be obvious that
something else was at work.  Perhaps it was something completely
legitimate; it probably would come out in discussion during the vote
period then.  Maybe it isn't something legitimate (as judged by the
community).  Either way, we'd know, and could form our opinions
accordingly.

> There is also another interesting observation here -- you don't have to be
> a
> committer to initiate changes to the Struts code base.  What you have to
> do
> is justify your bugfix or RFE to the point where an existing committer is
> willing to take responsibility for cleaning up any messes that committing
> the change might cause.  So, you only have to convince one of the various
> folks to get your patch in.  Failure to succeed in that goal *could* be a
> close minded community, but it also just might be that the proposed change
> doesn't fit with what the committers as a whole have in mind (it only
> takes
> one commiter -1 to make a committed change get reversed, so we pay
> attention
> to this as part of the decision process on accepting a patch).  Just in
> the
> little time I have had to spend on Struts in the last year, I've committed
> patches from at least 20 different people.  Spread across the six years
> that
> Struts has existed, and all the committers who have done the same thing,
> we
> are talking many *hundreds* of people who have contributed at least some
> code or documentation to what is now Struts.

Perfectly fair observation IMO.

> I just don't buy the presumption that the current system is broken.  I
> won't
> presume to convince *you* to think that way -- it's your perogative to
> think
> whatever you want -- but I will certainly take into account whether
> someone
> "gets it" before I would ever vote for them to be a committer.

Again, I never said anything was "broke".  If I were to describe it, I
would probably say "sub-optimal".  Unless you are prepared to say that you
think everything is absolutely perfect just the way it is, then there is
*always* remove for improvement, it doesn't have to be broken.

The "getting it" comment... if this equates to "you have to see things the
way I see it", then I think it it problematic.  I totally understand there
is a certain set of underlying principles that Apache runs on, and someone
should generally believe and adhere to those principles.  I think most of
us around here do, or we probably wouldn't be around! :)  But, how easy it
is to take the phrase "getting it" to an extreme that is unproductive...
does one not "get it" if they question how things work?  Does one not "get
it" if they propose changes?  Does one not "get it" if they mostly agree
with the principles but think one or two could be tweaked a bit?

I for one would very much appreciate a concrete definition of the phrase
"gets it"...  Because if it can't be concretely defined, that frankly
plays into the "closed club" preception IMO... if it's an arbitrary
determination made by those who already "get it", is it really a
legitimate reason?

> Fortunately for those who either don't, or don't want to, buy into this,
> the
> Apache license gives you the freedom to take the code and go start your
> own
> community, operating according to your own rules, if you don't like the
> way
> things work here.  But you are starting from a rationale that does not
> match
> the objective facts, so I'm not even going to be interested in trying to
> hash out details of how to change something that does not need to be
> changed.

Thank you Craig, I do appreciate you taking the time to react.  That last
sentence sums up your feelings I think.  I would only ask you to consider
once again that something does not have to be "broken" for there to be a
way to improve it.  You may still not think that the proposal has merit,
but at least come at it from the right perspective :)

> Craig

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
The burst in the number of committers has nothing to do with Struts.  For
the most part it is Craig bringing in people who had nothing to do with
Struts out of JSF to work on Shale and give him voting power.  Has Gary ever
done anything with Struts?  And, he is a Struts committer. That is the
Struts-Apache Way.  The Apache Way and the Struts-Apache Way or Way
Different.

On 4/25/06, Niall Pemberton <ni...@gmail.com> wrote:
>
> On 4/25/06, Craig McClanahan <cr...@apache.org> wrote:
> > On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> > >
> > > * Rationale
> > > One of the issues that a number of people seem to have with the way
> > > Struts has progressed is the seeming inability (or difficulty at
> least)
> > > of getting "new blood" involved.  There seems to be a perception by
> many
> > > that there is a bit of a "closed club" mentality with regard to being
> > > invited in as a committer and that the Struts community at large has
> no
> > > say in the matter.
> >
> >
> > The latter statement is, as mentioned in my previous response, the way
> that
> > *all* projects at Apache work -- it is not unique to Struts.  Any claim
> that
> > all of Apache is broken in this regard is going to be, umm, unlikely to
> be
> > agreed with :-).  What's more interesting is to examine the former
> > statement, and compare it to the facts.
> >
> > The "Who We Are" page[1] lists the current folks who are on the PMC (and
> > also have committer privileges), and who are committers not on the PMC.
> > There's 14 and 13 names, respectively, giving a total of 27 (and this
> > doesn't count the 10 previous committers who are now on the emeritus
> list,
> > for a total of 37).  That's a pretty good size number, compared to the
> > average at Apache.  But what is really interesting is to look at the
> timing
> > of how we got from one committer (me) six years ago, to where we are
> today
> > -- and focus especially on the more recent changes.
> >
> > In just the last year there have been quite a number of new committers
> > added[2] ... six independent of the WebWork merger (Wendy, Gary, Greg,
> > Shawn, Laurie, and Richard), two more (Jason and Patrick) directly
> because
> > of the merger, and five more who have commit rights to the WebWork
> incubator
> > code and will become Struts committers as soon as it graduates.  There
> is
> > also one outstanding invitation that, for personal reasons fo the
> individual
> > involved, will be accepted later rather than now.  That is a pretty
> large
> > percentage increase for a single year, even discounting the merger --
> and
> > have you ever seen other "competing" communities come together like
> this?
> > Hmm ... doesn't seem like the existing community is particularly
> "closed" to
> > new blood to me.
>
> I agree that we have been pretty active in bringing people into the
> Struts project but although the numbers look good, in terms of
> action1, it hasn't translated into much activity in terms of moving
> action1 code forward.
>
> > Examining how the new folks got themselves nominated and elected is also
> > interesting.  In every case, it was based on continuous contributions of
> > code, documentation, user list help, build script maintenance, or
> whatever
> > made a *positive* difference for everyone.  Indeed, if you go back to
> the
> > days when folks like Ted and Martin were added, a lot of it was being
> tired
> > of applying all the patches they were contributing :-).  All of these
> folks
> > "get it" -- so it is not just a couple of dictatorial snobs sitting on
> top
> > of the mountain dictating who is in and who is out :-).
> >
> > There is also another interesting observation here -- you don't have to
> be a
> > committer to initiate changes to the Struts code base.  What you have to
> do
> > is justify your bugfix or RFE to the point where an existing committer
> is
> > willing to take responsibility for cleaning up any messes that
> committing
> > the change might cause.  So, you only have to convince one of the
> various
> > folks to get your patch in.  Failure to succeed in that goal *could* be
> a
> > close minded community, but it also just might be that the proposed
> change
> > doesn't fit with what the committers as a whole have in mind (it only
> takes
> > one commiter -1 to make a committed change get reversed, so we pay
> attention
> > to this as part of the decision process on accepting a patch).  Just in
> the
> > little time I have had to spend on Struts in the last year, I've
> committed
> > patches from at least 20 different people.  Spread across the six years
> that
> > Struts has existed, and all the committers who have done the same thing,
> we
> > are talking many *hundreds* of people who have contributed at least some
> > code or documentation to what is now Struts.
>
> Looking at bugzilla we have 312 open enhancement tickets for action1
> and if someone did submit a good enhancement patch to bugzilla for
> action1, from my perspective, the most likely outcome is that it would
> be ignored. The situation is different for Shale and ww/action2 - but
> if I wasn't a committer and was interested in working on action1 my
> main concern would be that if I did bother to submit anything theres a
> good chance it would be a waste of time.
>
> > I just don't buy the presumption that the current system is broken.  I
> won't
> > presume to convince *you* to think that way -- it's your perogative to
> think
> > whatever you want -- but I will certainly take into account whether
> someone
> > "gets it" before I would ever vote for them to be a committer.
>
> I agree its not broken in general and there is much to back up that
> when it does work, it works well. However it doesn't mean to say it
> always works. IMO when ASF projects get into a situation where the
> committers on that project are no longer active then I think the
> system can stop working. Clearly we are not in a completely inactive
> situation on action1 - but this is mostly re-organisation,
> changing/fixing the build system and some bug fixes, which I would
> characterize as "maintenance mode". Unfortunately I think this has a
> downwards spiral effect - since if people see less activity and
> bugs/patches being left ignored then they are less likely to
> contribute, which makes us less likely to get new blood for action1
> and so on.
>
> While I agree that what Frank is proposing isn't currently "the Apache
> way" and other projects may look at it with suspicion - I don't think
> thats a reason for not considering something new. If it turned out to
> be a big success then it could become the Apache Way. Seems to me that
> the way for Apache to evolve is by projects trying out new approaches
> like this.
>
> I also don't think that what he is proposing actually goes against
> anything that is "the Apache Way" - the same procedures for a new
> commiter being elected still apply - this just adds a new dimension. I
> think where Frank's proposal has the possibility to do something good
> is that a provides a way which encourages community members to get
> involved and gives them some hope by having a mechanism in place. If
> we can reverse what I perceive as the spiral down wrt to community
> involvement in action1 then this would be really good.
>
> Ted in another post in this thread raises the point about voting
> publically on new committers. I used to be in the same camp, thinking
> its better not to embarras people, but I've changed my mind on this. I
> think one reason why some people believe its a "closed club" is the
> fact that we do the votes privately. Also I think the way to get round
> this issue is to contact the person first asking them if they mind or
> want to be nominated.
>
> > Fortunately for those who either don't, or don't want to, buy into this,
> the
> > Apache license gives you the freedom to take the code and go start your
> own
> > community, operating according to your own rules, if you don't like the
> way
> > things work here.  But you are starting from a rationale that does not
> match
> > the objective facts, so I'm not even going to be interested in trying to
> > hash out details of how to change something that does not need to be
> > changed.
>
> I agree in theory this is the case, but the reality for most people is
> that forking something like action1 as a non-Apache project is not a
> realistic option. For all the reasons why people/businesses are
> attracted to use an Apache project - having a non-official fork of an
> Apache project is unlikely to attract enough of the community to make
> it viable. I would be interested to know if there are any Apache
> projects where this has happened successfully?
>
> Niall
>
> > Craig
> >
> > [1] http://struts.apache.org/volunteers.html
> > [2] http://struts.apache.org/announce.html
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Niall Pemberton <ni...@gmail.com>.
On 4/25/06, Craig McClanahan <cr...@apache.org> wrote:
> On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> >
> > * Rationale
> > One of the issues that a number of people seem to have with the way
> > Struts has progressed is the seeming inability (or difficulty at least)
> > of getting "new blood" involved.  There seems to be a perception by many
> > that there is a bit of a "closed club" mentality with regard to being
> > invited in as a committer and that the Struts community at large has no
> > say in the matter.
>
>
> The latter statement is, as mentioned in my previous response, the way that
> *all* projects at Apache work -- it is not unique to Struts.  Any claim that
> all of Apache is broken in this regard is going to be, umm, unlikely to be
> agreed with :-).  What's more interesting is to examine the former
> statement, and compare it to the facts.
>
> The "Who We Are" page[1] lists the current folks who are on the PMC (and
> also have committer privileges), and who are committers not on the PMC.
> There's 14 and 13 names, respectively, giving a total of 27 (and this
> doesn't count the 10 previous committers who are now on the emeritus list,
> for a total of 37).  That's a pretty good size number, compared to the
> average at Apache.  But what is really interesting is to look at the timing
> of how we got from one committer (me) six years ago, to where we are today
> -- and focus especially on the more recent changes.
>
> In just the last year there have been quite a number of new committers
> added[2] ... six independent of the WebWork merger (Wendy, Gary, Greg,
> Shawn, Laurie, and Richard), two more (Jason and Patrick) directly because
> of the merger, and five more who have commit rights to the WebWork incubator
> code and will become Struts committers as soon as it graduates.  There is
> also one outstanding invitation that, for personal reasons fo the individual
> involved, will be accepted later rather than now.  That is a pretty large
> percentage increase for a single year, even discounting the merger -- and
> have you ever seen other "competing" communities come together like this?
> Hmm ... doesn't seem like the existing community is particularly "closed" to
> new blood to me.

I agree that we have been pretty active in bringing people into the
Struts project but although the numbers look good, in terms of
action1, it hasn't translated into much activity in terms of moving
action1 code forward.

> Examining how the new folks got themselves nominated and elected is also
> interesting.  In every case, it was based on continuous contributions of
> code, documentation, user list help, build script maintenance, or whatever
> made a *positive* difference for everyone.  Indeed, if you go back to the
> days when folks like Ted and Martin were added, a lot of it was being tired
> of applying all the patches they were contributing :-).  All of these folks
> "get it" -- so it is not just a couple of dictatorial snobs sitting on top
> of the mountain dictating who is in and who is out :-).
>
> There is also another interesting observation here -- you don't have to be a
> committer to initiate changes to the Struts code base.  What you have to do
> is justify your bugfix or RFE to the point where an existing committer is
> willing to take responsibility for cleaning up any messes that committing
> the change might cause.  So, you only have to convince one of the various
> folks to get your patch in.  Failure to succeed in that goal *could* be a
> close minded community, but it also just might be that the proposed change
> doesn't fit with what the committers as a whole have in mind (it only takes
> one commiter -1 to make a committed change get reversed, so we pay attention
> to this as part of the decision process on accepting a patch).  Just in the
> little time I have had to spend on Struts in the last year, I've committed
> patches from at least 20 different people.  Spread across the six years that
> Struts has existed, and all the committers who have done the same thing, we
> are talking many *hundreds* of people who have contributed at least some
> code or documentation to what is now Struts.

Looking at bugzilla we have 312 open enhancement tickets for action1
and if someone did submit a good enhancement patch to bugzilla for
action1, from my perspective, the most likely outcome is that it would
be ignored. The situation is different for Shale and ww/action2 - but
if I wasn't a committer and was interested in working on action1 my
main concern would be that if I did bother to submit anything theres a
good chance it would be a waste of time.

> I just don't buy the presumption that the current system is broken.  I won't
> presume to convince *you* to think that way -- it's your perogative to think
> whatever you want -- but I will certainly take into account whether someone
> "gets it" before I would ever vote for them to be a committer.

I agree its not broken in general and there is much to back up that
when it does work, it works well. However it doesn't mean to say it
always works. IMO when ASF projects get into a situation where the
committers on that project are no longer active then I think the
system can stop working. Clearly we are not in a completely inactive
situation on action1 - but this is mostly re-organisation,
changing/fixing the build system and some bug fixes, which I would
characterize as "maintenance mode". Unfortunately I think this has a
downwards spiral effect - since if people see less activity and
bugs/patches being left ignored then they are less likely to
contribute, which makes us less likely to get new blood for action1
and so on.

While I agree that what Frank is proposing isn't currently "the Apache
way" and other projects may look at it with suspicion - I don't think
thats a reason for not considering something new. If it turned out to
be a big success then it could become the Apache Way. Seems to me that
the way for Apache to evolve is by projects trying out new approaches
like this.

I also don't think that what he is proposing actually goes against
anything that is "the Apache Way" - the same procedures for a new
commiter being elected still apply - this just adds a new dimension. I
think where Frank's proposal has the possibility to do something good
is that a provides a way which encourages community members to get
involved and gives them some hope by having a mechanism in place. If
we can reverse what I perceive as the spiral down wrt to community
involvement in action1 then this would be really good.

Ted in another post in this thread raises the point about voting
publically on new committers. I used to be in the same camp, thinking
its better not to embarras people, but I've changed my mind on this. I
think one reason why some people believe its a "closed club" is the
fact that we do the votes privately. Also I think the way to get round
this issue is to contact the person first asking them if they mind or
want to be nominated.

> Fortunately for those who either don't, or don't want to, buy into this, the
> Apache license gives you the freedom to take the code and go start your own
> community, operating according to your own rules, if you don't like the way
> things work here.  But you are starting from a rationale that does not match
> the objective facts, so I'm not even going to be interested in trying to
> hash out details of how to change something that does not need to be
> changed.

I agree in theory this is the case, but the reality for most people is
that forking something like action1 as a non-Apache project is not a
realistic option. For all the reasons why people/businesses are
attracted to use an Apache project - having a non-official fork of an
Apache project is unlikely to attract enough of the community to make
it viable. I would be interested to know if there are any Apache
projects where this has happened successfully?

Niall

> Craig
>
> [1] http://struts.apache.org/volunteers.html
> [2] http://struts.apache.org/announce.html
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
> * Rationale
> One of the issues that a number of people seem to have with the way
> Struts has progressed is the seeming inability (or difficulty at least)
> of getting "new blood" involved.  There seems to be a perception by many
> that there is a bit of a "closed club" mentality with regard to being
> invited in as a committer and that the Struts community at large has no
> say in the matter.


The latter statement is, as mentioned in my previous response, the way that
*all* projects at Apache work -- it is not unique to Struts.  Any claim that
all of Apache is broken in this regard is going to be, umm, unlikely to be
agreed with :-).  What's more interesting is to examine the former
statement, and compare it to the facts.

The "Who We Are" page[1] lists the current folks who are on the PMC (and
also have committer privileges), and who are committers not on the PMC.
There's 14 and 13 names, respectively, giving a total of 27 (and this
doesn't count the 10 previous committers who are now on the emeritus list,
for a total of 37).  That's a pretty good size number, compared to the
average at Apache.  But what is really interesting is to look at the timing
of how we got from one committer (me) six years ago, to where we are today
-- and focus especially on the more recent changes.

In just the last year there have been quite a number of new committers
added[2] ... six independent of the WebWork merger (Wendy, Gary, Greg,
Shawn, Laurie, and Richard), two more (Jason and Patrick) directly because
of the merger, and five more who have commit rights to the WebWork incubator
code and will become Struts committers as soon as it graduates.  There is
also one outstanding invitation that, for personal reasons fo the individual
involved, will be accepted later rather than now.  That is a pretty large
percentage increase for a single year, even discounting the merger -- and
have you ever seen other "competing" communities come together like this?
Hmm ... doesn't seem like the existing community is particularly "closed" to
new blood to me.

Examining how the new folks got themselves nominated and elected is also
interesting.  In every case, it was based on continuous contributions of
code, documentation, user list help, build script maintenance, or whatever
made a *positive* difference for everyone.  Indeed, if you go back to the
days when folks like Ted and Martin were added, a lot of it was being tired
of applying all the patches they were contributing :-).  All of these folks
"get it" -- so it is not just a couple of dictatorial snobs sitting on top
of the mountain dictating who is in and who is out :-).

There is also another interesting observation here -- you don't have to be a
committer to initiate changes to the Struts code base.  What you have to do
is justify your bugfix or RFE to the point where an existing committer is
willing to take responsibility for cleaning up any messes that committing
the change might cause.  So, you only have to convince one of the various
folks to get your patch in.  Failure to succeed in that goal *could* be a
close minded community, but it also just might be that the proposed change
doesn't fit with what the committers as a whole have in mind (it only takes
one commiter -1 to make a committed change get reversed, so we pay attention
to this as part of the decision process on accepting a patch).  Just in the
little time I have had to spend on Struts in the last year, I've committed
patches from at least 20 different people.  Spread across the six years that
Struts has existed, and all the committers who have done the same thing, we
are talking many *hundreds* of people who have contributed at least some
code or documentation to what is now Struts.

I just don't buy the presumption that the current system is broken.  I won't
presume to convince *you* to think that way -- it's your perogative to think
whatever you want -- but I will certainly take into account whether someone
"gets it" before I would ever vote for them to be a committer.

Fortunately for those who either don't, or don't want to, buy into this, the
Apache license gives you the freedom to take the code and go start your own
community, operating according to your own rules, if you don't like the way
things work here.  But you are starting from a rationale that does not match
the objective facts, so I'm not even going to be interested in trying to
hash out details of how to change something that does not need to be
changed.

Craig

[1] http://struts.apache.org/volunteers.html
[2] http://struts.apache.org/announce.html

Re: Proposal for change

Posted by Niall Pemberton <ni...@gmail.com>.
I'm in favour of this for the reasons I put forward in response to
Craig's post. I have no idea whether it will have the desired effect
or not - but IMO its a good idea and I think we should give it a go.

Niall

On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> Dear Struts community,
>
>
> We have seen a rash of what most people consider "noise" on these lists
> recently, and I can't deny that I was even part of some of it (although
> I hope somewhat more constructively than some).  However, underlying the
> "noise" I feel were a few valid points worth considering.  I for one have.
>
> What I've come away with is a proposal I would like to make.  It would
> represent a procedural change of sorts, or addition to be more accurate.
>  I ask that anyone who has a thought on it please feel free to comment,
> but I ask that you try and do so constructively.  It is not my intention
> to start another 200-post thread that quickly devolves into name-calling
> and insults.
>
> Also, please try not to get hung up on all the details, because they are
> debatable and negotiable (although I have tried to make them reasonable
> to start with).  The two principles described in the conclusion are what
> is really important.  The details of how this would work can be adjusted
> to make everyone happy.
>
>
> A proposal for community-based committer nominations
> ----------------------------------------------------
>
> * Rationale
> One of the issues that a number of people seem to have with the way
> Struts has progressed is the seeming inability (or difficulty at least)
> of getting "new blood" involved.  There seems to be a perception by many
> that there is a bit of a "closed club" mentality with regard to being
> invited in as a committer and that the Struts community at large has no
> say in the matter.
>
> * Proposed Change:
> First, let me make clear that this proposal does NOT change the existing
> mechanism by which someone is invited to be a committer.  That decision
> still rests soley with the PMC.  This proposal only seeks to build on
> top of that mechanism.  I propose that a community-based nomination
> process be instituted.  For the sake of discussion, a "qualified" person
> is anyone that has been on the Struts Dev and/or User mailing lists for
> at least 6 months and has been relatively active (say, at minimum, 2
> posts per week total).  Any qualified person is eligible for nomination,
> or to nominate someone else.  Naturally, a person could never nominate
> themselves.  A nomination must then be seconded by another qualified
> person.  At that point, a voting period of one week commences, where any
> non-committer and non-PMC member, "qualified" or not, may vote (the
> usual +1, 0, -1).  The original nominator is responsible for tallying
> the vote.  A person must receive at least 60% +1's (i.e., 6 out of 10
> must be +1) and no more than half of the remainder may be negative.  At
> the end of that one week period, the vote results will be posted to the
> Dev list and a similar one week period will commence where existing
> Struts team members vote for the nominee.  Also note that at any point,
> the nominee can decline the nomination.  We wouldn't want to offer
> someone up that doesn't want to job!
>
> * Conclusion:
> Once again, let me make perfectly clear that the existing PMC still
> retains 100% control over who is invited to join.  This proposal only
> serves to introduce a mechanism by which members of the community can be
> nominated and force a vote by the PMC.  That is of course the first
> important principle of this proposal.  The other important principle is
> taking the will of the community into account.  By having the PMC not
> vote until AFTER the community has voted, the "will of the community"
> should be apparent, and the idea is that the PMC will take that into
> account when voting.  The community will then have a clear indication
> whether they have been listened to or not based on the outcome of the
> vote (and the comments made during the vote because, after all, there
> ould be legitimate reasons not to adhere to the community's vote, and
> hose reasons should come out in discussion).  But, at the end of the
> day, who is invited to join is still decided by the PMC, as it is today.
>
>
> I look forward to feedback.  Thanks for listening!
>
> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Kimani Darisha <kd...@gmail.com>.
zzzzzzzzzzzzzzzzzzzzz...

On 4/27/06, Jonathan Revusky <re...@wanadoo.es> wrote:
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> blah, blah, blah, bla blah, blah, blah, bla blah, blah, blah, bla
> Now I demand you to answer my blah blah!!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
Jonathan has the patience of a saint in answering people like you.  I
don't.  I am not 10 years old and have no interest in this sort of
discussion.  Grow up!

On 4/27/06, Daniel Warner <wh...@gmail.com> wrote:
>
> Please forgive me for feeding the trolls and wasting bandwidth.  I
> know, it makes me no better than they are and this apology is
> meaningless since I am going to keep doing it for a little while.
> ....but they are just such cute little trolls with those adorable
> nicknames and tiny perspectives!  Seriously, how can you expect anyone
> to resist those?! :)
>
> Besides, it is a slow morning for me, and I do not feel like just
> lurking as usual. :)  I will understand if you all think less of me
> for this utterly juvenile email.  I think less of me too.  Today is
> not a good self-control day. :(
>
> On 4/27/06, Dakota Jack <da...@gmail.com> wrote:
> > People do not do "work" around here because it is not rewarded.
> > The people who are rewarded are political.  Then they do the work and
> the
> > work looks like coding by politicians.
>
> Congratulations, that is the stupidest thing I have heard all week!
> You should be rewarded for being so political!  Or did you not know
> that playing the opposition means you are a politician too?
>
> > I can remember going into the
> > file upload section and seeing one of the worst messes I have ever
> > seen in an open source project.  There are hanging references and
> > other monstrosities that I had only seen community college class
> > assignments prior to looking at Struts code.  I could not even discuss
> > the code much less have any hope of helping, because the committers
> > use this for their work and are not amenable to good code but rather
> > to code that advances their careers.
>
> Then why are you here?  Why do you care if not because you love the
> politics?  Admit it, you are just jealous that you are not on the
> Struts PMC.  Come on, a little self-awareness will not hurt.  I
> promise.
>
> > If you think that Jonathan or I have nothing to contribute, you are
> > sadly mistaken.
>
> Awesome!  I love being called "sadly mistaken".  That is so witty and
> eloquent!  Now if only i could be called that by a truly famous troll
> like Mr. Revusky (there's a little ego stroke for you, JR), my life
> would be complete.
>
> But anyway, it is nice of you to "read my mind" and all, but all I was
> trying to communicate was that Jonathan and myself had not done any of
> the work around here.  I did not say anything about you or anyone's
> ability to contribute. (Though I think it is cute that you wanted to
> be in on the action. :)
>
> > We are quite aware of the nature of this beast.  You
> > really need to pay attention to what is going on.  There is nothing
> > like a meritocracy around here.
>
> (In unworthy imitation of the inimitable Bill Cosby)  ......right.
>
> > How do you think that Struts 1.x
> > managed to become a plate of spaghetti after such a fine start?
>
> Well, I do not think that.  I know that seems odd to you, but I
> actually lurk on this list because I think Struts 1.x was a decently
> constructed ham and cheese sandwich.  I am also excited to see it
> turning into a delicious BLT with the introduction of WebWork as SAF
> 2.
>
> > Mertiocracy does not mean just work, by the way.  It means work with
> > merit.  This not sold as a "docracy" or "actcracy".
>
> This is the second stupidest thing I have heard all week.  Thank you
> for sharing!
>
> > Get a clue.
>
> A clue?  Like the board game?  I love board games!  Would you like to
> play a game of "Sorry"?  CandyLand is fun too.
>
> Daniel Warner,
> lead time waster and troll feeder
> (for today only, I promise I will go back to lurking tomorrow!)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Daniel Warner <wh...@gmail.com>.
Please forgive me for feeding the trolls and wasting bandwidth.  I
know, it makes me no better than they are and this apology is
meaningless since I am going to keep doing it for a little while. 
....but they are just such cute little trolls with those adorable
nicknames and tiny perspectives!  Seriously, how can you expect anyone
to resist those?! :)

Besides, it is a slow morning for me, and I do not feel like just
lurking as usual. :)  I will understand if you all think less of me
for this utterly juvenile email.  I think less of me too.  Today is
not a good self-control day. :(

On 4/27/06, Dakota Jack <da...@gmail.com> wrote:
> People do not do "work" around here because it is not rewarded.
> The people who are rewarded are political.  Then they do the work and the
> work looks like coding by politicians.

Congratulations, that is the stupidest thing I have heard all week! 
You should be rewarded for being so political!  Or did you not know
that playing the opposition means you are a politician too?

> I can remember going into the
> file upload section and seeing one of the worst messes I have ever
> seen in an open source project.  There are hanging references and
> other monstrosities that I had only seen community college class
> assignments prior to looking at Struts code.  I could not even discuss
> the code much less have any hope of helping, because the committers
> use this for their work and are not amenable to good code but rather
> to code that advances their careers.

Then why are you here?  Why do you care if not because you love the
politics?  Admit it, you are just jealous that you are not on the
Struts PMC.  Come on, a little self-awareness will not hurt.  I
promise.

> If you think that Jonathan or I have nothing to contribute, you are
> sadly mistaken.

Awesome!  I love being called "sadly mistaken".  That is so witty and
eloquent!  Now if only i could be called that by a truly famous troll
like Mr. Revusky (there's a little ego stroke for you, JR), my life
would be complete.

But anyway, it is nice of you to "read my mind" and all, but all I was
trying to communicate was that Jonathan and myself had not done any of
the work around here.  I did not say anything about you or anyone's
ability to contribute. (Though I think it is cute that you wanted to
be in on the action. :)

> We are quite aware of the nature of this beast.  You
> really need to pay attention to what is going on.  There is nothing
> like a meritocracy around here.

(In unworthy imitation of the inimitable Bill Cosby)  ......right.

> How do you think that Struts 1.x
> managed to become a plate of spaghetti after such a fine start?

Well, I do not think that.  I know that seems odd to you, but I
actually lurk on this list because I think Struts 1.x was a decently
constructed ham and cheese sandwich.  I am also excited to see it
turning into a delicious BLT with the introduction of WebWork as SAF
2.

> Mertiocracy does not mean just work, by the way.  It means work with
> merit.  This not sold as a "docracy" or "actcracy".

This is the second stupidest thing I have heard all week.  Thank you
for sharing!

> Get a clue.

A clue?  Like the board game?  I love board games!  Would you like to
play a game of "Sorry"?  CandyLand is fun too.

Daniel Warner,
lead time waster and troll feeder
(for today only, I promise I will go back to lurking tomorrow!)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
People do not do "work" around here because it is not rewarded.  The
people who are rewarded are political.  Then they do the work and the
work looks like coding by politicians.  I can remember going into the
file upload section and seeing one of the worst messes I have ever
seen in an open source project.  There are hanging references and
other monstrosities that I had only seen community college class
assignments prior to looking at Struts code.  I could not even discuss
the code much less have any hope of helping, because the committers
use this for their work and are not amenable to good code but rather
to code that advances their careers.


If you think that Jonathan or I have nothing to contribute, you are
sadly mistaken.  We are quite aware of the nature of this beast.  You
really need to pay attention to what is going on.  There is nothing
like a meritocracy around here.  How do you think that Struts 1.x
managed to become a plate of spaghetti after such a fine start?


Mertiocracy does not mean just work, by the way.  It means work with
merit.  This not sold as a "docracy" or "actcracy".  Get a clue.




<snip>
On 4/27/06, Daniel Warner <wh...@gmail.com> wrote:
> > The only principle I see is the principle of incumbency or tenure.
>
> That's a problem with your vision.  There are plenty of reasons:
>
> 1) it's more about doing the work than doing the work "better".
> 2) SAF 2/WebWork is still in incubation.  It's not even actually part
> of Struts yet.
> 3) The Struts PMC currently oversees Shale, Tiles, and SAF 1.  WebWork
> is not the only project here.
</snip>
--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Michael Jouravlev <jm...@gmail.com>.
Decembrists awakened Herzen. Herzen launched revolutionary propaganda campaign.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Jonathan Revusky <re...@wanadoo.es>.
Daniel Warner wrote:
> On 4/27/06, Jonathan Revusky <re...@wanadoo.es> wrote:
> 
>>Dakota Jack wrote:
>>
>>>Doesn't this kind of talk sound goofy to you all?  Isn't this reference to
>>>the Apache Way sort of like a secret handshake and a silly hat?
>>
>>It's all that, yes, but it's also not very honest, I'd say.
>>
>>You see, the various scripture on the so-called "Apache Way" claims that
>>the ASF is run as a "meritocracy". What you see here is that the Struts
>>committers, after years of not achieving much, have invited in the
>>Webwork people with the intention of relabelling Webwork as Struts
>>Action 2 (when the existing Struts codebase is Struts Action 1). They
>>tacitly accept that the Webwork people ran the better project
>>technically, did the better work.
>>
>>Well, once you accept that the other people did the better work, and you
>>have a meritocracy, then those other people, who have more merit, they
>>run the show.
>>
>>The logic of this looks unassailble to me.
> 
> 
> That's because you don't understand what you're talking about. 

<sigh>

> The
> "meritocracy" idea at Apache is not about who does the work best. 
> It's just about who does the work.  You do the work, you make
> decisions.

<LOL>

You're joking, aren't you, Daniel? You're saying this is a "meritocracy" 
in which you gain merit by doing work, but the quality of the work 
doesn't matter?

OMG... I think maybe you're serious...

Well, that's just ridiculous, isn't it???? C'mon...

> 
>>So, by what basic principle does the existing Struts PMC remain in
>>control of the project when they accept that the other people did better
>>work?
>>
>>The only principle I see is the principle of incumbency or tenure.
> 
> 
> That's a problem with your vision.  There are plenty of reasons:
> 
> 1) it's more about doing the work than doing the work "better".

No further comment.


> 2) SAF 2/WebWork is still in incubation.  It's not even actually part
> of Struts yet.

<sigh>

The "incubator" is just ASF pseudoreality. It doesn't correspond to 
anything real. It makes no sense in this context. An actual incubator is 
something you use to hatch eggs, or sometimes it refers to a kind of 
environment that prematurely born babies are put in, because they could 
not survive in the outside world yet.

The living entity that you incubate is not even an infant, it is 
something in an embryonic state. Talking about how Webwork is still in 
"incubation" does not reflect anything real, because Webwork is not an 
unborn baby or even an infant. It is the moral equivalent of an adult, a 
peer of the Struts project and other projects in its space.

This whole business of mature projects like Webwork being "incubated" is 
just yet another striking example of the kind of bizarre use of words 
that is resorted to when people talk about this so-called "Apache Way".

The "incubator" is like the "meritocracy". Even though the term is being 
used as a kind of analogy, it does such violence to the normal meaning 
of the English word that it's hard to even have a sensible conversation 
about it.

> 3) The Struts PMC currently oversees Shale, Tiles, and SAF 1.  WebWork
> is not the only project here.

Until recently, SAF 1 was simply what was called "Struts". The status of 
the Struts developers is based on the existence of that codebase.

My point was that, when they accept that Webwork is simply better, as 
evidenced by calling it SAF 2, when Struts itself is SAF 1, this means 
that the Webwork people did superior work.

People who did inferior work overseeing or managing the people who did 
the better work, does not, prima facie, correspond to the basic logic 
and structure of what anybody would call a meritocracy.

> 
> 
>>When people who did inferior work remain the managers of a project (and
>>ostensibly manage the people who did the better work) and this is by
>>virtue of incumbency or tenure, you don't have a meritocracy.
> 
> 
> And all you have is a strawman.  Pay attention to how things actually
> are run around here. 

I've been watching.

> The PMC doesn't "manage" other committers.  

Maybe they don't. However, I think the 'M' in PMC stands for 
"management". But okay, the PMC doesn't actually do any managing, the 
incubator doesn't do anything that anybody sensible would call 
"incubating". The "merit" in the meritocracy has nothing to do with the 
quality of anybody's work...

Fine, be my guest....

Really, when people accuse one of not understanding the "Apache Way", it 
may be a kind of compliment. Frankly, I would be automatically quite 
suspicious of anybody who asserts that they really understand all this 
stuff. Now, okay, the projects that want to get branded as Apache 
projects, the people involved have to demonstrate that they "get" this 
Apache Way, but that's more like having to agree with some lunatics 
because it's the easier path.

"Yeah, I get it, I really dig the Apache Way. Cripes, I don't know how 
we actually developed all this code we developed outside ASF when we 
didn't even have the Apache Way, though somehow we did. But now I see 
the error of our ways. Yessah, I see the light."

"Praise be the Lawd! Hallelujah!"

> In
> practice, any committer's -1 is as meaningful as a PMC members.  In
> fact, if a contributor who is not a committer has something to say
> about the code they've contributed, then the PMC will respect that
> too.  In fact, i'm fairly sure these principles are actually codified
> somewhere in the "Apache scriptures".  Them that do the work make the
> decisions.  That's a meritocracy, if you ask me.

No comment...

> 
> Oh, and i seem to recall reading once in a Jakarta discussion that the
> ideal situation to the ASF is if all committers for a project are on
> the PMC that oversees the project.  Does that sound like it has
> anything to do with who does better work? hmm.

I dunno, but it doesn't have anything to do with what is happening in 
Struts, because in Struts, not all the committers are in the PMC...

> 
> 
>>So, actually, seriously applying the principles outlined about
>>meritocracy would necessarily imply an extreme shake-up in the Struts
>>project. However, in a typically ass backwards way, the "Apache Way"
>>stuff is being used as a rhetorical instrument to quell dissent --
>>"don't rock the boat". As another example of ass backwards rhetoric, in
>>his "This has gone too far" post, Don Brown implies that the reason for
>>a lack of forward progress is the presence of that discussion. But that
>>is 180ยบ away. That and other such discussions came about precisely
>>because of the lack of forward progress. The causality is in completely
>>the other direction.
>>
>>Of course, it's clear why there's an attempt to shut down any discussion
>>that casts doubt on the way in which certain people are club members and
>>others are not. It has nothing to do with any "Apache Way". It can't be
>>openly discussed because, in reality, the incumbent managers of the
>>project do not have a leg to stand on. If they accepted the basic logic
>>of a meritocracy, Don and Ted and the rest would have to just resign and
>>let new people in.
> 
> 
> If they accepted your personally expedient definition of a
> meritocracy, then maybe. 

I'm sorry, Daniel, you are a very confused individual. I am most 
certainly not the one promulgating a "personally expedient definition of 
meritocracy"....

> But Apache doesn't care what Jonathan
> Revusky thinks, because Jonathan Revusky doesn't do a lick of work for
> the ASF community (much like me). 

No, that's a false symmetry. I don't work within ASF, but I contribute 
to the overall space. The FreeMarker template engine is a core 
dependency in Webwork, which will eventually be SAF 2. Many people also 
use SAF 1 in conjunction with FreeMarker.

I am making political comments of a certain nature about a space in 
which I have made significant contributions. This is, I think, quite 
different from your situation, Daniel.


> It is you and i who have no legs to
> stand on here.  Don and Ted do tons of work, and therefore have all
> the legs they need and more.  Just pay attention to this list for a
> week and that will be obvious.


Well, they and the others on the Struts PMC are in a position where they 
have to answer certain questions regarding the lack of technical 
progress on Struts 1.x IMO. That they do a lot of work themselves is 
almost completely beside the point. An incompetent manager typically 
will end up having to do a lot more work than a competent one. The 
competent one manages to get other people involved and delegates work to 
them, where the incompetent one ends up having to do everything himself.

Don and Ted may do all kinds of work, but Struts development stagnated. 
Maybe they could have structured things better to get other people 
involved who would carry things forward.

But anyway, even if they've put in a herculean effort, things must be 
judged by the objective results. The objective results in the case of 
Struts 1.x are really quite poor. And that is where the basic logic and 
structure of meritocracy really would kick in -- that is, if this really 
was being run as a meritocracy....

Jonathan Revusky
--
lead developer, FreeMarker project, http://freemarker.org/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Daniel Warner <wh...@gmail.com>.
On 4/27/06, Jonathan Revusky <re...@wanadoo.es> wrote:
> Dakota Jack wrote:
> > Doesn't this kind of talk sound goofy to you all?  Isn't this reference to
> > the Apache Way sort of like a secret handshake and a silly hat?
>
> It's all that, yes, but it's also not very honest, I'd say.
>
> You see, the various scripture on the so-called "Apache Way" claims that
> the ASF is run as a "meritocracy". What you see here is that the Struts
> committers, after years of not achieving much, have invited in the
> Webwork people with the intention of relabelling Webwork as Struts
> Action 2 (when the existing Struts codebase is Struts Action 1). They
> tacitly accept that the Webwork people ran the better project
> technically, did the better work.
>
> Well, once you accept that the other people did the better work, and you
> have a meritocracy, then those other people, who have more merit, they
> run the show.
>
> The logic of this looks unassailble to me.

That's because you don't understand what you're talking about.  The
"meritocracy" idea at Apache is not about who does the work best. 
It's just about who does the work.  You do the work, you make
decisions.

> So, by what basic principle does the existing Struts PMC remain in
> control of the project when they accept that the other people did better
> work?
>
> The only principle I see is the principle of incumbency or tenure.

That's a problem with your vision.  There are plenty of reasons:

1) it's more about doing the work than doing the work "better".
2) SAF 2/WebWork is still in incubation.  It's not even actually part
of Struts yet.
3) The Struts PMC currently oversees Shale, Tiles, and SAF 1.  WebWork
is not the only project here.

> When people who did inferior work remain the managers of a project (and
> ostensibly manage the people who did the better work) and this is by
> virtue of incumbency or tenure, you don't have a meritocracy.

And all you have is a strawman.  Pay attention to how things actually
are run around here.  The PMC doesn't "manage" other committers.  In
practice, any committer's -1 is as meaningful as a PMC members.  In
fact, if a contributor who is not a committer has something to say
about the code they've contributed, then the PMC will respect that
too.  In fact, i'm fairly sure these principles are actually codified
somewhere in the "Apache scriptures".  Them that do the work make the
decisions.  That's a meritocracy, if you ask me.

Oh, and i seem to recall reading once in a Jakarta discussion that the
ideal situation to the ASF is if all committers for a project are on
the PMC that oversees the project.  Does that sound like it has
anything to do with who does better work? hmm.

> So, actually, seriously applying the principles outlined about
> meritocracy would necessarily imply an extreme shake-up in the Struts
> project. However, in a typically ass backwards way, the "Apache Way"
> stuff is being used as a rhetorical instrument to quell dissent --
> "don't rock the boat". As another example of ass backwards rhetoric, in
> his "This has gone too far" post, Don Brown implies that the reason for
> a lack of forward progress is the presence of that discussion. But that
> is 180ยบ away. That and other such discussions came about precisely
> because of the lack of forward progress. The causality is in completely
> the other direction.
>
> Of course, it's clear why there's an attempt to shut down any discussion
> that casts doubt on the way in which certain people are club members and
> others are not. It has nothing to do with any "Apache Way". It can't be
> openly discussed because, in reality, the incumbent managers of the
> project do not have a leg to stand on. If they accepted the basic logic
> of a meritocracy, Don and Ted and the rest would have to just resign and
> let new people in.

If they accepted your personally expedient definition of a
meritocracy, then maybe.  But Apache doesn't care what Jonathan
Revusky thinks, because Jonathan Revusky doesn't do a lick of work for
the ASF community (much like me).  It is you and i who have no legs to
stand on here.  Don and Ted do tons of work, and therefore have all
the legs they need and more.  Just pay attention to this list for a
week and that will be obvious.

> Jonathan Revusky
> --
> lead developer, FreeMarker project, http://freemarker.org/
> lead anti-Apache troll, http://freemarker.blogspot.com/
>
>
>
>
>
>
>
>
> > Let's say
> > what the Struts Way is.  It is not, I would strongly suggest even slightly
> > related to the Apache Way.  I am also strongly considering just never coming
> > back here.  I am getting just to sick of the plain and unvarinshed stupidity
> > on this list.
> >
> > On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
> >
> >>On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> >>
> >>>On Tue, April 25, 2006 2:22 pm, Paul Speed said:
> >>>
> >>>>
> >>>>Frank W. Zammetti wrote:
> >>>>
> >>>>
> >>>>>You are of course right about this.  But, much like taking the ideas
> >>>>>about
> >>>>>inventory control and order processing and such from Dell and
> >>
> >>starting
> >>
> >>>>>your own business is possible, the likelihood that you would get
> >>>>>anything
> >>>>>but a small fraction of the attention and business that Dell gets is
> >>>>>slim
> >>>>>to none.
> >>>>
> >>>>Not to sidle in where I don't really belong but perhaps this last
> >>>>sentence exemplifies the disconnect with "getting it"?  If one wanted
> >>
> >>to
> >>
> >>>>take the code from an apache project and do something else with it
> >>
> >>then
> >>
> >>>>all they care about is the something else they want to do.  It isn't
> >>>>really a "business"... the code exists for the code's sake.
> >>>
> >>>You aren't chiming in where you don't belong... if your interested, you
> >>>belong, at least as far as I'm concerned :)
> >>>
> >>>I think there is definitely something to your point, and the analogy may
> >>>have been a bit flawed.  However...
> >>>
> >>>I don't think it is accurate to think that ego doesn't play a part in
> >>
> >>just
> >>
> >>>about everything that just about everyone does.  We all want to see our
> >>>work benefit others.  For most of us I believe its because we genuinely
> >>>like the feeling we get when someone writes us and says "hey, your code
> >>>really helped me, thank you!".  I know speaking for myself, it makes my
> >>>day when I get those eMails!  Part of it is simply the ego stroke of
> >>>someone essentially saying your work is worth something, but I don't
> >>>believe that is the big factor for most people.  I know it isn't for me,
> >>>and I don't think it is for the Struts team.  I think the thank you note
> >>>means as much to them as it does me.
> >>>
> >>>If you agree with that, then the idea of forking the code and doing it
> >>>with the belief that you aren't going to reach a wide audience because
> >>
> >>the
> >>
> >>>Apache version continues to be what people go to, is not appealing.  In
> >>>that regard, if we substitute ego for money in the analogy, I think it
> >>>still works (although just saying ego is dangerous because as I tried to
> >>>illustrate above, I think there is good ego and bad ego).
> >>>
> >>>
> >>>>I'm not a committer but I've been following this list and the tomcat
> >>
> >>dev
> >>
> >>>>list since the last millennium... I think before there even was a
> >>
> >>struts
> >>
> >>>>1.0.  I can't speak in an official capacity, I can't even pretend, but
> >>>>here is my take on the "apache way".
> >>>
> >>>Isn't kind of interesting that there can be more than one "take" on it
> >>>though?
> >>>
> >>>
> >>>>For an open source project to exist you need code.  All of apache
> >>>>projects seem to exist to benefit the code... and by extension the
> >>>>documentation.  Though, even without documentation you still have the
> >>>>code.  All of the other stuff is extraneous or the life support system
> >>>>depending on how you look at it.  I think most of the "apache way" is
> >>>>partially considering it to be extraneous... in a "if the code goes
> >>
> >>sour
> >>
> >>>>and you have nothing" sort of way.  It's definitely symbiotic but
> >>>>without the code, you have nothing.  You might as well be chatting on
> >>>>myspace.com.
> >>>
> >>>Hehe, considering some of the recent threads around here, posting on
> >>>myspace.com might actually be safer! :-) LOL
> >>>
> >>>
> >>>>So, the only reason to be a committer is to contribute to the
> >>>>codebase... and all other committers have to live with each
> >>
> >>other.  The
> >>
> >>>>only reason to be able to cast a binding vote is if you have a stake
> >>
> >>in
> >>
> >>>>the code... ie: are a committer.
> >>>
> >>>This is where I'm not sure I agree... why can you only have a stake in
> >>
> >>the
> >>
> >>>code, or in the community even, if you are a committer?  And certainly
> >>
> >>the
> >>
> >>>"community" is often touted as the most important part of any ASF
> >>>project... it's just that "community" in that context means the
> >>
> >>committers
> >>
> >>>only, which is where I disagree with the Apache Way I guess.
> >>
> >>
> >>No, that's not correct. The community is, as you put it earlier, "anyone
> >>who
> >>has an active interest in how the project develops". So you actually agree
> >>with the Apache Way. ;-)
> >>
> >>--
> >>Martin Cooper
> >>
> >>
> >>Simply putting code out there and sharing your work is great, but going
> >>
> >>>back to a point I made some weeks ago, I beleive there is a
> >>
> >>responsibility
> >>
> >>>that comes along with it when you do that.  Whether they should or not,
> >>>people become dependent on the project... not in a cocaine kind of way
> >>
> >>of
> >>
> >>>course, but they are "counting on you" basically.  That to me implies
> >>>taking into consideration their needs and wants.  Not above your own of
> >>>course, but to some degree.
> >>>
> >>>
> >>>>Bottom line: if a person isn't contributing to code and documentation
> >>
> >>in
> >>
> >>>>a way that the other committers are comfortable with then that person
> >>>>shouldn't be a committer on the project.  There is no other reason for
> >>>>being a committer.
> >>>
> >>>This I absolutely agree with, and it was the reason my proposal didn't
> >>
> >>try
> >>
> >>>to change that.  I would NEVER propose that the PMC not have the final
> >>
> >>say
> >>
> >>>in who is invited.  It just to me seems right for that to be the case.
> >>>But, I still see nothing wrong with being able to say "hey, PMC, we
> >>
> >>think
> >>
> >>>this guy or gal would be a good addition, please consider him".
> >>>
> >>>
> >>>>My personal (and probably unneeded) opinion on the original subject:
> >>>>
> >>>> From my perspective, nominations don't matter so much... as I recall
> >>>>someone could nominate themselves.  If that person hasn't been
> >>>>contributing code then there is no reason to think they will become a
> >>>>committer.
> >>>
> >>>That is correct.  I frankly was not aware that someone could do that,
> >>
> >>Ted
> >>
> >>>pointed it out to me.  As I replied previously, that indeed covers the
> >>>first principle of my proposal.  I always prefer things like that be
> >>
> >>more
> >>
> >>>concrete, i.e., rules layed out in document form, but even failing that
> >>
> >>I
> >>
> >>>think the principle is followed, so I'm happy.
> >>>
> >>>
> >>>>It would be nice if the process were a little more transparent as it
> >>>>would be interesting to know who was proposed, accepted, rejected,
> >>
> >>etc.
> >>
> >>>>even if we didn't know why.  (Though, even counter to that it was nice
> >>>>to know that someone who contributed to another apache project and
> >>>>stomped all over my contributed implementation because they didn't
> >>>>bother to patch to head was at least a controversial nomination.  But
> >>>>that's sort of personal and isolated reason for wanting to see the
> >>
> >>dirty
> >>
> >>>>laundry.)
> >>>
> >>>I still have the concerns about people being embarassed by
> >>
> >>this.  However,
> >>
> >>>I think the idea of a nominee accepting the nomination first is a fair
> >>>idea.  Putting aside the original proposal, how would that simple
> >>
> >>change,
> >>
> >>>along with opening the vote process discussion for all to see, sit with
> >>>everyone?
> >>>
> >>>
> >>>>I guess I have trouble seeing how things could be improved much by
> >>
> >>your
> >>
> >>>>proposal... especially since I understood there to be nothing wrong
> >>
> >>with
> >>
> >>>>nominations coming from anywhere.  It was just explained to be easier
> >>>>with a committer's support.  I don't follow this list too closely, so
> >>>>maybe I missed someone who has been contributing lots of stuff and
> >>
> >>still
> >>
> >>>>was overlooked.
> >>>
> >>>Agreed, once Ted explained that point to me, the proposal isn't quite as
> >>>strong as I thought at first.  I still think there is the issue of
> >>>transparency that could do with further discussion, but it seems the
> >>>nomination part of it is, more or less, already present.  Codifying it
> >>>would be nice, but I can live with it not being written anywhere.
> >>>
> >>>Thanks for commenting, you are always welcome as far as I'm concerned :)
> >>>
> >>>
> >>>>-Paul
> >>>
> >>>Frank
> >>>
> >>>---------------------------------------------------------------------
> >>>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>>For additional commands, e-mail: dev-help@struts.apache.org
> >>>
> >>>
> >>
> >>
> >
> >
> > --
> > "You can lead a horse to water but you cannot make it float on its back."
> > ~Dakota Jack~
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Jonathan Revusky <re...@wanadoo.es>.
Dakota Jack wrote:
> Doesn't this kind of talk sound goofy to you all?  Isn't this reference to
> the Apache Way sort of like a secret handshake and a silly hat? 

It's all that, yes, but it's also not very honest, I'd say.

You see, the various scripture on the so-called "Apache Way" claims that 
the ASF is run as a "meritocracy". What you see here is that the Struts 
committers, after years of not achieving much, have invited in the 
Webwork people with the intention of relabelling Webwork as Struts 
Action 2 (when the existing Struts codebase is Struts Action 1). They 
tacitly accept that the Webwork people ran the better project 
technically, did the better work.

Well, once you accept that the other people did the better work, and you 
have a meritocracy, then those other people, who have more merit, they 
run the show.

The logic of this looks unassailble to me.

So, by what basic principle does the existing Struts PMC remain in 
control of the project when they accept that the other people did better 
work?

The only principle I see is the principle of incumbency or tenure.

When people who did inferior work remain the managers of a project (and 
ostensibly manage the people who did the better work) and this is by 
virtue of incumbency or tenure, you don't have a meritocracy.

So, actually, seriously applying the principles outlined about 
meritocracy would necessarily imply an extreme shake-up in the Struts 
project. However, in a typically ass backwards way, the "Apache Way" 
stuff is being used as a rhetorical instrument to quell dissent -- 
"don't rock the boat". As another example of ass backwards rhetoric, in 
his "This has gone too far" post, Don Brown implies that the reason for 
a lack of forward progress is the presence of that discussion. But that 
is 180ยบ away. That and other such discussions came about precisely 
because of the lack of forward progress. The causality is in completely 
the other direction.

Of course, it's clear why there's an attempt to shut down any discussion 
that casts doubt on the way in which certain people are club members and 
others are not. It has nothing to do with any "Apache Way". It can't be 
openly discussed because, in reality, the incumbent managers of the 
project do not have a leg to stand on. If they accepted the basic logic 
of a meritocracy, Don and Ted and the rest would have to just resign and 
let new people in.

Jonathan Revusky
--
lead developer, FreeMarker project, http://freemarker.org/
FreeMarker blog, http://freemarker.blogspot.com/








> Let's say
> what the Struts Way is.  It is not, I would strongly suggest even slightly
> related to the Apache Way.  I am also strongly considering just never coming
> back here.  I am getting just to sick of the plain and unvarinshed stupidity
> on this list.
> 
> On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
> 
>>On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>>
>>>On Tue, April 25, 2006 2:22 pm, Paul Speed said:
>>>
>>>>
>>>>Frank W. Zammetti wrote:
>>>>
>>>>
>>>>>You are of course right about this.  But, much like taking the ideas
>>>>>about
>>>>>inventory control and order processing and such from Dell and
>>
>>starting
>>
>>>>>your own business is possible, the likelihood that you would get
>>>>>anything
>>>>>but a small fraction of the attention and business that Dell gets is
>>>>>slim
>>>>>to none.
>>>>
>>>>Not to sidle in where I don't really belong but perhaps this last
>>>>sentence exemplifies the disconnect with "getting it"?  If one wanted
>>
>>to
>>
>>>>take the code from an apache project and do something else with it
>>
>>then
>>
>>>>all they care about is the something else they want to do.  It isn't
>>>>really a "business"... the code exists for the code's sake.
>>>
>>>You aren't chiming in where you don't belong... if your interested, you
>>>belong, at least as far as I'm concerned :)
>>>
>>>I think there is definitely something to your point, and the analogy may
>>>have been a bit flawed.  However...
>>>
>>>I don't think it is accurate to think that ego doesn't play a part in
>>
>>just
>>
>>>about everything that just about everyone does.  We all want to see our
>>>work benefit others.  For most of us I believe its because we genuinely
>>>like the feeling we get when someone writes us and says "hey, your code
>>>really helped me, thank you!".  I know speaking for myself, it makes my
>>>day when I get those eMails!  Part of it is simply the ego stroke of
>>>someone essentially saying your work is worth something, but I don't
>>>believe that is the big factor for most people.  I know it isn't for me,
>>>and I don't think it is for the Struts team.  I think the thank you note
>>>means as much to them as it does me.
>>>
>>>If you agree with that, then the idea of forking the code and doing it
>>>with the belief that you aren't going to reach a wide audience because
>>
>>the
>>
>>>Apache version continues to be what people go to, is not appealing.  In
>>>that regard, if we substitute ego for money in the analogy, I think it
>>>still works (although just saying ego is dangerous because as I tried to
>>>illustrate above, I think there is good ego and bad ego).
>>>
>>>
>>>>I'm not a committer but I've been following this list and the tomcat
>>
>>dev
>>
>>>>list since the last millennium... I think before there even was a
>>
>>struts
>>
>>>>1.0.  I can't speak in an official capacity, I can't even pretend, but
>>>>here is my take on the "apache way".
>>>
>>>Isn't kind of interesting that there can be more than one "take" on it
>>>though?
>>>
>>>
>>>>For an open source project to exist you need code.  All of apache
>>>>projects seem to exist to benefit the code... and by extension the
>>>>documentation.  Though, even without documentation you still have the
>>>>code.  All of the other stuff is extraneous or the life support system
>>>>depending on how you look at it.  I think most of the "apache way" is
>>>>partially considering it to be extraneous... in a "if the code goes
>>
>>sour
>>
>>>>and you have nothing" sort of way.  It's definitely symbiotic but
>>>>without the code, you have nothing.  You might as well be chatting on
>>>>myspace.com.
>>>
>>>Hehe, considering some of the recent threads around here, posting on
>>>myspace.com might actually be safer! :-) LOL
>>>
>>>
>>>>So, the only reason to be a committer is to contribute to the
>>>>codebase... and all other committers have to live with each
>>
>>other.  The
>>
>>>>only reason to be able to cast a binding vote is if you have a stake
>>
>>in
>>
>>>>the code... ie: are a committer.
>>>
>>>This is where I'm not sure I agree... why can you only have a stake in
>>
>>the
>>
>>>code, or in the community even, if you are a committer?  And certainly
>>
>>the
>>
>>>"community" is often touted as the most important part of any ASF
>>>project... it's just that "community" in that context means the
>>
>>committers
>>
>>>only, which is where I disagree with the Apache Way I guess.
>>
>>
>>No, that's not correct. The community is, as you put it earlier, "anyone
>>who
>>has an active interest in how the project develops". So you actually agree
>>with the Apache Way. ;-)
>>
>>--
>>Martin Cooper
>>
>>
>>Simply putting code out there and sharing your work is great, but going
>>
>>>back to a point I made some weeks ago, I beleive there is a
>>
>>responsibility
>>
>>>that comes along with it when you do that.  Whether they should or not,
>>>people become dependent on the project... not in a cocaine kind of way
>>
>>of
>>
>>>course, but they are "counting on you" basically.  That to me implies
>>>taking into consideration their needs and wants.  Not above your own of
>>>course, but to some degree.
>>>
>>>
>>>>Bottom line: if a person isn't contributing to code and documentation
>>
>>in
>>
>>>>a way that the other committers are comfortable with then that person
>>>>shouldn't be a committer on the project.  There is no other reason for
>>>>being a committer.
>>>
>>>This I absolutely agree with, and it was the reason my proposal didn't
>>
>>try
>>
>>>to change that.  I would NEVER propose that the PMC not have the final
>>
>>say
>>
>>>in who is invited.  It just to me seems right for that to be the case.
>>>But, I still see nothing wrong with being able to say "hey, PMC, we
>>
>>think
>>
>>>this guy or gal would be a good addition, please consider him".
>>>
>>>
>>>>My personal (and probably unneeded) opinion on the original subject:
>>>>
>>>> From my perspective, nominations don't matter so much... as I recall
>>>>someone could nominate themselves.  If that person hasn't been
>>>>contributing code then there is no reason to think they will become a
>>>>committer.
>>>
>>>That is correct.  I frankly was not aware that someone could do that,
>>
>>Ted
>>
>>>pointed it out to me.  As I replied previously, that indeed covers the
>>>first principle of my proposal.  I always prefer things like that be
>>
>>more
>>
>>>concrete, i.e., rules layed out in document form, but even failing that
>>
>>I
>>
>>>think the principle is followed, so I'm happy.
>>>
>>>
>>>>It would be nice if the process were a little more transparent as it
>>>>would be interesting to know who was proposed, accepted, rejected,
>>
>>etc.
>>
>>>>even if we didn't know why.  (Though, even counter to that it was nice
>>>>to know that someone who contributed to another apache project and
>>>>stomped all over my contributed implementation because they didn't
>>>>bother to patch to head was at least a controversial nomination.  But
>>>>that's sort of personal and isolated reason for wanting to see the
>>
>>dirty
>>
>>>>laundry.)
>>>
>>>I still have the concerns about people being embarassed by
>>
>>this.  However,
>>
>>>I think the idea of a nominee accepting the nomination first is a fair
>>>idea.  Putting aside the original proposal, how would that simple
>>
>>change,
>>
>>>along with opening the vote process discussion for all to see, sit with
>>>everyone?
>>>
>>>
>>>>I guess I have trouble seeing how things could be improved much by
>>
>>your
>>
>>>>proposal... especially since I understood there to be nothing wrong
>>
>>with
>>
>>>>nominations coming from anywhere.  It was just explained to be easier
>>>>with a committer's support.  I don't follow this list too closely, so
>>>>maybe I missed someone who has been contributing lots of stuff and
>>
>>still
>>
>>>>was overlooked.
>>>
>>>Agreed, once Ted explained that point to me, the proposal isn't quite as
>>>strong as I thought at first.  I still think there is the issue of
>>>transparency that could do with further discussion, but it seems the
>>>nomination part of it is, more or less, already present.  Codifying it
>>>would be nice, but I can live with it not being written anywhere.
>>>
>>>Thanks for commenting, you are always welcome as far as I'm concerned :)
>>>
>>>
>>>>-Paul
>>>
>>>Frank
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>>
> 
> 
> --
> "You can lead a horse to water but you cannot make it float on its back."
> ~Dakota Jack~
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by netsql <ne...@roomity.com>.
You are bluffing Jack!
.V

Dakota Jack wrote:
  I am also strongly considering just never coming
> back here.  


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
Doesn't this kind of talk sound goofy to you all?  Isn't this reference to
the Apache Way sort of like a secret handshake and a silly hat?  Let's say
what the Struts Way is.  It is not, I would strongly suggest even slightly
related to the Apache Way.  I am also strongly considering just never coming
back here.  I am getting just to sick of the plain and unvarinshed stupidity
on this list.

On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>
> On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> >
> > On Tue, April 25, 2006 2:22 pm, Paul Speed said:
> > >
> > >
> > > Frank W. Zammetti wrote:
> > >
> > >>
> > >> You are of course right about this.  But, much like taking the ideas
> > >> about
> > >> inventory control and order processing and such from Dell and
> starting
> > >> your own business is possible, the likelihood that you would get
> > >> anything
> > >> but a small fraction of the attention and business that Dell gets is
> > >> slim
> > >> to none.
> > >
> > > Not to sidle in where I don't really belong but perhaps this last
> > > sentence exemplifies the disconnect with "getting it"?  If one wanted
> to
> > > take the code from an apache project and do something else with it
> then
> > > all they care about is the something else they want to do.  It isn't
> > > really a "business"... the code exists for the code's sake.
> >
> > You aren't chiming in where you don't belong... if your interested, you
> > belong, at least as far as I'm concerned :)
> >
> > I think there is definitely something to your point, and the analogy may
> > have been a bit flawed.  However...
> >
> > I don't think it is accurate to think that ego doesn't play a part in
> just
> > about everything that just about everyone does.  We all want to see our
> > work benefit others.  For most of us I believe its because we genuinely
> > like the feeling we get when someone writes us and says "hey, your code
> > really helped me, thank you!".  I know speaking for myself, it makes my
> > day when I get those eMails!  Part of it is simply the ego stroke of
> > someone essentially saying your work is worth something, but I don't
> > believe that is the big factor for most people.  I know it isn't for me,
> > and I don't think it is for the Struts team.  I think the thank you note
> > means as much to them as it does me.
> >
> > If you agree with that, then the idea of forking the code and doing it
> > with the belief that you aren't going to reach a wide audience because
> the
> > Apache version continues to be what people go to, is not appealing.  In
> > that regard, if we substitute ego for money in the analogy, I think it
> > still works (although just saying ego is dangerous because as I tried to
> > illustrate above, I think there is good ego and bad ego).
> >
> > > I'm not a committer but I've been following this list and the tomcat
> dev
> > > list since the last millennium... I think before there even was a
> struts
> > > 1.0.  I can't speak in an official capacity, I can't even pretend, but
> > > here is my take on the "apache way".
> >
> > Isn't kind of interesting that there can be more than one "take" on it
> > though?
> >
> > > For an open source project to exist you need code.  All of apache
> > > projects seem to exist to benefit the code... and by extension the
> > > documentation.  Though, even without documentation you still have the
> > > code.  All of the other stuff is extraneous or the life support system
> > > depending on how you look at it.  I think most of the "apache way" is
> > > partially considering it to be extraneous... in a "if the code goes
> sour
> > > and you have nothing" sort of way.  It's definitely symbiotic but
> > > without the code, you have nothing.  You might as well be chatting on
> > > myspace.com.
> >
> > Hehe, considering some of the recent threads around here, posting on
> > myspace.com might actually be safer! :-) LOL
> >
> > > So, the only reason to be a committer is to contribute to the
> > > codebase... and all other committers have to live with each
> other.  The
> > > only reason to be able to cast a binding vote is if you have a stake
> in
> > > the code... ie: are a committer.
> >
> > This is where I'm not sure I agree... why can you only have a stake in
> the
> > code, or in the community even, if you are a committer?  And certainly
> the
> > "community" is often touted as the most important part of any ASF
> > project... it's just that "community" in that context means the
> committers
> > only, which is where I disagree with the Apache Way I guess.
>
>
> No, that's not correct. The community is, as you put it earlier, "anyone
> who
> has an active interest in how the project develops". So you actually agree
> with the Apache Way. ;-)
>
> --
> Martin Cooper
>
>
> Simply putting code out there and sharing your work is great, but going
> > back to a point I made some weeks ago, I beleive there is a
> responsibility
> > that comes along with it when you do that.  Whether they should or not,
> > people become dependent on the project... not in a cocaine kind of way
> of
> > course, but they are "counting on you" basically.  That to me implies
> > taking into consideration their needs and wants.  Not above your own of
> > course, but to some degree.
> >
> > > Bottom line: if a person isn't contributing to code and documentation
> in
> > > a way that the other committers are comfortable with then that person
> > > shouldn't be a committer on the project.  There is no other reason for
> > > being a committer.
> >
> > This I absolutely agree with, and it was the reason my proposal didn't
> try
> > to change that.  I would NEVER propose that the PMC not have the final
> say
> > in who is invited.  It just to me seems right for that to be the case.
> > But, I still see nothing wrong with being able to say "hey, PMC, we
> think
> > this guy or gal would be a good addition, please consider him".
> >
> > > My personal (and probably unneeded) opinion on the original subject:
> > >
> > >  From my perspective, nominations don't matter so much... as I recall
> > > someone could nominate themselves.  If that person hasn't been
> > > contributing code then there is no reason to think they will become a
> > > committer.
> >
> > That is correct.  I frankly was not aware that someone could do that,
> Ted
> > pointed it out to me.  As I replied previously, that indeed covers the
> > first principle of my proposal.  I always prefer things like that be
> more
> > concrete, i.e., rules layed out in document form, but even failing that
> I
> > think the principle is followed, so I'm happy.
> >
> > > It would be nice if the process were a little more transparent as it
> > > would be interesting to know who was proposed, accepted, rejected,
> etc.
> > > even if we didn't know why.  (Though, even counter to that it was nice
> > > to know that someone who contributed to another apache project and
> > > stomped all over my contributed implementation because they didn't
> > > bother to patch to head was at least a controversial nomination.  But
> > > that's sort of personal and isolated reason for wanting to see the
> dirty
> > > laundry.)
> >
> > I still have the concerns about people being embarassed by
> this.  However,
> > I think the idea of a nominee accepting the nomination first is a fair
> > idea.  Putting aside the original proposal, how would that simple
> change,
> > along with opening the vote process discussion for all to see, sit with
> > everyone?
> >
> > > I guess I have trouble seeing how things could be improved much by
> your
> > > proposal... especially since I understood there to be nothing wrong
> with
> > > nominations coming from anywhere.  It was just explained to be easier
> > > with a committer's support.  I don't follow this list too closely, so
> > > maybe I missed someone who has been contributing lots of stuff and
> still
> > > was overlooked.
> >
> > Agreed, once Ted explained that point to me, the proposal isn't quite as
> > strong as I thought at first.  I still think there is the issue of
> > transparency that could do with further discussion, but it seems the
> > nomination part of it is, more or less, already present.  Codifying it
> > would be nice, but I can live with it not being written anywhere.
> >
> > Thanks for commenting, you are always welcome as far as I'm concerned :)
> >
> > > -Paul
> >
> > Frank
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Nathan Bubna <nb...@gmail.com>.
On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> On Tue, April 25, 2006 3:10 pm, Martin Cooper said:
> >> This is where I'm not sure I agree... why can you only have a stake in
> >> the
> >> code, or in the community even, if you are a committer?  And certainly
> >> the
> >> "community" is often touted as the most important part of any ASF
> >> project... it's just that "community" in that context means the
> >> committers
> >> only, which is where I disagree with the Apache Way I guess.
> >
> >
> > No, that's not correct. The community is, as you put it earlier, "anyone
> > who
> > has an active interest in how the project develops". So you actually agree
> > with the Apache Way. ;-)
>
> If your saying that the "community" is not only composed of committers,
> PMC members, etc., then yes, I do agree :)

and of course, i sent me email before reading these because the thread
is moving so fast.

ugh, defining words can be such a pain. :)  for the record, when i use
"community == them that do the work" in my email, i am referring to
those who make the decisions.  this is pretty much the committers and
contributors (note again that contributors != patch submitters).  of
course, there is the broader sense of community that includes those
who have an interest in the development of a project, but in the
Apache Way, their opinions are not binding.  oh, and i realized that
calling them "irrelevant politics" was totally wrong since the
"decision making community" does care about the opinions of the
broader "interested-in-development community" and even the "user
community".   committers and contributors are not at all immune to
ego-stroking and the politics that accompany it.  instead of
"irrelevant politics", i ought to have just said "politics".  ;-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 3:10 pm, Martin Cooper said:
>> This is where I'm not sure I agree... why can you only have a stake in
>> the
>> code, or in the community even, if you are a committer?  And certainly
>> the
>> "community" is often touted as the most important part of any ASF
>> project... it's just that "community" in that context means the
>> committers
>> only, which is where I disagree with the Apache Way I guess.
>
>
> No, that's not correct. The community is, as you put it earlier, "anyone
> who
> has an active interest in how the project develops". So you actually agree
> with the Apache Way. ;-)

If your saying that the "community" is not only composed of committers,
PMC members, etc., then yes, I do agree :)

> --
> Martin Cooper

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Martin Cooper <ma...@apache.org>.
On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
> On Tue, April 25, 2006 2:22 pm, Paul Speed said:
> >
> >
> > Frank W. Zammetti wrote:
> >
> >>
> >> You are of course right about this.  But, much like taking the ideas
> >> about
> >> inventory control and order processing and such from Dell and starting
> >> your own business is possible, the likelihood that you would get
> >> anything
> >> but a small fraction of the attention and business that Dell gets is
> >> slim
> >> to none.
> >
> > Not to sidle in where I don't really belong but perhaps this last
> > sentence exemplifies the disconnect with "getting it"?  If one wanted to
> > take the code from an apache project and do something else with it then
> > all they care about is the something else they want to do.  It isn't
> > really a "business"... the code exists for the code's sake.
>
> You aren't chiming in where you don't belong... if your interested, you
> belong, at least as far as I'm concerned :)
>
> I think there is definitely something to your point, and the analogy may
> have been a bit flawed.  However...
>
> I don't think it is accurate to think that ego doesn't play a part in just
> about everything that just about everyone does.  We all want to see our
> work benefit others.  For most of us I believe its because we genuinely
> like the feeling we get when someone writes us and says "hey, your code
> really helped me, thank you!".  I know speaking for myself, it makes my
> day when I get those eMails!  Part of it is simply the ego stroke of
> someone essentially saying your work is worth something, but I don't
> believe that is the big factor for most people.  I know it isn't for me,
> and I don't think it is for the Struts team.  I think the thank you note
> means as much to them as it does me.
>
> If you agree with that, then the idea of forking the code and doing it
> with the belief that you aren't going to reach a wide audience because the
> Apache version continues to be what people go to, is not appealing.  In
> that regard, if we substitute ego for money in the analogy, I think it
> still works (although just saying ego is dangerous because as I tried to
> illustrate above, I think there is good ego and bad ego).
>
> > I'm not a committer but I've been following this list and the tomcat dev
> > list since the last millennium... I think before there even was a struts
> > 1.0.  I can't speak in an official capacity, I can't even pretend, but
> > here is my take on the "apache way".
>
> Isn't kind of interesting that there can be more than one "take" on it
> though?
>
> > For an open source project to exist you need code.  All of apache
> > projects seem to exist to benefit the code... and by extension the
> > documentation.  Though, even without documentation you still have the
> > code.  All of the other stuff is extraneous or the life support system
> > depending on how you look at it.  I think most of the "apache way" is
> > partially considering it to be extraneous... in a "if the code goes sour
> > and you have nothing" sort of way.  It's definitely symbiotic but
> > without the code, you have nothing.  You might as well be chatting on
> > myspace.com.
>
> Hehe, considering some of the recent threads around here, posting on
> myspace.com might actually be safer! :-) LOL
>
> > So, the only reason to be a committer is to contribute to the
> > codebase... and all other committers have to live with each other.  The
> > only reason to be able to cast a binding vote is if you have a stake in
> > the code... ie: are a committer.
>
> This is where I'm not sure I agree... why can you only have a stake in the
> code, or in the community even, if you are a committer?  And certainly the
> "community" is often touted as the most important part of any ASF
> project... it's just that "community" in that context means the committers
> only, which is where I disagree with the Apache Way I guess.


No, that's not correct. The community is, as you put it earlier, "anyone who
has an active interest in how the project develops". So you actually agree
with the Apache Way. ;-)

--
Martin Cooper


Simply putting code out there and sharing your work is great, but going
> back to a point I made some weeks ago, I beleive there is a responsibility
> that comes along with it when you do that.  Whether they should or not,
> people become dependent on the project... not in a cocaine kind of way of
> course, but they are "counting on you" basically.  That to me implies
> taking into consideration their needs and wants.  Not above your own of
> course, but to some degree.
>
> > Bottom line: if a person isn't contributing to code and documentation in
> > a way that the other committers are comfortable with then that person
> > shouldn't be a committer on the project.  There is no other reason for
> > being a committer.
>
> This I absolutely agree with, and it was the reason my proposal didn't try
> to change that.  I would NEVER propose that the PMC not have the final say
> in who is invited.  It just to me seems right for that to be the case.
> But, I still see nothing wrong with being able to say "hey, PMC, we think
> this guy or gal would be a good addition, please consider him".
>
> > My personal (and probably unneeded) opinion on the original subject:
> >
> >  From my perspective, nominations don't matter so much... as I recall
> > someone could nominate themselves.  If that person hasn't been
> > contributing code then there is no reason to think they will become a
> > committer.
>
> That is correct.  I frankly was not aware that someone could do that, Ted
> pointed it out to me.  As I replied previously, that indeed covers the
> first principle of my proposal.  I always prefer things like that be more
> concrete, i.e., rules layed out in document form, but even failing that I
> think the principle is followed, so I'm happy.
>
> > It would be nice if the process were a little more transparent as it
> > would be interesting to know who was proposed, accepted, rejected, etc.
> > even if we didn't know why.  (Though, even counter to that it was nice
> > to know that someone who contributed to another apache project and
> > stomped all over my contributed implementation because they didn't
> > bother to patch to head was at least a controversial nomination.  But
> > that's sort of personal and isolated reason for wanting to see the dirty
> > laundry.)
>
> I still have the concerns about people being embarassed by this.  However,
> I think the idea of a nominee accepting the nomination first is a fair
> idea.  Putting aside the original proposal, how would that simple change,
> along with opening the vote process discussion for all to see, sit with
> everyone?
>
> > I guess I have trouble seeing how things could be improved much by your
> > proposal... especially since I understood there to be nothing wrong with
> > nominations coming from anywhere.  It was just explained to be easier
> > with a committer's support.  I don't follow this list too closely, so
> > maybe I missed someone who has been contributing lots of stuff and still
> > was overlooked.
>
> Agreed, once Ted explained that point to me, the proposal isn't quite as
> strong as I thought at first.  I still think there is the issue of
> transparency that could do with further discussion, but it seems the
> nomination part of it is, more or less, already present.  Codifying it
> would be nice, but I can live with it not being written anywhere.
>
> Thanks for commenting, you are always welcome as far as I'm concerned :)
>
> > -Paul
>
> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 3:19 pm, Paul Speed said:
> Sure, if just always seems to me that the "I want to be a committer"
> guys that haven't contributed any code are 100% ego.  They just want
> their name on the list.  To them, forking the code is not at all
> appealing since they only want the recognition.

Totally agree.

> And there's the other
> side of the coin, if you have some specific direction you need to take
> the code and are willing to put the work in then a fork is totally
> appropriate and if no one else uses it, well that was only a secondary
> concern anyway.

Also agree.  I think forking when you have a specific need is not a problem.

> I have several open source projects of my own and some small amount of
> "fame" due to that, but at the end of the day I still wrote those
> projects for my own needs... which makes them useful by definition.  The
> fact that others use them is icing on the cake.  (Though it is a warm
> fuzzy feeling when I go to respond to someone's post on the NWN forums
> only to see that several others have already recommended my tools...)

Same here.  All the open-source projects I started were to serve some need
that I had.  JWP has evolved into something that is trying to anticipate
the needs of others and service them, but many, maybe even most, of the
things on our to-do list are things we want to use ourselves.  That
particular part of the Apache Way has never escaped me :)

> I think people who think about having their name on the committers list
> first and "what can I do to help" second will always be frustrated and
> disappointed at an apache project.  Just my gut feeling and experience.

Agreed.

> I think there are different levels of "stake".  There is the "stake in
> the code" that your project depends on it... in an emergency, you can
> fork it.  There is the "stake in the code" that you are notionally and
> legally responsible for what is produced (ie: a committer).  The first
> is a completely single-direction dependency.  If you think about things
> from the code's perspective, it only has a stake in the committers...
> and that's only while things are still broken. ;)

Hehe... kind of scary to anthropomorphize code... SkyNet anyone?!?

>> Simply putting code out there and sharing your work is great, but going
>> back to a point I made some weeks ago, I beleive there is a
>> responsibility
>> that comes along with it when you do that.  Whether they should or not,
>> people become dependent on the project... not in a cocaine kind of way
>> of
>> course, but they are "counting on you" basically.  That to me implies
>> taking into consideration their needs and wants.  Not above your own of
>> course, but to some degree.
>
> Yeah, but see... that's almost a moralistic view.  The code only cares
> that _someone_ is using it.  So as long as it has committers that "eat
> their own dogfood" it is happy.  The committers should feel motivated to
> listen to the community because the community ideas could help them do
> their own jobs better.  But it isn't an obligation at all.  The license
> is liberal, you can fork whenever you want.

It *is* a moralistic view, I agree.  I've just always felt that
approaching things moralisticly yields better results than not, be it with
code or in life.  I already know most don't agree with me, I had the
argument with Ted a few weeks back :)  That's OK though, it's just a
different mindset, no big deal.

>> Thanks for commenting, you are always welcome as far as I'm concerned :)
>
> Sure, I always have an opinion on something. ;)

Hehe, and I don't?!?  You really *haven't* been around here long, have
you?!? LOL

> -Paul

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Paul Speed <ps...@progeeks.com>.

Frank W. Zammetti wrote:
> 
[...]
> I don't think it is accurate to think that ego doesn't play a part in just
> about everything that just about everyone does.  We all want to see our
> work benefit others.  For most of us I believe its because we genuinely
> like the feeling we get when someone writes us and says "hey, your code
> really helped me, thank you!".  I know speaking for myself, it makes my
> day when I get those eMails!  Part of it is simply the ego stroke of
> someone essentially saying your work is worth something, but I don't
> believe that is the big factor for most people.  I know it isn't for me,
> and I don't think it is for the Struts team.  I think the thank you note
> means as much to them as it does me.
> 
> If you agree with that, then the idea of forking the code and doing it
> with the belief that you aren't going to reach a wide audience because the
> Apache version continues to be what people go to, is not appealing.  In
> that regard, if we substitute ego for money in the analogy, I think it
> still works (although just saying ego is dangerous because as I tried to
> illustrate above, I think there is good ego and bad ego).

Sure, if just always seems to me that the "I want to be a committer" 
guys that haven't contributed any code are 100% ego.  They just want 
their name on the list.  To them, forking the code is not at all 
appealing since they only want the recognition.  And there's the other 
side of the coin, if you have some specific direction you need to take 
the code and are willing to put the work in then a fork is totally 
appropriate and if no one else uses it, well that was only a secondary 
concern anyway.

I have several open source projects of my own and some small amount of 
"fame" due to that, but at the end of the day I still wrote those 
projects for my own needs... which makes them useful by definition.  The 
fact that others use them is icing on the cake.  (Though it is a warm 
fuzzy feeling when I go to respond to someone's post on the NWN forums 
only to see that several others have already recommended my tools...)

I think people who think about having their name on the committers list 
first and "what can I do to help" second will always be frustrated and 
disappointed at an apache project.  Just my gut feeling and experience.

> 
>>So, the only reason to be a committer is to contribute to the
>>codebase... and all other committers have to live with each other.  The
>>only reason to be able to cast a binding vote is if you have a stake in
>>the code... ie: are a committer.
> 
> 
> This is where I'm not sure I agree... why can you only have a stake in the

I think there are different levels of "stake".  There is the "stake in 
the code" that your project depends on it... in an emergency, you can 
fork it.  There is the "stake in the code" that you are notionally and 
legally responsible for what is produced (ie: a committer).  The first 
is a completely single-direction dependency.  If you think about things 
from the code's perspective, it only has a stake in the committers... 
and that's only while things are still broken. ;)

> code, or in the community even, if you are a committer?  And certainly the
> "community" is often touted as the most important part of any ASF
> project... it's just that "community" in that context means the committers
> only, which is where I disagree with the Apache Way I guess.

Yeah, I guess I haven't seen it codefied like that.  I always think of 
"committers" as the committers and "community" as everything else that 
grew up around that.

> 
> Simply putting code out there and sharing your work is great, but going
> back to a point I made some weeks ago, I beleive there is a responsibility
> that comes along with it when you do that.  Whether they should or not,
> people become dependent on the project... not in a cocaine kind of way of
> course, but they are "counting on you" basically.  That to me implies
> taking into consideration their needs and wants.  Not above your own of
> course, but to some degree.

Yeah, but see... that's almost a moralistic view.  The code only cares 
that _someone_ is using it.  So as long as it has committers that "eat 
their own dogfood" it is happy.  The committers should feel motivated to 
listen to the community because the community ideas could help them do 
their own jobs better.  But it isn't an obligation at all.  The license 
is liberal, you can fork whenever you want.

For a while, as a rule, the company I work for routinely forked open 
source projects into our own repository to insulate ourselves from 
external changes and to more methodically control what went into it. 
And in several cases, we did a true fork.  Now we're back to baseline 
and happy to be there... but we wouldn't have been successful without 
our local copies.

[...]
> 
> Thanks for commenting, you are always welcome as far as I'm concerned :)

Sure, I always have an opinion on something. ;)
-Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 2:22 pm, Paul Speed said:
>
>
> Frank W. Zammetti wrote:
>
>>
>> You are of course right about this.  But, much like taking the ideas
>> about
>> inventory control and order processing and such from Dell and starting
>> your own business is possible, the likelihood that you would get
>> anything
>> but a small fraction of the attention and business that Dell gets is
>> slim
>> to none.
>
> Not to sidle in where I don't really belong but perhaps this last
> sentence exemplifies the disconnect with "getting it"?  If one wanted to
> take the code from an apache project and do something else with it then
> all they care about is the something else they want to do.  It isn't
> really a "business"... the code exists for the code's sake.

You aren't chiming in where you don't belong... if your interested, you
belong, at least as far as I'm concerned :)

I think there is definitely something to your point, and the analogy may
have been a bit flawed.  However...

I don't think it is accurate to think that ego doesn't play a part in just
about everything that just about everyone does.  We all want to see our
work benefit others.  For most of us I believe its because we genuinely
like the feeling we get when someone writes us and says "hey, your code
really helped me, thank you!".  I know speaking for myself, it makes my
day when I get those eMails!  Part of it is simply the ego stroke of
someone essentially saying your work is worth something, but I don't
believe that is the big factor for most people.  I know it isn't for me,
and I don't think it is for the Struts team.  I think the thank you note
means as much to them as it does me.

If you agree with that, then the idea of forking the code and doing it
with the belief that you aren't going to reach a wide audience because the
Apache version continues to be what people go to, is not appealing.  In
that regard, if we substitute ego for money in the analogy, I think it
still works (although just saying ego is dangerous because as I tried to
illustrate above, I think there is good ego and bad ego).

> I'm not a committer but I've been following this list and the tomcat dev
> list since the last millennium... I think before there even was a struts
> 1.0.  I can't speak in an official capacity, I can't even pretend, but
> here is my take on the "apache way".

Isn't kind of interesting that there can be more than one "take" on it
though?

> For an open source project to exist you need code.  All of apache
> projects seem to exist to benefit the code... and by extension the
> documentation.  Though, even without documentation you still have the
> code.  All of the other stuff is extraneous or the life support system
> depending on how you look at it.  I think most of the "apache way" is
> partially considering it to be extraneous... in a "if the code goes sour
> and you have nothing" sort of way.  It's definitely symbiotic but
> without the code, you have nothing.  You might as well be chatting on
> myspace.com.

Hehe, considering some of the recent threads around here, posting on
myspace.com might actually be safer! :-) LOL

> So, the only reason to be a committer is to contribute to the
> codebase... and all other committers have to live with each other.  The
> only reason to be able to cast a binding vote is if you have a stake in
> the code... ie: are a committer.

This is where I'm not sure I agree... why can you only have a stake in the
code, or in the community even, if you are a committer?  And certainly the
"community" is often touted as the most important part of any ASF
project... it's just that "community" in that context means the committers
only, which is where I disagree with the Apache Way I guess.

Simply putting code out there and sharing your work is great, but going
back to a point I made some weeks ago, I beleive there is a responsibility
that comes along with it when you do that.  Whether they should or not,
people become dependent on the project... not in a cocaine kind of way of
course, but they are "counting on you" basically.  That to me implies
taking into consideration their needs and wants.  Not above your own of
course, but to some degree.

> Bottom line: if a person isn't contributing to code and documentation in
> a way that the other committers are comfortable with then that person
> shouldn't be a committer on the project.  There is no other reason for
> being a committer.

This I absolutely agree with, and it was the reason my proposal didn't try
to change that.  I would NEVER propose that the PMC not have the final say
in who is invited.  It just to me seems right for that to be the case. 
But, I still see nothing wrong with being able to say "hey, PMC, we think
this guy or gal would be a good addition, please consider him".

> My personal (and probably unneeded) opinion on the original subject:
>
>  From my perspective, nominations don't matter so much... as I recall
> someone could nominate themselves.  If that person hasn't been
> contributing code then there is no reason to think they will become a
> committer.

That is correct.  I frankly was not aware that someone could do that, Ted
pointed it out to me.  As I replied previously, that indeed covers the
first principle of my proposal.  I always prefer things like that be more
concrete, i.e., rules layed out in document form, but even failing that I
think the principle is followed, so I'm happy.

> It would be nice if the process were a little more transparent as it
> would be interesting to know who was proposed, accepted, rejected, etc.
> even if we didn't know why.  (Though, even counter to that it was nice
> to know that someone who contributed to another apache project and
> stomped all over my contributed implementation because they didn't
> bother to patch to head was at least a controversial nomination.  But
> that's sort of personal and isolated reason for wanting to see the dirty
> laundry.)

I still have the concerns about people being embarassed by this.  However,
I think the idea of a nominee accepting the nomination first is a fair
idea.  Putting aside the original proposal, how would that simple change,
along with opening the vote process discussion for all to see, sit with
everyone?

> I guess I have trouble seeing how things could be improved much by your
> proposal... especially since I understood there to be nothing wrong with
> nominations coming from anywhere.  It was just explained to be easier
> with a committer's support.  I don't follow this list too closely, so
> maybe I missed someone who has been contributing lots of stuff and still
> was overlooked.

Agreed, once Ted explained that point to me, the proposal isn't quite as
strong as I thought at first.  I still think there is the issue of
transparency that could do with further discussion, but it seems the
nomination part of it is, more or less, already present.  Codifying it
would be nice, but I can live with it not being written anywhere.

Thanks for commenting, you are always welcome as far as I'm concerned :)

> -Paul

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Paul Speed <ps...@progeeks.com>.

Frank W. Zammetti wrote:

> 
> You are of course right about this.  But, much like taking the ideas about
> inventory control and order processing and such from Dell and starting
> your own business is possible, the likelihood that you would get anything
> but a small fraction of the attention and business that Dell gets is slim
> to none.

Not to sidle in where I don't really belong but perhaps this last 
sentence exemplifies the disconnect with "getting it"?  If one wanted to 
take the code from an apache project and do something else with it then 
all they care about is the something else they want to do.  It isn't 
really a "business"... the code exists for the code's sake.

I'm not a committer but I've been following this list and the tomcat dev 
list since the last millennium... I think before there even was a struts 
1.0.  I can't speak in an official capacity, I can't even pretend, but 
here is my take on the "apache way".

For an open source project to exist you need code.  All of apache 
projects seem to exist to benefit the code... and by extension the 
documentation.  Though, even without documentation you still have the 
code.  All of the other stuff is extraneous or the life support system 
depending on how you look at it.  I think most of the "apache way" is 
partially considering it to be extraneous... in a "if the code goes sour 
and you have nothing" sort of way.  It's definitely symbiotic but 
without the code, you have nothing.  You might as well be chatting on 
myspace.com.

So, the only reason to be a committer is to contribute to the 
codebase... and all other committers have to live with each other.  The 
only reason to be able to cast a binding vote is if you have a stake in 
the code... ie: are a committer.

Which doesn't mean that other votes don't count... that's up to how the 
committers want to appeal to the community.  But ultimately, they have 
to live with what the decide so it makes sense that they have the final 
word.

Bottom line: if a person isn't contributing to code and documentation in 
a way that the other committers are comfortable with then that person 
shouldn't be a committer on the project.  There is no other reason for 
being a committer.

My personal (and probably unneeded) opinion on the original subject:

 From my perspective, nominations don't matter so much... as I recall 
someone could nominate themselves.  If that person hasn't been 
contributing code then there is no reason to think they will become a 
committer.

It would be nice if the process were a little more transparent as it 
would be interesting to know who was proposed, accepted, rejected, etc. 
even if we didn't know why.  (Though, even counter to that it was nice 
to know that someone who contributed to another apache project and 
stomped all over my contributed implementation because they didn't 
bother to patch to head was at least a controversial nomination.  But 
that's sort of personal and isolated reason for wanting to see the dirty 
laundry.)

I guess I have trouble seeing how things could be improved much by your 
proposal... especially since I understood there to be nothing wrong with 
nominations coming from anywhere.  It was just explained to be easier 
with a committer's support.  I don't follow this list too closely, so 
maybe I missed someone who has been contributing lots of stuff and still 
was overlooked.

-Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 12:36 am, Craig McClanahan said:
> Without commenting on the merit of the proposal itself, or the reasoning
> presented as its justification, it is important to note that we (the
> Struts
> community) do not have free reign to do whatever we want in this regard.
> As
> part of Apache, the Struts community is accountable to the Apache Software
> Foundation's Board of Directors, and one of the things that gets watched
> is
> how well the various projects implement "the Apache Way".  And one of the
> key tenets of that "way" is how new committers get selected.

I understand that... does that mean that a particular project is not
allowed to try something new?  If there are rules in place to keep
projects from donig so, then I wasn't aware of that, and certainly that
puts a damper on this proposal :)

> Regardless of the details, anything along the general lines of what you
> describe would be quite different from the way Apache has grown from the
> very beginning to what it is today -- and it would, therefore, be looked
> at
> with a *lot* of skepticism by Apache as a whole.

I would *hope* it would be looked upon with skepticism :)  I'm certainly
in no way saying the Apache Way hasn't worked all this time, of course it
has! :)

But, is skepticism enough to dissuage an attempt at something?  Assuming
there are no rules in place to stop a project from trying it I mean.

> Trying to argue that the
> Apache Way is flawed, and needs to be fundamentally changed like this,
> does
> not seem likely (to me) to get much agreement Apache wide, given the ASF's
> history, and the success of many of its projects at building communities
> of
> committers that buy in to that culture -- and, by the way, produce some
> pretty popular software to boot.

No argument.  But again, I'm not talking about changing anything
Apache-wide.  I'm talking about trying something in one project where
there *seems* to be a perception that things could be somewhat improved,
and seeing how it works.

> So what the heck is this "Apache way" thing?  It is a culture; a way of
> gathering a community that interoperates ... and it can be tough at times
> to
> write down a descrption that makes sense.  But [1] is a pretty good
> starting
> point.  I'd also recommend looking through the documentation for the
> Incubator Project (where a specific exit criteria is that the folks
> participating in the new project "get it" about the Apache way).
>
> Frank
>
>
> Craig
>
> [1] http://www.apache.org/foundation/how-it-works.html

I've read this page before, and just did so again.  While I think it is
fantastic at describing what Apache is and how it works, I don't see
anything that would help me or anyone else understand how to "get it". 
Aside from the discussion on meritocracy, nothing seems to discuss that. 
The Philosophy section seems to discuss the philosophy of a project, the
the philosophy of how someone needs to conduct themselves to "get it".  I
would very much like to understand how this determination is made.

> PS:  If you like the code but don't like the community, one of the best
> things about Apache is that the license gives you the right to fork and
> build your own community, operated according to whatever rules please you.
> So, even if a proposal like this is not accepted, you still have the
> opportunity to go build "a better Struts" -- that doesn't have to be done
> here.

You are of course right about this.  But, much like taking the ideas about
inventory control and order processing and such from Dell and starting
your own business is possible, the likelihood that you would get anything
but a small fraction of the attention and business that Dell gets is slim
to none.

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 12:36 am, Craig McClanahan said:
> Without commenting on the merit of the proposal itself, or the reasoning
> presented as its justification, it is important to note that we (the
> Struts
> community) do not have free reign to do whatever we want in this regard.
> As
> part of Apache, the Struts community is accountable to the Apache Software
> Foundation's Board of Directors, and one of the things that gets watched
> is
> how well the various projects implement "the Apache Way".  And one of the
> key tenets of that "way" is how new committers get selected.

I understand that... does that mean that a particular project is not
allowed to try something new?  If there are rules in place to keep
projects from donig so, then I wasn't aware of that, and certainly that
puts a damper on this proposal :)

> Regardless of the details, anything along the general lines of what you
> describe would be quite different from the way Apache has grown from the
> very beginning to what it is today -- and it would, therefore, be looked
> at
> with a *lot* of skepticism by Apache as a whole.

I would *hope* it would be looked upon with skepticism :)  I'm certainly
in no way saying the Apache Way hasn't worked all this time, of course it
has! :)

But, is skepticism enough to dissuage an attempt at something?  Assuming
there are no rules in place to stop a project from trying it I mean.

> Trying to argue that the
> Apache Way is flawed, and needs to be fundamentally changed like this,
> does
> not seem likely (to me) to get much agreement Apache wide, given the ASF's
> history, and the success of many of its projects at building communities
> of
> committers that buy in to that culture -- and, by the way, produce some
> pretty popular software to boot.

No argument.  But again, I'm not talking about changing anything
Apache-wide.  I'm talking about trying something in one project where
there *seems* to be a perception that things could be somewhat improved,
and seeing how it works.

> So what the heck is this "Apache way" thing?  It is a culture; a way of
> gathering a community that interoperates ... and it can be tough at times
> to
> write down a descrption that makes sense.  But [1] is a pretty good
> starting
> point.  I'd also recommend looking through the documentation for the
> Incubator Project (where a specific exit criteria is that the folks
> participating in the new project "get it" about the Apache way).
>
> Frank
>
>
> Craig
>
> [1] http://www.apache.org/foundation/how-it-works.html

I've read this page before, and just did so again.  While I think it is
fantastic at describing what Apache is and how it works, I don't see
anything that would help me or anyone else understand how to "get it". 
Aside from the discussion on meritocracy, nothing seems to discuss that. 
The Philosophy section seems to discuss the philosophy of a project, the
the philosophy of how someone needs to conduct themselves to "get it".  I
would very much like to understand how this determination is made.

> PS:  If you like the code but don't like the community, one of the best
> things about Apache is that the license gives you the right to fork and
> build your own community, operated according to whatever rules please you.
> So, even if a proposal like this is not accepted, you still have the
> opportunity to go build "a better Struts" -- that doesn't have to be done
> here.

You are of course right about this.  But, much like taking the ideas about
inventory control and order processing and such from Dell and starting
your own business is possible, the likelihood that you would get anything
but a small fraction of the attention and business that Dell gets is slim
to none.

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org


Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
>
> I look forward to feedback.  Thanks for listening!


Without commenting on the merit of the proposal itself, or the reasoning
presented as its justification, it is important to note that we (the Struts
community) do not have free reign to do whatever we want in this regard.  As
part of Apache, the Struts community is accountable to the Apache Software
Foundation's Board of Directors, and one of the things that gets watched is
how well the various projects implement "the Apache Way".  And one of the
key tenets of that "way" is how new committers get selected.

Regardless of the details, anything along the general lines of what you
describe would be quite different from the way Apache has grown from the
very beginning to what it is today -- and it would, therefore, be looked at
with a *lot* of skepticism by Apache as a whole.  Trying to argue that the
Apache Way is flawed, and needs to be fundamentally changed like this, does
not seem likely (to me) to get much agreement Apache wide, given the ASF's
history, and the success of many of its projects at building communities of
committers that buy in to that culture -- and, by the way, produce some
pretty popular software to boot.

So what the heck is this "Apache way" thing?  It is a culture; a way of
gathering a community that interoperates ... and it can be tough at times to
write down a descrption that makes sense.  But [1] is a pretty good starting
point.  I'd also recommend looking through the documentation for the
Incubator Project (where a specific exit criteria is that the folks
participating in the new project "get it" about the Apache way).

Frank


Craig

[1] http://www.apache.org/foundation/how-it-works.html

PS:  If you like the code but don't like the community, one of the best
things about Apache is that the license gives you the right to fork and
build your own community, operated according to whatever rules please you.
So, even if a proposal like this is not accepted, you still have the
opportunity to go build "a better Struts" -- that doesn't have to be done
here.

Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
> * Rationale
> One of the issues that a number of people seem to have with the way
> Struts has progressed is the seeming inability (or difficulty at least)
> of getting "new blood" involved.  There seems to be a perception by many
> that there is a bit of a "closed club" mentality with regard to being
> invited in as a committer and that the Struts community at large has no
> say in the matter.


The latter statement is, as mentioned in my previous response, the way that
*all* projects at Apache work -- it is not unique to Struts.  Any claim that
all of Apache is broken in this regard is going to be, umm, unlikely to be
agreed with :-).  What's more interesting is to examine the former
statement, and compare it to the facts.

The "Who We Are" page[1] lists the current folks who are on the PMC (and
also have committer privileges), and who are committers not on the PMC.
There's 14 and 13 names, respectively, giving a total of 27 (and this
doesn't count the 10 previous committers who are now on the emeritus list,
for a total of 37).  That's a pretty good size number, compared to the
average at Apache.  But what is really interesting is to look at the timing
of how we got from one committer (me) six years ago, to where we are today
-- and focus especially on the more recent changes.

In just the last year there have been quite a number of new committers
added[2] ... six independent of the WebWork merger (Wendy, Gary, Greg,
Shawn, Laurie, and Richard), two more (Jason and Patrick) directly because
of the merger, and five more who have commit rights to the WebWork incubator
code and will become Struts committers as soon as it graduates.  There is
also one outstanding invitation that, for personal reasons fo the individual
involved, will be accepted later rather than now.  That is a pretty large
percentage increase for a single year, even discounting the merger -- and
have you ever seen other "competing" communities come together like this?
Hmm ... doesn't seem like the existing community is particularly "closed" to
new blood to me.

Examining how the new folks got themselves nominated and elected is also
interesting.  In every case, it was based on continuous contributions of
code, documentation, user list help, build script maintenance, or whatever
made a *positive* difference for everyone.  Indeed, if you go back to the
days when folks like Ted and Martin were added, a lot of it was being tired
of applying all the patches they were contributing :-).  All of these folks
"get it" -- so it is not just a couple of dictatorial snobs sitting on top
of the mountain dictating who is in and who is out :-).

There is also another interesting observation here -- you don't have to be a
committer to initiate changes to the Struts code base.  What you have to do
is justify your bugfix or RFE to the point where an existing committer is
willing to take responsibility for cleaning up any messes that committing
the change might cause.  So, you only have to convince one of the various
folks to get your patch in.  Failure to succeed in that goal *could* be a
close minded community, but it also just might be that the proposed change
doesn't fit with what the committers as a whole have in mind (it only takes
one commiter -1 to make a committed change get reversed, so we pay attention
to this as part of the decision process on accepting a patch).  Just in the
little time I have had to spend on Struts in the last year, I've committed
patches from at least 20 different people.  Spread across the six years that
Struts has existed, and all the committers who have done the same thing, we
are talking many *hundreds* of people who have contributed at least some
code or documentation to what is now Struts.

I just don't buy the presumption that the current system is broken.  I won't
presume to convince *you* to think that way -- it's your perogative to think
whatever you want -- but I will certainly take into account whether someone
"gets it" before I would ever vote for them to be a committer.

Fortunately for those who either don't, or don't want to, buy into this, the
Apache license gives you the freedom to take the code and go start your own
community, operating according to your own rules, if you don't like the way
things work here.  But you are starting from a rationale that does not match
the objective facts, so I'm not even going to be interested in trying to
hash out details of how to change something that does not need to be
changed.

Craig

[1] http://struts.apache.org/volunteers.html
[2] http://struts.apache.org/announce.html

Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
>
> I look forward to feedback.  Thanks for listening!


Without commenting on the merit of the proposal itself, or the reasoning
presented as its justification, it is important to note that we (the Struts
community) do not have free reign to do whatever we want in this regard.  As
part of Apache, the Struts community is accountable to the Apache Software
Foundation's Board of Directors, and one of the things that gets watched is
how well the various projects implement "the Apache Way".  And one of the
key tenets of that "way" is how new committers get selected.

Regardless of the details, anything along the general lines of what you
describe would be quite different from the way Apache has grown from the
very beginning to what it is today -- and it would, therefore, be looked at
with a *lot* of skepticism by Apache as a whole.  Trying to argue that the
Apache Way is flawed, and needs to be fundamentally changed like this, does
not seem likely (to me) to get much agreement Apache wide, given the ASF's
history, and the success of many of its projects at building communities of
committers that buy in to that culture -- and, by the way, produce some
pretty popular software to boot.

So what the heck is this "Apache way" thing?  It is a culture; a way of
gathering a community that interoperates ... and it can be tough at times to
write down a descrption that makes sense.  But [1] is a pretty good starting
point.  I'd also recommend looking through the documentation for the
Incubator Project (where a specific exit criteria is that the folks
participating in the new project "get it" about the Apache way).

Frank


Craig

[1] http://www.apache.org/foundation/how-it-works.html

PS:  If you like the code but don't like the community, one of the best
things about Apache is that the license gives you the right to fork and
build your own community, operated according to whatever rules please you.
So, even if a proposal like this is not accepted, you still have the
opportunity to go build "a better Struts" -- that doesn't have to be done
here.

Re: Proposal for change

Posted by Nathan Bubna <nb...@gmail.com>.
On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> On Tue, April 25, 2006 3:42 pm, Nathan Bubna said:
> >> Question: does submitting a patch have to mean having the patch
> >> accepted?
> >> At first glance, the obvious answer is yes, but I'm not so sure it's
> >> really the obvious answer... if someone has submitted a number of
> >> patches
> >> that were not committed for reasons other than purely technical (i.e.,
> >> the
> >> patch will break X), should those patches be considered?
> > <snip/>
> >
> > forgive me for being blunt, but this is nonsense.  who wants a
> > committer whose work breaks X?  those patches aren't part of the
> > "work" of the project.  that's a bummer for the submitter, but this is
> > not about effort or desire or concern or anything other form of
> > interest in a project.  it's about merit.  if you don't have it, then
> > you are s.o.l.   Oh, and if you do have it but insist on changing this
> > to be more about "interest" than "merit" (i.e. you don't "get it"),
> > then you should not be the least surprised when you find a lot of
> > resistance. :)
>
> I think you may have misunderstood... someone who's code breaks X SHOULD
> NOT be considered.  I didn't say otherwise :)  As for interest vs. merit,
> I don't at all disagree... merit is what counts.  My only point would be
> that what constitutes "merit" may not be, or maybe should not be, as
> simple as "how many accepted patches has this person put forward".  Ted
> hinted at that with his commented about the Wiki being considered.  I
> agree that code trumps all else, as it should be, but should that be the
> *only* consideration?

no, not just code; documentation is great too!  and personally, the
only parts of wiki contributions that ought to be considered are those
that become part of the official release/distribution.  those are the
wiki-submitted patches that have been accepted.

> Well, in any case, you raise a good point about the proposal maybe being
> more of a paradigm shift than I thought.  I may have miscalculated that.
> You also raise some other fair points above I think about being a
> fundamental change in what community is.
>
> I sincerely thank everyone that commented, I appreciate you taking the
> time out of your busy schedules to at least consider the proposal.  I
> won't push it any further, being heard and considered is all I could have
> expected.

thanks for stirring the pot!  it's a healthy thing. :)

> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 3:42 pm, Nathan Bubna said:
>> Question: does submitting a patch have to mean having the patch
>> accepted?
>> At first glance, the obvious answer is yes, but I'm not so sure it's
>> really the obvious answer... if someone has submitted a number of
>> patches
>> that were not committed for reasons other than purely technical (i.e.,
>> the
>> patch will break X), should those patches be considered?
> <snip/>
>
> forgive me for being blunt, but this is nonsense.  who wants a
> committer whose work breaks X?  those patches aren't part of the
> "work" of the project.  that's a bummer for the submitter, but this is
> not about effort or desire or concern or anything other form of
> interest in a project.  it's about merit.  if you don't have it, then
> you are s.o.l.   Oh, and if you do have it but insist on changing this
> to be more about "interest" than "merit" (i.e. you don't "get it"),
> then you should not be the least surprised when you find a lot of
> resistance. :)

I think you may have misunderstood... someone who's code breaks X SHOULD
NOT be considered.  I didn't say otherwise :)  As for interest vs. merit,
I don't at all disagree... merit is what counts.  My only point would be
that what constitutes "merit" may not be, or maybe should not be, as
simple as "how many accepted patches has this person put forward".  Ted
hinted at that with his commented about the Wiki being considered.  I
agree that code trumps all else, as it should be, but should that be the
*only* consideration?

Well, in any case, you raise a good point about the proposal maybe being
more of a paradigm shift than I thought.  I may have miscalculated that. 
You also raise some other fair points above I think about being a
fundamental change in what community is.

I sincerely thank everyone that commented, I appreciate you taking the
time out of your busy schedules to at least consider the proposal.  I
won't push it any further, being heard and considered is all I could have
expected.

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Nathan Bubna <nb...@gmail.com>.
On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> On Tue, April 25, 2006 6:45 am, Ted Husted said:
<snip/>
> > From an ASF perspective, the "community" is not everyone who
> > subscribes to the mailing list and downloads the product. The
> > community is the set of individuals who contribute to the project,
> > both by making helpful posts to the mailing list *and* by contributing
> > useful code and documentation. Downloads don't make the product
> > possible. Contributions make the product possible. Our customers are
> > the contributors, who pay for the product with posts and patches.
>
> I guess this is one way that I've never quite "got it", as Craig says :)
> I view the community as being larger than just those contributing.  While
> I have no problem affording something "more" to those that contribute, I
> think those simply using the product have a stake in it.  They can of
> course choose to ignore that stake, but they can exercise interest if they
> wish.
>
> For me, the community would be "anyone who has an active interest in how
> the project develops".  Those that contribute in some way deserve a louder
> voice and a bigger say in things, but I don't think contributing is the
> only criteria for being in the community.
>
> But that is my interpretation, I realize it doesn't jive with the ASF
> interpretation :)

it feels like this is really the lynchpin of all this.  your
understanding of the "Struts community" is not the ASF's.  your
understanding of what the "community" is appears to be the driving
principle behind your proposal.  so this proposal contains an implicit
subtraction of the current definition of "community" to replace it
with a broader one.  like it or not, when you widen the scope, you are
subtracting an intentional limitation set by the ASF.

i know, it seems like a fairly simple and nice proposal to make it the
standard practice to let all interested parties weigh in on committer
nominations, but as you are probably discovering by the responses,
there is a significant ideological shift involved.  community is
critical to the ASF; changing that from "them that do the work" to
"all who are interested in the work" is no small thing.

committer status is fundamentally two things: a formal recognition
that the person is among "them that do the work" (which should already
be obvious) and a labor saving device (so the other committers don't
have to deal with the person's patches).   so as i see it, nominations
and votes ought to be a largely superfluous formality, and the opinion
of those "interested in shaping the development of the project" but
not among "them that do the work" is irrelevant politics (the
unfortunately common penalty for popular projects like Struts).

> > Over the years, I think there have been exactly two committer
> > nominations here that failed, and both times the failed nominees had
> > not submitted a single patch.

i.e.  it was not at all obvious that those two were among "them that
do the work".

> Question: does submitting a patch have to mean having the patch accepted?
> At first glance, the obvious answer is yes, but I'm not so sure it's
> really the obvious answer... if someone has submitted a number of patches
> that were not committed for reasons other than purely technical (i.e., the
> patch will break X), should those patches be considered?
<snip/>

forgive me for being blunt, but this is nonsense.  who wants a
committer whose work breaks X?  those patches aren't part of the
"work" of the project.  that's a bummer for the submitter, but this is
not about effort or desire or concern or anything other form of
interest in a project.  it's about merit.  if you don't have it, then
you are s.o.l.   Oh, and if you do have it but insist on changing this
to be more about "interest" than "merit" (i.e. you don't "get it"),
then you should not be the least surprised when you find a lot of
resistance. :)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 2:41 pm, Martin Cooper said:
>> For me, the community would be "anyone who has an active interest in how
>> the project develops".
>
>
> There! You've said it. That exactly describes the purpose of the dev@
> list.
> So, now, why again do we need the three lists you mention above? ;-)

Ok, fair enough, I'll concede the point :)

(Since suggesting three lists was *maybe* only 5% serious anyway, it's not
such a big concession!)

This whole discussion seems to have moved to the dev@ list anyway, which
is fine by me, given the above.

> --
> Martin Cooper

Frank


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Don Brown <mr...@twdata.org>.
Ted Husted wrote:
> On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
>> There! You've said it. That exactly describes the purpose of the dev@ list.
>> So, now, why again do we need the three lists you mention above? ;-)
> 
> Actually, there are three public lists.
> 
> * user@ for helping people use the product
> * dev@ for discussing changes to the product
> * commit@ for logging changes to the product
> 
> Right now, we have the issue trackers and wiki posting to dev@, but I
> sometimes wonder if it would be "cleaner" to have all the automatic
> posts going to commit@, especially if we are going to be hooking
> forums up to the lists.

+1

> 
> -Ted.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by netsql <ne...@roomity.com>.
And I have a theory: Code emails scare trolls.

It may actually increase the noise to signal
.V

Craig McClanahan wrote:
> 
> I've historically been a holdout on this issue (based on the philosophy that
> anyone who is interested in the development of a project should be watching
> the commit messages too,


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Dakota Jack <da...@gmail.com>.
If you thought waiting like you were asked would help at all, Patrick, you
are probably about to learn your first lesson in
Struts-Shale-JSF-Craig-Apache Way.

On 4/25/06, Craig McClanahan <cr...@apache.org> wrote:
>
> On 4/25/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> >
> > Any chance that as you discuss this there would be a move to make dev@
> not
> > receive all commit@ messages? Some of us (me) prefer to use RSS and
> forcing
> > the emails seems a bit heavy handed.
>
>
> I've historically been a holdout on this issue (based on the philosophy
> that
> anyone who is interested in the development of a project should be
> watching
> the commit messages too, and having separate lists for commit messages
> makes
> it too easy to ignore those), but I'd be ok with separate lists if the
> majority of the commiters want it that way.
>
> Craig
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/25/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
>
> Any chance that as you discuss this there would be a move to make dev@ not
> receive all commit@ messages? Some of us (me) prefer to use RSS and forcing
> the emails seems a bit heavy handed.


I've historically been a holdout on this issue (based on the philosophy that
anyone who is interested in the development of a project should be watching
the commit messages too, and having separate lists for commit messages makes
it too easy to ignore those), but I'd be ok with separate lists if the
majority of the commiters want it that way.

Craig

Re: Proposal for change

Posted by Wendy Smoak <ws...@gmail.com>.
On 4/25/06, Patrick Lightbody <fo...@opensymphony.com> wrote:

> Any chance that as you discuss this there would be a move to make dev@ not receive all commit@ messages? Some of us (me) prefer to use RSS and forcing the emails seems a bit heavy handed.

I remember this request from the last time this came up, and it's part
of the proposal (in a separate thread, since the subject of this one
has now shifted.)

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Ted Husted <te...@gmail.com>.
On 4/25/06, Craig McClanahan <cr...@apache.org> wrote:
> FWIW, this (four lists) is what the ADF Faces incubator podling chose
> (dev,user,issues,commits).  There's actually yet one more category of
> automated messages (wiki changes), but I suspect the volume of those is low
> enough not to bother anyone.

I'd suggest that the wiki changes look and feel like commit logs, and
that these would be a good fit for commit@.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Patrick Lightbody <fo...@opensymphony.com>.
Any chance that as you discuss this there would be a move to make dev@ not receive all commit@ messages? Some of us (me) prefer to use RSS and forcing the emails seems a bit heavy handed.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=27416&messageID=54179#54179


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Craig McClanahan <cr...@apache.org>.
On 4/25/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 4/25/06, Ted Husted <te...@gmail.com> wrote:
>
> > Actually, there are three public lists.
> >
> > * user@ for helping people use the product
> > * dev@ for discussing changes to the product
> > * commit@ for logging changes to the product
> >
> > Right now, we have the issue trackers and wiki posting to dev@, but I
> > sometimes wonder if it would be "cleaner" to have all the automatic
> > posts going to commit@, especially if we are going to be hooking
> > forums up to the lists.
>
> I was wishing for that today as I set up filters to get all the JIRA
> messages out of my struts-dev label.  IIRC this has been suggested
> before. :)
>
> What about issues@ rather than directing them to commits@ (which they
> really aren't)?


FWIW, this (four lists) is what the ADF Faces incubator podling chose
(dev,user,issues,commits).  There's actually yet one more category of
automated messages (wiki changes), but I suspect the volume of those is low
enough not to bother anyone.


--
> Wendy


Craig

Re: Proposal for change

Posted by Wendy Smoak <ws...@gmail.com>.
On 4/25/06, Ted Husted <te...@gmail.com> wrote:

> Actually, there are three public lists.
>
> * user@ for helping people use the product
> * dev@ for discussing changes to the product
> * commit@ for logging changes to the product
>
> Right now, we have the issue trackers and wiki posting to dev@, but I
> sometimes wonder if it would be "cleaner" to have all the automatic
> posts going to commit@, especially if we are going to be hooking
> forums up to the lists.

I was wishing for that today as I set up filters to get all the JIRA
messages out of my struts-dev label.  IIRC this has been suggested
before. :)

What about issues@ rather than directing them to commits@ (which they
really aren't)?

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Ted Husted <te...@gmail.com>.
On 4/25/06, Martin Cooper <ma...@apache.org> wrote:
> There! You've said it. That exactly describes the purpose of the dev@ list.
> So, now, why again do we need the three lists you mention above? ;-)

Actually, there are three public lists.

* user@ for helping people use the product
* dev@ for discussing changes to the product
* commit@ for logging changes to the product

Right now, we have the issue trackers and wiki posting to dev@, but I
sometimes wonder if it would be "cleaner" to have all the automatic
posts going to commit@, especially if we are going to be hooking
forums up to the lists.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Martin Cooper <ma...@apache.org>.
On 4/25/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
>
> Yes, I considered doing that... but as my proposal was specifically *for*
> the community, I felt it important to put the most number of eyeballs on
> it as possible.
>
> You know, perhaps we need *three* mailing lists... one for devs, one for
> users who just want questions answered, and one for the "community", those
> that want to be involved in shaping things but that aren't committers. :)


[...]


> I guess this is one way that I've never quite "got it", as Craig says :)
> I view the community as being larger than just those contributing.  While
> I have no problem affording something "more" to those that contribute, I
> think those simply using the product have a stake in it.  They can of
> course choose to ignore that stake, but they can exercise interest if they
> wish.
>
> For me, the community would be "anyone who has an active interest in how
> the project develops".


There! You've said it. That exactly describes the purpose of the dev@ list.
So, now, why again do we need the three lists you mention above? ;-)

--
Martin Cooper

Re: Proposal for change

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
On Tue, April 25, 2006 6:45 am, Ted Husted said:
> I should mention that proposals for change are best sent to dev@. This
> list is meant for people who want help using a product. Changes to the
> project are best discussed on dev@. We should get back on task as to
> the role of each list, and :) stop annoying people who just want to
> know how to use the taglibs :)

Yes, I considered doing that... but as my proposal was specifically *for*
the community, I felt it important to put the most number of eyeballs on
it as possible.

You know, perhaps we need *three* mailing lists... one for devs, one for
users who just want questions answered, and one for the "community", those
that want to be involved in shaping things but that aren't committers. :)

> Back at Jakarta, we used to have committer votes on public lists, and
> I saw a lot of those go very wrong. People would use them as an excuse
> to talk about something else. It's hard to have a candid discussion
> about a *person* on a public list. As it turns out, the Apache HTTPD
> team has never had discussions about people on a public list. I think
> that is a  much better way to go. We announce the tallies for the
> committer votes that succeed, but we don't embarrass people by
> announcing votes and discussions that fail.

I certainly see the point your making, I happen to agree with it.  Perhaps
it should work more like a senate confirmation hearing in the sense that
before you begin to discuss someone you ask them if they want to be
considered, and then have the discussions in public? (I think Niall more
or less suggests the same thing in this thread).  If a person accepts a
nomination, they then accept the public debate, and any embarassment that
might result.  Just a thought.

> If you want to "force" a vote by the PMC, why not just bring one up on
> dev@? But, please, check with the nominee first, to be sure he or she
> wishes to be discussed on a public list in this way.

I didn't frankly know that was an option... has that ever happened before?
 If there is some unofficial policy in this regard, I'd be happy to know
about it... as long as there is some unwritten rule that the PMC will vote
on a nominee made by someone not on the PMC, then the underlying spirit of
my proposal is already in place... I think it's always better to codify
these kinds of things, but I can live with an unwritten rule :)  I'd like
to know that it has been exercised in the past though.

> From an ASF perspective, the "community" is not everyone who
> subscribes to the mailing list and downloads the product. The
> community is the set of individuals who contribute to the project,
> both by making helpful posts to the mailing list *and* by contributing
> useful code and documentation. Downloads don't make the product
> possible. Contributions make the product possible. Our customers are
> the contributors, who pay for the product with posts and patches.

I guess this is one way that I've never quite "got it", as Craig says :) 
I view the community as being larger than just those contributing.  While
I have no problem affording something "more" to those that contribute, I
think those simply using the product have a stake in it.  They can of
course choose to ignore that stake, but they can exercise interest if they
wish.

For me, the community would be "anyone who has an active interest in how
the project develops".  Those that contribute in some way deserve a louder
voice and a bigger say in things, but I don't think contributing is the
only criteria for being in the community.

But that is my interpretation, I realize it doesn't jive with the ASF
interpretation :)

> Over the years, I think there have been exactly two committer
> nominations here that failed, and both times the failed nominees had
> not submitted a single patch.

Question: does submitting a patch have to mean having the patch accepted? 
At first glance, the obvious answer is yes, but I'm not so sure it's
really the obvious answer... if someone has submitted a number of patches
that were not committed for reasons other than purely technical (i.e., the
patch will break X), should those patches be considered?

>> But, at the end of the
>> day, who is invited to join is still decided by the PMC, as it is today.
>
> :) Well, yeah. We're the ones that have to live with the decision,
> long after whoever "voted" on the nomiantion might have unsubscribed
> and faded away. :)

Yep :)

> Who I would feel sorry for is all the people who might be nominated,
> and then turned down, on a public list, without ever even asking to be
> nominated or discussed in a public forum. This isn't about making
> legislation or winning a popularity contest. We need people who *can
> and do* create code or documentation and *collaborate* with other team
> members, without a suit or "lead developer" pulling the strings.

Yes, that's why I'm not completely against the private system in place
now.  I do agree with your point here.  As I suggested earlier, the easy
solution might be simply to ask a nominee if they want to be considered...
if they do, they accept whatever might come out.  At least then the
reasons for a failed nomination are obvious to all, including the nominee,
there is no opportunity for anyone to accuse the PMC of doing anything
improper.  I believe transparency is good, but I also think not
embarassing people is good... accepting a nomination seems like a good
compromise to me.

> One blind spot right now might be the wiki. Some people have been
> making some great contributions to the wiki, but because they don't go
> into the repository, they don't seem like patches. But, we should
> start considering wiki contributions to be as valuable as
> contributions to the other documentation.

I would agree with that, and not just because I've made a few
contributions to the Wiki! :)

> And thanks for this post, and all the other helpful posts you and so
> many others make to the list.

No problem... I derive a lot of enjoyment from helping people when I can. 
Thanks for considering :)

Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Ted Husted <te...@gmail.com>.
On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> * Proposed Change:

I should mention that proposals for change are best sent to dev@. This
list is meant for people who want help using a product. Changes to the
project are best discussed on dev@. We should get back on task as to
the role of each list, and :) stop annoying people who just want to
know how to use the taglibs :)


> First, let me make clear that this proposal does NOT change the existing
> mechanism by which someone is invited to be a committer.  That decision
> still rests soley with the PMC.  This proposal only seeks to build on
> top of that mechanism.  I propose that a community-based nomination
> process be instituted.  For the sake of discussion, a "qualified" person
> is anyone that has been on the Struts Dev and/or User mailing lists for
> at least 6 months and has been relatively active (say, at minimum, 2
> posts per week total).

The main reason we make someone a committer is so that he or she can
commit directly to the repository, without waiting for someone else to
apply a patch. Aside from posting to the  mailing list, or commenting
on issue tickets, an important aspect of being "active" should be
submitting patches that actually change the content of the repository.
(Otherwise there is no practical reason for the individual to be a
committer.) The "tipping point" for committer nominations is typically
whether an individual submits useful patches. In the "How to Help"
FAQ, we say:

----

In an ASF project, like Apache Struts, volunteers who make sustained
contributions to the project are invited to become "Committers". In
due course, Committers are invited to join the Project Management
Committee (PMC). A goal of the ASF is for all Committers to be on the
PMC.

By "sustained", we mean that an individual has been active in the
project for at least six months. The contributions should come in the
form of both patches (to code or documentation), and posts to the
mailing lists. Patches must be competent and accepted into the
repository. Posts must be consistently helpful, friendly, and
collaborative. The most important characteristic in a prospective
Committer is an amicable demeanor that fosters goodwill.

* http://struts.apache.org/helping.html

----

> Any qualified person is eligible for nomination,
> or to nominate someone else.  Naturally, a person could never nominate
> themselves.  A nomination must then be seconded by another qualified
> person.  At that point, a voting period of one week commences, where any
> non-committer and non-PMC member, "qualified" or not, may vote (the
> usual +1, 0, -1).  The original nominator is responsible for tallying
> the vote.  A person must receive at least 60% +1's (i.e., 6 out of 10
> must be +1) and no more than half of the remainder may be negative.  At
> the end of that one week period, the vote results will be posted to the
> Dev list and a similar one week period will commence where existing
> Struts team members vote for the nominee.  Also note that at any point,
> the nominee can decline the nomination.  We wouldn't want to offer
> someone up that doesn't want to job!

Back at Jakarta, we used to have committer votes on public lists, and
I saw a lot of those go very wrong. People would use them as an excuse
to talk about something else. It's hard to have a candid discussion
about a *person* on a public list. As it turns out, the Apache HTTPD
team has never had discussions about people on a public list. I think
that is a  much better way to go. We announce the tallies for the
committer votes that succeed, but we don't embarrass people by
announcing votes and discussions that fail.

Being popular on the mailing lists is a good thing. But, mailing list
posts don't get us any closer to releases. As a practical matter, we
need people who create code and documentation, *and* who can get along
with the other committers. The committers must be a set of people who
can and will do the work *and* collaborate without a lead developer or
other boss pulling the strings.


>
> * Conclusion:
> Once again, let me make perfectly clear that the existing PMC still
> retains 100% control over who is invited to join.  This proposal only
> serves to introduce a mechanism by which members of the community can be
> nominated and force a vote by the PMC.

If you want to "force" a vote by the PMC, why not just bring one up on
dev@? But, please, check with the nominee first, to be sure he or she
wishes to be discussed on a public list in this way.

A better approach might be to send your nomination to the PMC chair
and ask that it be forwarded to the PMC list. Based on votes I've seen
at Jakarta and other PMC lists, the usual form is something like this:

----

The nominee has been an active contributor to the project for more
than six months. The nominee's posts to user@ and dev@ are
consistently helpful. The nominee often participates in development
discussions in a collaborative way. The nominee has submitted code and
patches and collaborated on changes that were accepted to the code
base.

* << link to report showing the nominee's patches >>

Here's my +1.

----

> That is of course the first
> important principle of this proposal.  The other important principle is
> taking the will of the community into account.  By having the PMC not
> vote until AFTER the community has voted, the "will of the community"
> should be apparent, and the idea is that the PMC will take that into
> account when voting.  The community will then have a clear indication
> whether they have been listened to or not based on the outcome of the
> vote (and the comments made during the vote because, after all, there
> ould be legitimate reasons not to adhere to the community's vote, and
> hose reasons should come out in discussion).

>From an ASF perspective, the "community" is not everyone who
subscribes to the mailing list and downloads the product. The
community is the set of individuals who contribute to the project,
both by making helpful posts to the mailing list *and* by contributing
useful code and documentation. Downloads don't make the product
possible. Contributions make the product possible. Our customers are
the contributors, who pay for the product with posts and patches.

An ASF project is about creating a collaborative community of
developers, who do the work and make the decisions. It's not just
about creating a product for other people to download. It's about
creating and maintaining the product that we want to use ourselves,
and sharing that product with others who might also find it useful.
Users are our way of finding new contributors.

If we've overlooked someone who is making helpful posts, submitting
useful patches, and who also works well with others, please let me
know. In the case of patches, please also include links to several
tickets that were applied.

Over the years, I think there have been exactly two committer
nominations here that failed, and both times the failed nominees had
not submitted a single patch.


> But, at the end of the
> day, who is invited to join is still decided by the PMC, as it is today.

:) Well, yeah. We're the ones that have to live with the decision,
long after whoever "voted" on the nomiantion might have unsubscribed
and faded away. :)

Who I would feel sorry for is all the people who might be nominated,
and then turned down, on a public list, without ever even asking to be
nominated or discussed in a public forum. This isn't about making
legislation or winning a popularity contest. We need people who *can
and do* create code or documentation and *collaborate* with other team
members, without a suit or "lead developer" pulling the strings.

> * Rationale
> One of the issues that a number of people seem to have with the way
> Struts has progressed is the seeming inability (or difficulty at least)
> of getting "new blood" involved.

As Craig mentions, six new committers joined us in the last year,
along with seven others in the WebWork merger. That seems like quite a
lot of "new blood" to me.

> There seems to be a perception by many
> that there is a bit of a "closed club" mentality with regard to being
> invited in as a committer and that the Struts community at large has no
> say in the matter.

All of our development resources are managed in the open. Any one can
download the source, report an issue, submit a patch, write to the
wiki, or post to the unmoderated lists. What's more, under the Apache
License, anyone who is willing to do the work can take the codebase
and start their own project.

We are prudent when it comes to direct write access to the repository.
We use the repository to generate releases, and the ASF takes
releases, and supporting releases, very seriously. It's not just about
slapping code together and seeing if it sticks. It's about being
ready, willing, and able to support the product over the long haul.
When someone does make sustained and welcome contributions to the
codebase and to the lists, I do believe we've been asking those people
to join us as committers. If there are people we haven't invited, I'd
suggest it's either an oversight, or because a person's contributions
have been one-sided, all patches or all posts.

One blind spot right now might be the wiki. Some people have been
making some great contributions to the wiki, but because they don't go
into the repository, they don't seem like patches. But, we should
start considering wiki contributions to be as valuable as
contributions to the other documentation.

> I look forward to feedback. Thanks for listening!

And thanks for this post, and all the other helpful posts you and so
many others make to the list.

>
> Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: Proposal for change

Posted by Jonathan Revusky <re...@wanadoo.es>.
Craig McClanahan wrote:
> On 4/24/06, Frank W. Zammetti <fz...@omnytex.com> wrote:
> 
>>
>>I look forward to feedback.  Thanks for listening!
> 
> 
> 
> Without commenting on the merit of the proposal itself, or the reasoning
> presented as its justification, it is important to note that we (the Struts
> community) do not have free reign to do whatever we want in this regard.  

Craig, while you aren't directly addressing me in this post, I take some 
offense to the above statement. It is very insulting. You are insulting 
people's intelligence.

First of all, this "royal we" of speaking in the name of the community 
rubs me the wrong way. Also, it is quite obvious to me that, so-called 
"Apache Way" or not, a community can add more committers if it wants to. 
What discussions or proposals precede that is really pretty much beside 
the point.

You collectively can certainly add Frank and other people who are 
willing and able to do work as committers if you want to. Now, I'm 
inferring that you don't want to do that. But then you should come up 
with some other reason than this stuff about community and the "Apache Way".

> As
> part of Apache, the Struts community is accountable to the Apache Software
> Foundation's Board of Directors, and one of the things that gets watched is
> how well the various projects implement "the Apache Way".  And one of the
> key tenets of that "way" is how new committers get selected.

My casual observation suggests that the "way" in which new committers 
get selected is entirely arbitrary.

In fact, it strikes me that what you are saying is 180ยบ from the truth. 
If I want to know how somebody who has a ph.D. in a field has that 
degree, I can go dig up the guy's doctoral dissertation and see how he 
got the degree. If somebody is a member of the New York Bar, they must 
have passed the New York Bar examination, and I could dig up examples of 
  the test that person would have had to pass. Guilds of medieval 
craftsmen had a system whereby, to become a full member of the guild, a 
"master" of the craft, you had to present some kind of major work. This 
is where the term "masterpiece" comes from IIRC.

As regards the question of why one person is a "committer" and somebody 
else is not, there is simply no equivalent way of pointing to why 
somebody is a committer and another person is not.

Anyway, I think the text you wrote above is a further insult to people's 
intelligence. I don't find what you're saying credible. I am quite sure
that the "Struts community" can add whoever they want as a committer and 
the ASF Board of Directors is not going to say boo.

Are there any precedents you can point to?

Like, project FooBar added Joe Blow as a commmitter and the ASF Board of
Directors actually took issue with this?

Does this ever happen?

So I get the very very real sense here that you guys just make up this 
stuff as you go along. Though I don't know which aspect is more 
distturbing -- that you do this, or that other people just meekly go 
along with it...

> 
> Regardless of the details, anything along the general lines of what you
> describe would be quite different from the way Apache has grown from the
> very beginning to what it is today -- and it would, therefore, be looked at
> with a *lot* of skepticism by Apache as a whole. 

Well, you seem to be implying that other ASF members who are not at all 
involved in Struts are going to second-guess your decisions about who to 
add as a committer and why you added the person(s) in question.

This just does not ring true to me.

> Trying to argue that the
> Apache Way is flawed, and needs to be fundamentally changed like this, does
> not seem likely (to me) to get much agreement Apache wide, given the ASF's
> history, and the success of many of its projects at building communities of
> committers that buy in to that culture -- and, by the way, produce some
> pretty popular software to boot.

Well, much (maybe most) of the software under the ASF brand was 
developed originally outside of ASF. In the case of what is going on 
with Struts right now, you are currently in the process of relabelling a 
competing product, Webwork, as "Struts Action 2". Since the existing 
Struts is going to be "Struts Action 1", there is a tacit acceptance of 
the fact that the codebase developed within ASF, and presumably 
according to the "Apache Way", was technically superseded by the 
codebase developed outside of ASF.

It is quite clear that Struts 1.x development stagnated terribly and, to 
keep saying that you can't do anything any differently from what was 
done heretofore because it runs against this so-called "Apache Way" -- 
this strikes me as lunacy.


> 
> So what the heck is this "Apache way" thing?  It is a culture; a way of
> gathering a community that interoperates ... 

In another part of this overall discussion, Niall Pemberton took me to 
task (or tried to) because he characterized my attitude as wanting the 
"demise of apache" and I did not deign to elaborate on that. (An example 
presumably of me "walking away from discussions")

Well, one basic benefit of a hypothetical "demise of ASF" would be that 
one would no longer have to hear any of this claptrap about the "Apache 
Way". Frankly, that would be one major improvement in the situation. <sigh>

> and it can be tough at times to
> write down a descrption that makes sense.  

Well, the other possibility is that, if you can't write a description of 
the "Apache Way" that really makes sense, maybe it's because it doesn't 
really make any sense...

Also, if it's left deliberately vague what the "Apache Way" is, kind of 
mystical, you can set yourself up as the interpreter of what the "Apache 
  Way" is and this gives you leeway to stifle needed discussion by 
jumping in and saying: "this runs counter to the Apache Way".

> But [1] is a pretty good starting
> point.  I'd also recommend looking through the documentation for the
> Incubator Project (where a specific exit criteria is that the folks
> participating in the new project "get it" about the Apache way).

You know, recently, in private correspondence, somebody who is on the 
PMC of a project that recently graduated from the "incubator" told me 
that he didn't really understand what the "Apache Way" was.

The real fact of the matter is that projects in the incubator want to 
get in on ASF because, like, it's a big ball of wax, you know. They know 
that their work will get a lot more visibility by being on apache.org 
than where it was previously. So, you know, you guys spout this stuff 
about the "Apache Way" and they basically say: "Whatever you say, man..."

That's the way it really is...

It reminds me of the scene in the Shawshank Redemption where Red (The 
Morgan Freeman character) is asked by the parole board: "Do you consider
yourself rehabilitated?"

"Oh, yessah, I am most definitely rehabilitated..."

Similarly:

"Do you consider that you now "get" the "Apache Way".

"Oh, yessah, we most definitely do..."

I know that in private, at least some of these guys will tell you that 
they don't even understand WTF the "Apache Way is!!! And they've been 
through this incubator and so on...


> 
> Frank
> 
> 
> Craig
> 
> [1] http://www.apache.org/foundation/how-it-works.html
> 
> PS:  If you like the code but don't like the community, one of the best
> things about Apache is that the license gives you the right to fork and
> build your own community, operated according to whatever rules please you.
> So, even if a proposal like this is not accepted, you still have the
> opportunity to go build "a better Struts" -- that doesn't have to be done
> here.

Yeah, in other words: "Why don't you go fork off?"

Well, this begs the question really. First of all, it is not a special 
characteristic of Apache projects that you can go fork them off 
somewhere. That's true of open source projects generally.

The problem is that, once you're working on a non-canonical version of
the code, your work only gets a small fraction of the usage and 
attention that it would if it was part of the canonical Struts project 
on apache.org. You are basically in the position of being out in the 
cold, shouting into the void.

I would bet that if you reviewed the list of current Struts committers, 
you would find that there are people there who have contributed nothing 
or hardly anything substantial in years. Why should they be committers 
when somebody who wants to do something, like Frank, is out in the cold?

If that is what the Apache Way says, I think then, most pragmatic people 
would say, to h*ll with the Apache Way.

OTOH, I don't think that either. I think the so-called "Apache Way" and
all the vacuous verbiage around it is basically a kind of MacGuffin you
guys trot out.

So stop it. Please answer the question without any nonsense about the 
Apache Way:

What is the reason not to let Frank (or others who are able and willing
to do so) commit code?

Jonathan Revusky
--
lead developer, FreeMarker project, http://freemarker.org/
FreeMarker blog, http://freemarker.blogspot.com/




> 





---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org