jakarta-oro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Markey <kmar...@onerealm.com>
Subject RE: jakarta-oro dilemma
Date Tue, 12 Aug 2003 21:33:57 GMT
Our firm has incorporated ORO into one of our products for the 
following reasons:

1. At the time, java.util.regex did not exist.
2. We prefer Perl regex compatibility.
3. There are still apparent ORO performance advantages.
4. There are still weaknesses in java.util.regex.
5. ORO has proven to be a solid, reliable component.

For these reasons, we hope that whatever is decided maintains 
approximately the same API and adds Perl 5.8 compatibility.

And please accept our thanks for everyone who has contributed to 
the ORO project.

Without knowing more about the proposed 2.0.8 release, its timing, and 
any proposed division of labor, it would be difficult to commit to 
personally contribute, but I would be happy to seriously consider such 
a contribution.  Please keep me on the list and up-to-date on plans.

Kevin Markey

> -----Original Message-----
> From: Daniel F. Savarese [mailto:dfs@savarese.org]
> Sent: Tuesday, August 12, 2003 12:02 PM
> To: pmc@jakarta.apache.org
> Cc: oro-dev@jakarta.apache.org
> Subject: jakarta-oro dilemma
> Dear Jakarta PMC,
> We've got a problem over in jakarta-oro that we need the PMC 
> to help fix.
> We no longer have a quorum of active committers to vote on things.
> But we do have active contributors and plenty of active users.  We
> need to get our 2.0.8 release out the door and have been fudging the
> voting rules for a couple of previous releases, by counting votes from
> two active contributors who aren't committers, in addition to my vote
> (an active committer) and Jon Steven's vote (who is a committer, but
> not active).  This can't go on any longer because it's just 
> not correct
> procedure.  We'd like to vote two active contributors in as 
> committers,
> but for obvious reasons we can't.  Therefore, we need the PMC to step
> in and help.
> There are several, not necessarily mutually exclusive, possibilities:
>   1. PMC evaluates situation and votes in two committers, 
> restoring the
>      necessary quorum.
>   2. PMC takes over voting responsibility for releases, which 
> I believe
>      is the long term goal for all Jakarta projects.  In this 
> case, I'd
>      request to be added to/voted onto the PMC because I'm a 
> former PMC
>      member and someone from the project should be around to initiate
>      votes.
>   3. Project is opened up to all Jakarta committers and those 
> interested
>      subscribe to dev mailing list and participate in votes.
>   4. Make jakarta-regexp committers jakarta-oro committers 
> and vice versa,
>      as I believe jakarta-regexp is in a similar situation to 
> jakarta-oro.
>      Whether or not the two projects would merge would be 
> decided later,
>      but participants of each could take an active role in helping the
>      other project along.
>   5. A call for participation is made to general@jakarta and 
> any already
>      existing Jakarta committer willing to contribute some time to the
>      project is automatically made a committer for the project.
> I'm sure there are additional alternatives.  I'm happy with any of the
> above.
> Specifically, we've been wanting to vote on
> Takashi Okamoto <tokamoto at rd.nttdata.co.jp> and
> Mark Murphy <markm at tyrell.com>
> as committers, because of the significant code contributions they
> have made and their continued active participation in development
> discussions.
> As a side note, the project has been hindered by its advanced
> stage of development when initially imported as a Jakarta project
> (no itches to scratch), initial reluctance to vote in committers
> because of SVN always being on the horizon and my (mis)perception that
> the ASF wanted to limit the creation of new committer 
> accounts, and more
> recently, the J2SE 1.4 javax.regex package.  However, there is still a
> role for jakarta-oro to play in the Java and Jakarta 
> ecosystems, but we
> have to break the project out of it's current doldrums.  The problems
> that developed with jakarta-oro did not arise with commons-net because
> I took a back seat and forced the user community to take the lead and
> become the development community before it entered the commons-sandbox
> and then commons proper.  In other words, commons-net is healthy and
> will survive without my participation, but I'm afraid the same isn't
> the case with jakarta-oro and we need to get it to that point.  As I
> mentioned above, jakarta-regexp is also in a paralyzed state, 
> with only
> one truly active committer, preventing release votes.  So in 
> considering
> jakarta-oro, jakarta-regexp should also be considered.
> thanks,
> daniel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: oro-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: oro-dev-help@jakarta.apache.org

View raw message