You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Leon Rosenberg <st...@anotheria.net> on 2005/09/10 18:19:49 UTC
Re: Who (really) decides?
> -----Ursprüngliche Nachricht-----
> Von: Frank W. Zammetti [mailto:fzlists@omnytex.com]
> Gesendet: Samstag, 10. September 2005 17:12
> An: Struts Users Mailing List
> Betreff: Re: Who decides?
>
> Ted Husted wrote:
> > Sometimes, we hear about people "voting with their feet". Here, we
> > invite people to vote with their hands, by collaborating on
> code and
> > documentation. It's not up to anyone else. It's up to everyone who
> > volunteers. Here, the only decisions that matter are patches and
> > commits, because without commits, nothing can change.
>
> Interesting... It's not really up to those that "vote", it
> is always in the end up to those that "commit". Every time a
> contribution is turned away, that is in essence saying "your
> vote doesn't count, at least this time", isn't it?
I agree with Frank that, what Ted says, is nice and right and everything,
but it's the theory. The real life shows it's cold shoulder.
I don't know whether my example fits your question, but at least it fits the
topic of the thread, so it came in handy.
As you might know, or not know, there is an issue with tomcat 5. To make it
short:
You can not use struts (or probably most other jakarta projects) with tomcat
5. The issue has been submitted. There is a patch available. The bug became
16 votes (btw. some struts commiters voted too), which is by far most votes
on open tomcat 5 bugs right now.
So far to the community part. The tomcat developers or probably the tomcat
developer in lead, Remy Maucherat, refuses to fix it.
So who really decides? Anyone, but not the community and not the users. (And
please don't think that struts is safe from that)
>
> > Discussion is good. Stepping up to the plate and making a
> difference is better.
>
> But how many times have people stepped up and been stopped
> from making a difference? In the end, isn't it the
> committers that have the power to direct where things go,
> regardless of what the community "votes"? As Craig said, a
> good community-driven project will listen to the community.
Yes, and it seems that "community-driven projects" are not to be found at
apache.
Regards
Leon
P.S. In case you didn't know it yet, here is the link to the tomcat issue:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36541
P.P.S. By the way, when goes struts warn their users, that struts 1.1, 1.2.x
and 1.3 aren't compliant with tomcat 5?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Session Synchronization Issues (Re: Who (really) decides?)
Posted by Leon Rosenberg <st...@anotheria.net>.
On Mon, 2005-09-12 at 11:18 -0500, Joe Germuska wrote:
> At 5:24 PM +0200 9/12/05, Leon Rosenberg wrote:
> >And I think there is no PMC for tomcat?
>
> Tomcat is still officially a Jakarta subproject, so the Jakarta PMC
> fills this role. I'm not sure at this time if they are planning to
> move to TLP or not, but probably someone else on this list knows.
>
> > > If nothing changes by Wednesday, if it were me, I'd submit a patch to
> >> the documentation summarizing the issue and pointing to the ticket.
> >
> >How can I submit a patch to the documentation?
>
> The site is in CVS (not SVN); I think this is the main root:
> http://svn.apache.org/viewcvs.cgi/jakarta-tomcat/src/doc/?root=Apache
>
> By the way, iId like to point out that in Struts 1.3 the
> ActionContext provides a pretty convenient way to organize your
> application to help control this. (Soon-to-be-) Common practice is
> to specify an alternative implementation class for ActionContext with
> your own typesafe property methods which internally use the request
> and/or session to store values. You could control synchronization on
> those methods.
>
> At this time, Struts doesn't routinely place the ActionContext itself
> into the request scope (although perhaps it should?) but if you put
> it there, then even your JSPs could use the ActionContext as a facade
> against the Session and then you could control the sync issues.
Sounds interesting, will look into it,
thanx
Leon
>
> Joe
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Session Synchronization Issues (Re: Who (really) decides?)
Posted by Joe Germuska <Jo...@Germuska.com>.
At 5:24 PM +0200 9/12/05, Leon Rosenberg wrote:
>And I think there is no PMC for tomcat?
Tomcat is still officially a Jakarta subproject, so the Jakarta PMC
fills this role. I'm not sure at this time if they are planning to
move to TLP or not, but probably someone else on this list knows.
> > If nothing changes by Wednesday, if it were me, I'd submit a patch to
>> the documentation summarizing the issue and pointing to the ticket.
>
>How can I submit a patch to the documentation?
The site is in CVS (not SVN); I think this is the main root:
http://svn.apache.org/viewcvs.cgi/jakarta-tomcat/src/doc/?root=Apache
By the way, iId like to point out that in Struts 1.3 the
ActionContext provides a pretty convenient way to organize your
application to help control this. (Soon-to-be-) Common practice is
to specify an alternative implementation class for ActionContext with
your own typesafe property methods which internally use the request
and/or session to store values. You could control synchronization on
those methods.
At this time, Struts doesn't routinely place the ActionContext itself
into the request scope (although perhaps it should?) but if you put
it there, then even your JSPs could use the ActionContext as a facade
against the Session and then you could control the sync issues.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Who (really) decides?
Posted by Ted Husted <te...@gmail.com>.
On 9/12/05, David G. Friedman <hu...@ix.netcom.com> wrote:
> > From: Ted Husted [mailto:ted.husted@gmail.com]
> > Apache Tomcat was established as a top-level
> > project in May. The PMC members are
>
> Funny but I didn't see anything in their front page or main documentation
> about this when I did a search on the Jakarta site.
Tomcat hasn't done the infrastructure work yet. The Tomcat TLP
resolution is part of the May 2005 ASF Board minutes. They've only
posted through April 2005 on the website so far, but the records will
be made public in due course.
Because of the lag in the posting of the board minutes on the web
site, the ASF President, Greg Stein, sends the committers a summary
each month. As an ASF member, I'm also subscribed to the internal
board mailing list, which posts the meeting agendas and draft
resolutions for each meeting.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
RE: Who (really) decides?
Posted by Leon Rosenberg <st...@anotheria.net>.
a quote from remy (in the bug comments)
"I wasn't really serious. In the end, it's not really my decision, so
you should send a request to the pmc once it is correctly setup."
So I assume TC is a TLP but they aren't functional yet, this would
explain Ted's and your posts :-)
regards
Leon
On Mon, 2005-09-12 at 12:34 -0400, David G. Friedman wrote:
> > From: Ted Husted [mailto:ted.husted@gmail.com]
> > Apache Tomcat was established as a top-level
> > project in May. The PMC members are
>
> Funny but I didn't see anything in their front page or main documentation
> about this when I did a search on the Jakarta site. Plus, top-levels
> usually
> work for urls like http://tomcat.apache.org and, well, there's just a funny
> redirect there. Any idea why they didn't change the URL and post it to
> their quarterly notes? For example, their q1 notes list Lucene being
> upgraded to top-level with the heading "Lucene moves to Apache top-level"
> but nothing for Tomcat.
>
> The Q1 & Q2 (may) notes don't show anything about Tomcat top-level status
> either. I'm curious, do you remember where you heard about that?
>
> Jakarta Projects' Q1 notes:
> http://jakarta.apache.org/site/news/news-2005-q1.html
>
> Jakarta Projects' Q2 notes:
> http://jakarta.apache.org/site/news/news-2005-q2.html
>
> Jakarta Projects' Q3 notes:
> http://jakarta.apache.org/site/news/news-2005-q3.html
>
> Ever curious,
> David
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
RE: Who (really) decides?
Posted by "David G. Friedman" <hu...@ix.netcom.com>.
> From: Ted Husted [mailto:ted.husted@gmail.com]
> Apache Tomcat was established as a top-level
> project in May. The PMC members are
Funny but I didn't see anything in their front page or main documentation
about this when I did a search on the Jakarta site. Plus, top-levels
usually
work for urls like http://tomcat.apache.org and, well, there's just a funny
redirect there. Any idea why they didn't change the URL and post it to
their quarterly notes? For example, their q1 notes list Lucene being
upgraded to top-level with the heading "Lucene moves to Apache top-level"
but nothing for Tomcat.
The Q1 & Q2 (may) notes don't show anything about Tomcat top-level status
either. I'm curious, do you remember where you heard about that?
Jakarta Projects' Q1 notes:
http://jakarta.apache.org/site/news/news-2005-q1.html
Jakarta Projects' Q2 notes:
http://jakarta.apache.org/site/news/news-2005-q2.html
Jakarta Projects' Q3 notes:
http://jakarta.apache.org/site/news/news-2005-q3.html
Ever curious,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Who (really) decides?
Posted by Ted Husted <te...@gmail.com>.
On 9/12/05, Leon Rosenberg <st...@anotheria.net> wrote:
> How can I submit a patch to the documentation?
It's the same as code, only to XML source.
* http://jakarta.apache.org/site/source.html#Patches
> And I think there is no PMC for tomcat?
Apache Tomcat was established as a top-level project in May. The PMC
members are
Jean-Francois Arcand (jfarcand@apache.org)
Bill Barker (billbarker@apache.org)
Kin-man Chung (kinman@apache.org)
Jean-Frederic Clere (jfclere@apache.org)
Ian Darwin (idarwin@apache.org)
Tim Funk (funkman@apache.org)
Henri Gomez (hgomez@apache.org)
Filip Hanik (fhanik@apache.org)
Larry Isaacs (larryi@apache.org)
Jim Jagielski (jim@apache.org)
Jan Luehe (luehe@apache.org)
Costin Manolache (costin@apache.org)
Remy Maucherat (remm@apache.org)
Kurt Miller (truk@apache.org)
Glenn Nielsen (glenn@apache.org)
Amy Roh (amyroh@apache.org)
Peter Rossbach (pero@apache.org)
Yoav Shapira (yoavs@apache.org)
Mark Thomas (markt@apache.org)
Mladen Turk (mturk@apache.org)
Keith Wannamaker (keith@apache.org)
-- HTH, Ted.
http://www.husted.com/poe/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Who (really) decides?
Posted by Leon Rosenberg <st...@anotheria.net>.
On Mon, 2005-09-12 at 06:23 -0400, Ted Husted wrote:
> On 9/10/05, Leon Rosenberg <st...@anotheria.net> wrote:
> > I agree with Frank that, what Ted says, is nice and right and everything,
> > but it's the theory. The real life shows it's cold shoulder.
> >
> > I don't know whether my example fits your question, but at least it fits the
> > topic of the thread, so it came in handy.
> > As you might know, or not know, there is an issue with tomcat 5. To make it
> > short:
> > You can not use struts (or probably most other jakarta projects) with tomcat
> > 5. The issue has been submitted. There is a patch available. The bug became
> > 16 votes (btw. some struts commiters voted too), which is by far most votes
> > on open tomcat 5 bugs right now.
> > So far to the community part. The tomcat developers or probably the tomcat
> > developer in lead, Remy Maucherat, refuses to fix it.
> > So who really decides? Anyone, but not the community and not the users. (And
> > please don't think that struts is safe from that)
>
> Looking over the bugzilla ticket, which was posted on Friday, it looks
> like a healthy discussion to me. Sure, one committer wants the ticket
> to go away, but he is being overruled. If not by the other committers,
> certainly by users. Any Tomcat committer can apply that patch. It's
> not a heirarchy. One comitter does not need to ask another for
> permission to make a change.
So we just have to find a willing committer? :-) Maybe you know one? :-)
Btw, the issue is still resolved as invalid, so it doesn't look like
someone has been overruled... I mean tomcat developers / committers
(surely not all, but those involved) simply closed the case...
>
> In this particular instance, there seems to a problem with the
> specification. Unfortunately, the last I knew, the scope of the Tomcat
> project including staying in line with the specification. So, if
> someone did apply the patch, a PMC member could veto it on that
> technical ground. If another PMC member seconds the veto, then the
> patch would have be undone.
Well, this seems in fact being a spec interpretation issue. However, the
bug fix wouldn't harm the spec, because it seems that both cases are
valid. And in my personal opinion Frank's post hits the problem best:
spec or not, if I call session.getAttribute() or setAttribute
() in a servlet or Struts Action or whatnot, I do not expect there to be any
chance of the internal data structures getting corrupted... and I do not
expect to have to do anything myself to ensure any of this...
And I think there is no PMC for tomcat?
>
> But, if not for the specification issue, any Tomcat committer could
> apply that patch. If a PMC member tries to undo another member's
> change, without a technical justification, the likely result will be
> loss of his or her Apache account. We've seen that happen before. The
> ASF board wouldn't rule on a technical issue, but if one project
> member tries to run the project solo, that member is shown the door.
Still I miss the "one" committer :-)
>
> As it stands, in the span of three days, there seems to be available
> to the public
>
> * A patch that users can apply it to their own copy of Tomcat.
> * A suggestion for a compiled patch that people could just put in
> their classpath.
> * A change people can make to the configuation file that solves the problem.
The last one will probably exists in future versions, no committment
when... or "if at all".
>
> If nothing changes by Wednesday, if it were me, I'd submit a patch to
> the documentation summarizing the issue and pointing to the ticket.
How can I submit a patch to the documentation?
> I'd also start a thread on Tomcat User to be sure people know about
> the problem. (Being careful to take that tact: Alert people of the
> problem, without complaining that no one will apply the patch.)
Will do.
>
> You might also encourage people to send in their request to clarify
> the specification, as Craig has already done. If the specification is
> clarified, then the patch is veto-proof. All you need is one Tomcat
> PMC member who will apply it, and the deed is done.
I sent a request to sun myself too, and guess what answer i got... none
at all.
>
> If the issue is not resolved by the time the next release vote comes
> around, if it were me, I'd vote -1 on the release and encourage
> everyone involved in the bugzilla ticket and user thread to do the
> same. The -1s won't be binding, but if the users outvote the
> committers by a wide margin, people will start to wake up and smell
> the coffee.
will do.
>
> (Did someone say coffee?...)
great idea :-) entering *coffee dreaming, moving in the kitchen mode
now*
best regards
Leon
>
> -- HTH, Ted.
> http://www.husted.com/poe/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Who (really) decides?
Posted by Ted Husted <te...@gmail.com>.
On 9/10/05, Leon Rosenberg <st...@anotheria.net> wrote:
> I agree with Frank that, what Ted says, is nice and right and everything,
> but it's the theory. The real life shows it's cold shoulder.
>
> I don't know whether my example fits your question, but at least it fits the
> topic of the thread, so it came in handy.
> As you might know, or not know, there is an issue with tomcat 5. To make it
> short:
> You can not use struts (or probably most other jakarta projects) with tomcat
> 5. The issue has been submitted. There is a patch available. The bug became
> 16 votes (btw. some struts commiters voted too), which is by far most votes
> on open tomcat 5 bugs right now.
> So far to the community part. The tomcat developers or probably the tomcat
> developer in lead, Remy Maucherat, refuses to fix it.
> So who really decides? Anyone, but not the community and not the users. (And
> please don't think that struts is safe from that)
Looking over the bugzilla ticket, which was posted on Friday, it looks
like a healthy discussion to me. Sure, one committer wants the ticket
to go away, but he is being overruled. If not by the other committers,
certainly by users. Any Tomcat committer can apply that patch. It's
not a heirarchy. One comitter does not need to ask another for
permission to make a change.
In this particular instance, there seems to a problem with the
specification. Unfortunately, the last I knew, the scope of the Tomcat
project including staying in line with the specification. So, if
someone did apply the patch, a PMC member could veto it on that
technical ground. If another PMC member seconds the veto, then the
patch would have be undone.
But, if not for the specification issue, any Tomcat committer could
apply that patch. If a PMC member tries to undo another member's
change, without a technical justification, the likely result will be
loss of his or her Apache account. We've seen that happen before. The
ASF board wouldn't rule on a technical issue, but if one project
member tries to run the project solo, that member is shown the door.
As it stands, in the span of three days, there seems to be available
to the public
* A patch that users can apply it to their own copy of Tomcat.
* A suggestion for a compiled patch that people could just put in
their classpath.
* A change people can make to the configuation file that solves the problem.
If nothing changes by Wednesday, if it were me, I'd submit a patch to
the documentation summarizing the issue and pointing to the ticket.
I'd also start a thread on Tomcat User to be sure people know about
the problem. (Being careful to take that tact: Alert people of the
problem, without complaining that no one will apply the patch.)
You might also encourage people to send in their request to clarify
the specification, as Craig has already done. If the specification is
clarified, then the patch is veto-proof. All you need is one Tomcat
PMC member who will apply it, and the deed is done.
If the issue is not resolved by the time the next release vote comes
around, if it were me, I'd vote -1 on the release and encourage
everyone involved in the bugzilla ticket and user thread to do the
same. The -1s won't be binding, but if the users outvote the
committers by a wide margin, people will start to wake up and smell
the coffee.
(Did someone say coffee?...)
-- HTH, Ted.
http://www.husted.com/poe/
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org