Re: [VOTE][LAZY] Move Jakarta Regexp to Attic
+1 Vadim On Mar 21, 2011, at 8:00 PM, Rahul Akolkar wrote: This is a vote to move Jakarta Regexp to the Apache Attic, based on the outcome of the most recent discussion on the topic. Since Regexp may not have enough PMC members active, this vote will be held by lazy consensus. If you object, please also provide a reasonable explanation. Vote runs for a week, ending no sooner than Mar 28th, ~8:00 pm Eastern US. Vote is being held on general@jao but is being cross-posted to ensure we reach the full audience. Please include general@jao on any replies. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: Regexp (was: Move ECS, ORO and Regexp to Attic)
On Mar 12, 2011, at 1:13 PM, Rahul Akolkar wrote: On Sat, Mar 12, 2011 at 10:33 AM, Ian Darwin i...@darwinsys.com wrote: Six months have passed and there hasn't been much activity. Should we revisit this now? Someone recently offered to contribute some code on regexp-user@, but it didn't generate enough interest for anyone to reply. daniel No-one's even interested in replying to Daniel's mail :-) On Friday night? Bah! I guess that means it should go to the Attic. snip/ Barring strong objections at this time, I'll initiate the process in one week (as we did for ECS and ORO, starting with a lazy consensus vote). I don't think I'll get to it within next few months, so will not object to moving it. Vadim - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [RESULT][VOTE][LAZY] Move ECS, ORO and Regexp to Attic
On Mar 11, 2011, at 9:09 PM, Daniel F. Savarese wrote: Someone recently offered to contribute some code on regexp-user@, Daniel - Unless I miss something... regexp-user is dead though? Was replaced by general a good while ago. Vadim - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [VOTE][LAZY] Move ECS, ORO and Regexp to Attic
On Aug 18, 2010, at 12:23 AM, Gary Gregory wrote: With RegEx in Java since 1.4, I do not see the need for these libs aside from legacy application support. I consider mothballing a service to the community at large: please, join us in the 21st century, port your RegEx code to Java 1.4. ;) I guess not everybody is satisfied with Java 1.4 version yet, otherwise there would be no such wide variety of choices: http://tusker.org/regex/regex_benchmark.html Vadim - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [VOTE][LAZY] Move ECS, ORO and Regexp to Attic
On Aug 15, 2010, at 12:16 AM, Rahul Akolkar wrote: This is a vote (or more correctly, three independent votes) to move Jakarta ECS, Jakarta ORO and Jakarta Regexp to the Apache Attic, based on the outcome of the most recent discussion on the topic. There is one unreleased bugfix on trunk since the last regexp release, that's probably the only reason stopping me from voting +1. But if you are eager to mothball it, I won't object. My vote is +0. Vadim Since none of these subprojects may have enough PMC members active, this vote will be held by lazy consensus. If you object, please also provide a reasonable explanation. Vote runs for a week, ending no sooner than Aug 22nd, ~1:00 am Eastern US. Vote is being held on gene...@jao but is being cross-posted to ensure we reach the full audience. Please include gene...@jao in your reply. -Rahul - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [VOTE] Merge dev lists
On Oct 19, 2009, at 4:02 PM, Rahul Akolkar wrote: [Suggestion is to please reply to the gene...@jakarta list only] This is a vote to consolidate the development lists at Jakarta into one development and one notifications list. For background including timing, anticipated benefits and some discussion, see proposal [1] thread. [X] +1 [ ] -1 While not required, it'd be nice if anyone voting against could briefly state the reason(s). And you're ofcourse welcome to vote +/-0 if you really want. Vote will run atleast 72 hours and will close no sooner than Thursday 5 pm EST. Regexp list has no traffic, and I don't have any objections if it were folded into general. Vadim - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [VOTE] - please! - Release JMeter 2.3 final
sebb wrote: Thanks to those who voted so far. At least two more PMC votes are needed - please! S/// On 25/09/2007, sebb [EMAIL PROTECTED] wrote: I've created what I hope will be JMeter 2.3 final in the directory: http://people.apache.org/~sebb/jmeter-2.3/dist Site/Docs are here: http://people.apache.org/~sebb/jmeter-2.3/site This is a bugfix release compared with RC4. Also some documentation has been updated. All feedback (and votes!) welcome. [ ]+1 - the release candidate is OK [ ]-1 - there is a problem (please indicate what it is) +1! Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
Henri Yandell wrote: So the question is; is the above direction worth discussing, Not sure about moving to incubator part -- but overall -- yes, IMHO it is worth discussing. Vadim or should we just go with the Commons TLP. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Niall Pemberton wrote: On 3/14/07, Vadim Gritsenko [EMAIL PROTECTED] wrote: sebb wrote: Also I think I need to update headers as per [3], is that correct? You also need a NOTICE file [3] Updated license headers, added NOTICE to zip/tar.gz. The NOTICE file is missing the copyright statement - see: Thanks, Niall. Corrected. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Henri Yandell wrote: This 'how we release' conversation has been bouncing around the ASF for 4 months now, the above is my best grok on the summary. I've not seen anyone yet speaking in favour of a view that we should have a vote on the idea of releasing and then someone does it when they can. Please bring that up on members@ Vadim - good luck. That is a tough crowd and I don't think I have enough skills to convince them on anything. OTOH, you can. It's pity though that ASF is loosing its values. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r520239 - /jakarta/site/docs/site/news/news-2007-q1.html
sebb wrote: URL: http://svn.apache.org/viewvc?view=revrev=520239 Log: set eol-style Modified: jakarta/site/docs/site/news/news-2007-q1.html (contents, props changed) By the way, when changing the SVN eol-style to native, if possible, it is best to do this on a platform which has the current eol-style. This should eliminate the difference listing. Interesting tip, thanks. (Un)fortunately I could not follow it. Of course, the best is to ensure that new documents are given the correct eol-style in the first place. Agreed. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCEMENT] Jakarta Regexp 1.5 released
The Jakarta Regexp team announces availability of the Jakarta Regexp 1.5 release. This is a maintenance release containing several bug fixes as well as performance optimizations for several classes of expressions. Complete list of changes is available at the website: http://jakarta.apache.org/regexp/changes.html Due to the changes in the implementation of reluctant closures, users of the recompile utility are advised to re-compile their expressions using version of the tool bundled with this Regexp release. Regexp comes in one small download, containing both compiled binary, docs and the source code. Download Regexp from the nearest mirror: http://jakarta.apache.org/site/downloads/downloads_regexp.cgi Bug reports and patches are accepted via Bugzilla, located at: http://issues.apache.org/bugzilla/ Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Henning Schmiedehausen wrote: Vadim, that is not the point. The procedure in itself is flawed. You missed it too :) Existing procedure might be flawed in somebody's opinion, and I'm not arguing that it is ideal, but proposed procedure is even worse. It makes any release impossible: release packages can be made available only after the release itself is made. This makes me think that such procedure comes from the camp not taking SCM seriously. Since the objective of the change to the process is to verify steps done by RM, the only viable procedure, in my view, is - (1) vote on SVN rev number (with packages made available), (2) tagging and building a release, (3) quick vote on resulting files. It's quick sine no actual software testing need to be performed, just verify that zip unzips and tar untars. Vadim There might be files now, but the procedure still has to be aligned to ASF wide guide lines. Before you wonder/think about conspiracy theories: Yes, I brought the board (i.e. Henri) attention to this. It is necessary to change the commons release procedures and if you think that experiences of other PMCs (Velocity) don't count, let's try with a board opinion. Best regards Henning Vadim Gritsenko schrieb: Henri Yandell wrote: 3) Creating the actual files that are going to be released and voting on them. There's pressure to go this way, but it's not the policy yet. Vote has passed, so now actual files are made, and are available at the same location [1]. Vadim [1] http://people.apache.org/~vgritsenko/regexp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
sebb wrote: On 19/03/07, Vadim Gritsenko [EMAIL PROTECTED] wrote: resulting files. It's quick sine no actual software testing need to be performed, just verify that zip unzips and tar untars. I think one also needs to check that: * that the various signature files are present and correct * the zips and tars contain the same files as each other * the zips and tars and contained jars contain the required NOTICE and LICENSE files * the source archive includes all the required sources from SVN * the bin archive includes all the required files (apart from any documented dependencies) (This is done by ant, btw, and so is 99% reproducible) I don't think these can be determined directly from the contents of an SVN rev number, so need to be checked after a potential release has been built. Hence I mentioned 'quick check of release files'. Would satisfy even procedure extremists. == As to release voting: Surely the most important thing is to ensure that a build is not released to the general public - i.e. not put in the dist tree - before the vote has passed. So long as the build files are in a private area - e.g. the RM's public_html directory - (and maybe are named as pre-release) the vote can be done on the actual files. Actual files, as you might have noticed, are impossible to produce before release is tagged. To tag a release, a vote must pass. Best you could do is to produce 'rc' build off of trunk. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
sebb wrote: Surely voting on creating a tag (if this is necessary) Absolutely. Any release tag must be a community decision == vote is required. is completely different from voting on a release? Not to me. Voting on a release (on a tag) signifies that software is in a state where it can be released to general public. Voting on a files (produced from release tag) is a mechanical vote on correctness of files produced by ant. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Jesse Kuhnert wrote: Ehh...Obviously I'm alone in my opinion so I'll shut up now, just wanted to make sure I got my two cents in. Make that two of us. ASF today indeed contains much more Administratium (thanks Dave, great link!) than it used to. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Martin Cooper wrote: Those sites provide infrastructure, but absolutely no legal protection. Who says there is no way to combine legal protection and non-absurd procedures? For example: community votes for a release, RM tags a release (and prepares files), pmc rubber-stamps it with 'ACK' within 72 hours (a-la PMC composition change process), done. And the big one. The main goal ASF exists for is fostering software development communities. With second goal being software released in the process. And the legal part here is an *evil necessity*, it is *not* a goal. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Martin Cooper wrote: On 3/19/07, Vadim Gritsenko [EMAIL PROTECTED] wrote: Martin Cooper wrote: Those sites provide infrastructure, but absolutely no legal protection. Who says there is no way to combine legal protection and non-absurd procedures? Not me. We don't have absurd procedures, so we're already there. I consider tag before vote as absurd. For example: community votes for a release, RM tags a release (and prepares files), pmc rubber-stamps it with 'ACK' within 72 hours (a-la PMC composition change process), done. PMCs are not about rubber-stamping anything. They are about project oversight and responsibility. Oversight and responsibility is happening before you tag. They are part of day to day work. Mechanical checks for NOTICE and LICENSE files preceding approval for distribution stamp happen after. And the big one. The main goal ASF exists for is fostering software development communities. With second goal being software released in the process. And the legal part here is an *evil necessity*, it is *not* a goal. Interesting perspective. Thanks. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Martin Cooper wrote: On 3/19/07, Vadim Gritsenko [EMAIL PROTECTED] wrote: Martin Cooper wrote: On 3/19/07, Vadim Gritsenko [EMAIL PROTECTED] wrote: Martin Cooper wrote: Those sites provide infrastructure, but absolutely no legal protection. Who says there is no way to combine legal protection and non-absurd procedures? Not me. We don't have absurd procedures, so we're already there. I consider tag before vote as absurd. Yeah, well I consider voting on something that doesn't exist yet to be absurd. So there we are. You tagging -- voluntarism; you tagging after a vote -- community supported decision. By the way, if you really want to change any of this, burying the discussion in a vote thread on this list isn't the best way to go about it. If there is no consensus, there is no point of pushing it. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] Release Regexp 1.5
The vote to release passes with +1s from: Vadim Gritsenko Henning Schmiedehausen Daniel F. Savarese sebb Henri Yandell wrote: There are (to my knowledge) three types of vote/release styles that have been happening at the ASF. 1) A vote to do a release, with no sign of release files. This is how this thread started and it's against ASF policy. Can you put a finger on this policy? I'm not sure I'm aware of such policy. 2) A vote on release-candidate files (or -dev in your case), and then a release that is trusted to be a repeat of the process used. This is currently a grey area policy-wise, and is where this release moved to with the ~/vgritsenko/*-dev files. Indeed. 3) Creating the actual files that are going to be released and voting on them. There's pressure to go this way, but it's not the policy yet. personally I do prefer Vote-then-Release myself but that seems to be the way it is. Release-then-Vote has some nice parts, the actual release is really easy. That's nice if the release process has been painful as it means I don't have to remember how to do the damn thing. Vote-then-Release is nice in that you don't end up doing as many vote builds. Other parts of the ASF seem to do a release where they make a build and if it passes a vote it goes out, if it doesn't then they up the bugfix number and do it again (I don't think anyone actually has a build number, ie: 1.3.5.7). They also have an alpha/beta/GA thing that the version number doesn't show. Very confusing as a user I think. Agree. Mostly at this stage the mandate is that we have to be voting on release files, not on Hey, how about a release. This is the single most valuable vote. Either community has a consensus on status of code in question - is it ready to be a GA release? - or not. There is some limited sense on voting on final files - just to make sure RM did not messed up in the process - but it has no much value over Hey, how about a release vote, and adds to the confusion, as you correctly noted above. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Henri Yandell wrote: snip/ PS I noticed that you forgot to vote this year :-) http://marc.info/?l=jakarta-generalm=11231425543 Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
Henri Yandell wrote: 3) Creating the actual files that are going to be released and voting on them. There's pressure to go this way, but it's not the policy yet. Vote has passed, so now actual files are made, and are available at the same location [1]. Vadim [1] http://people.apache.org/~vgritsenko/regexp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
sebb wrote:
The LICENSE and NOTICE files are now in the zip and jar, but they show
up for me as License and Notice. Ideally they should be in capitals.
They are:
[EMAIL PROTECTED] ~/public_html/regexp $ tar -tzf
jakarta-regexp-1.5-dev.tar.gz | grep dev/[^dsx]
jakarta-regexp-1.5-dev/LICENSE
jakarta-regexp-1.5-dev/NOTICE
jakarta-regexp-1.5-dev/README
[EMAIL PROTECTED] ~/public_html/regexp $ unzip -l jakarta-regexp-1.5-dev.zip |
grep dev/[^dsx]
11357 03-14-07 10:05 jakarta-regexp-1.5-dev/LICENSE
302 03-14-07 10:05 jakarta-regexp-1.5-dev/NOTICE
901 03-14-07 10:05 jakarta-regexp-1.5-dev/README
[EMAIL PROTECTED] ~/public_html/regexp $ unzip jakarta-regexp-1.5-dev.zip
jakarta-regexp-1.5-dev/jakarta-regexp-1.5-dev.jar
[EMAIL PROTECTED] ~/public_html/regexp $ unzip -l
jakarta-regexp-1.5-dev/jakarta-regexp-1.5-dev.jar | grep -v org
Archive: jakarta-regexp-1.5-dev/jakarta-regexp-1.5-dev.jar
Length Date TimeName
0 03-14-07 10:04 META-INF/
106 03-14-07 10:04 META-INF/MANIFEST.MF
11357 03-14-07 09:52 META-INF/LICENSE
302 10-31-06 22:36 META-INF/NOTICE
---
62348 24 files
[2] http://people.apache.org/~vgritsenko/regexp/
It would be nice if the MD5 files used the more standard format:
9336ab3a8871e055ca573ef6167ca90d *jakarta-regexp-1.5-dev.zip
so that MD5 tools can process the file automatically.
Which tools you have in mind? All tools known and available to me
(locally and on p.a.o) produce the output
MD5 (file.name) = a7845d1201075c5041a798ae1cd7b8c8
The only exception is 'md5 -r', but it does not put '*' before file name.
The '*' is supposed to be used for binary files; otherwise use ' ' (space).
The ones I have seen are:
http://en.wikipedia.org/wiki/Md5sum
It's not found on apache boxes.
http://mirror.href.com/thestarman/DOS/MD5progs.html#format
http://www.fourmilab.ch/md5/
That's exactly what I used. As mentioned above, can use 'md5 -r' if you prefer
it more. I guess that's exactly what you had in mind.
Vadim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Regexp 1.5
sebb wrote: Also I think I need to update headers as per [3], is that correct? You also need a NOTICE file [3] Updated license headers, added NOTICE to zip/tar.gz. The LICENSE and NOTICE files ought to go into the jar as well, as the jar may well be used on its own. Added both files to the META-INF directory of the jar file. License should be LICENSE [3] Yep, it is there [1]. Exact copy. [2] http://people.apache.org/~vgritsenko/regexp/ It would be nice if the MD5 files used the more standard format: 9336ab3a8871e055ca573ef6167ca90d *jakarta-regexp-1.5-dev.zip so that MD5 tools can process the file automatically. Which tools you have in mind? All tools known and available to me (locally and on p.a.o) produce the output MD5 (file.name) = a7845d1201075c5041a798ae1cd7b8c8 The only exception is 'md5 -r', but it does not put '*' before file name. Thanks for all the feedback. Files, now using r518169, are re-built and re-uploaded [2]. Vadim [1] http://svn.apache.org/repos/asf/jakarta/regexp/trunk/LICENSE [2] http://people.apache.org/~vgritsenko/regexp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Regexp 1.5
Hi All,
With 5 recent bug fixes [1], one *major* speed improvement for {m,n} closures
[2], with other various optimizations to compiler and runtime, and with previous
release published sometime back in 2005 [3], now is the best, or at the very
least, really good time to to cut next, 1.5 release of the venerable Jakarta
Regexp package.
Please try out current svn (r517970) version [4] and test for any regressions,
and vote for a release. Regexp test suite can be run by issuing 'ant test' in
the checkout directory, and does not take even 3 seconds to complete.
Interactive testing can be done by using applet version [5].
The only known incompatibility with Regexp 1.4 is that pre-compiled RE programs
created with 'recompile' utility [6] for patterns containing reluctant closures
are not compatible with trunk. But, that should not be a problem since they did
not work correctly before anyway [7].
My vote for the release is +1.
Thanks,
Vadim
[1] http://jakarta.apache.org/regexp/changes.html
[2] http://issues.apache.org/bugzilla/show_bug.cgi?id=9153
[3] http://marc.info/?l=jakarta-regexp-devm=112429683615736
[4] http://svn.apache.org/repos/asf/jakarta/regexp/trunk/
[5] http://jakarta.apache.org/regexp/applet.html
[6]
http://svn.apache.org/repos/asf/jakarta/regexp/trunk/src/java/org/apache/regexp/recompile.java
[7] http://issues.apache.org/bugzilla/show_bug.cgi?id=27763
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of JakartaBoardReport-current by HenriYandell
Apache Wiki wrote: + * Inactive - No activity, no one watching it. Candidate for dormancy. + * Maintenance - No activity, someone watching it. Henri, Regexp + See ORO. + According to your definition, Regexp should be in Maintenance state. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROPOSAL: commons-ssl
Julius Davies wrote: ... I had to explain that Commons-SSL just sits on top of the JSSE and JCE to try and make working with SSL and Java easier. Your point about the name is a good one. The counterpoint to name argument. Just single example, I'm sure there are many more: commons-logging sits on top of log4j/java logger/logkit/... and tries to make working with all them seamless. commons-ssl may be not the best name but it isn't terribly bad either. Vadim ... On 12/1/06, Roland Weber [EMAIL PROTECTED] wrote: The working title Commons-SSL does not really reflect this. Do you plan to implement the SSL protocol as part of the project? Probably not, so the title is misleading. An all-encompassing name might also be offensive to people working on other SSL-related projects. I think you should spend the time and define not only a motto, but a very clear scope of the project. Both in terms of what's in scope as well as what's out of scope. From there on, we can work on finding a name and home. Please do not underestimate the importance of this step. Finding a name may seem like a minor detail, but the problem of defining the scope is very real. Only a few months ago, there was a long discussion on this list about a proposal for testing.apache.org. I haven't read anything about it anymore after the supporters realized that a scope of everything that has to do with testing was overly broad. We don't want to see that happen to your proposal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Representing project inactivity on the site
Henri Yandell wrote: * ECS, ORO, Regexp to be moved to a label of Inactive. Think of Regexp as of low maintenance project. There are several issues reported against it, and some of those can be (relatively) easy fixed and new release can be pushed out. It would be disappointing if such labeling makes it harder to maintain project or forces users to look elsewhere. 'Mature' seems to better reflect current state of the project. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta stats
Martin van den Bemt wrote: Vadim Gritsenko wrote: Martin van den Bemt wrote: The result can be a couple of things (probably depending on the response) : - Leave it as is - Move them to emuritus Above two are the only acceptable choices for folks with valid accounts. We can discuss means and mechanisms of moving to emeritus and back, but removing folks who fall into groups 2) to 5) is unacceptable - all IMHO. Removing can also be started on request of the committer... So the third option is acceptable. (it is happening as we speak btw : Jeff Dever, see infrastructure list). Well that's different - we should not hold anybody against their will :-) Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta stats
Martin van den Bemt wrote: The result can be a couple of things (probably depending on the response) : - Leave it as is - Move them to emuritus Above two are the only acceptable choices for folks with valid accounts. We can discuss means and mechanisms of moving to emeritus and back, but removing folks who fall into groups 2) to 5) is unacceptable - all IMHO. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Jakarta Http Components
Henri Yandell wrote: So, period of comments now over, let's go ahead and vote on the creation of a Jakarta Subproject named Http Components with the following initial charter: http://wiki.apache.org/jakarta-httpclient/NewProjectCharter [ ] +1 [ ] -1 +1 Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: Subscribing a new Project into Jakarta
Felipe Leme wrote:
[EMAIL PROTECTED] wrote:
projects, but still, i must ask this to the FtpServer developers (i
don´t know who they are).
Hmm, there is a Maven-generated link that says Who We Are :-)
I didn´t find this information on the site.
Here is the link I mentioned:
http://incubator.apache.org/projects/ftpserver/team-list.html
(of course, you must change the {at} for @ and {d0t} for . :-)
Even better - mailing list
http://incubator.apache.org/projects/ftpserver/mail-lists.html
Vadim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: Subscribing a new Project into Jakarta
[EMAIL PROTECTED] wrote: On Wed, 12 Oct 2005, robert burrell donkin wrote: jakarta's been self consciously shrinking over the last few years (it's just too big and too complex) with a lot of old sub-projects graduating to lop level status. it's more difficult now to persuade people that new sub-projects should be accepted. (of course, this doesn't mean that JFTP4I couldn't aim for top level or for a sub-project of another project) Effectively it's turning into a component container, a larger variant of Commons. All of our server-like parts have moved to top level, and it sounds like JFTP4I would (despite not being just an FTP server) still be very much a server-like project. So definitely a TLP example. Yeah, i'm just i little confuse of how to initiate the process. Who to talk, what email to send, and so on. Have you seen FtpServer in incubation [1]? I would think there is significant overlap between projects, so may be instead of creating new project, you could join efforts with existing one? Vadim [1] http://incubator.apache.org/projects/ftpserver/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Jakarta Regexp 1.4 released
David J. M. Karlsen wrote: Vadim Gritsenko wrote: The Jakarta Regexp team announces availability of the Jakarta Regexp 1.4 release. Are there any plans for consolidating ORO and Regexp ? I had none. Unless you want to do it. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Jakarta Regexp 1.4 released
The Jakarta Regexp team announces availability of the Jakarta Regexp 1.4 release. This is a maintenance release containing several (eleven, to be presice) bug fixes accumulated since the 1.3 release almost 2 years ago. Complete list of changes is available at the website: http://jakarta.apache.org/regexp/changes.html Regexp comes in one small download, containing both compiled binary, docs and the source code. Download Regexp from the nearest mirror: http://jakarta.apache.org/site/downloads/downloads_regexp.cgi Bug reports and patches are accepted via Bugzilla, located at: http://issues.apache.org/bugzilla/ Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] Release Regexp 1.4
On Fri, 12 Aug 2005, Vadim Gritsenko [EMAIL PROTECTED] wrote: Please try out current svn (r232390) version [4] and test for any regressions, and vote for a release. Vote passes with 4 +1s [1], I'm cutting the release. Vadim [1] http://marc.theaimsgroup.com/?t=11238848995r=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Regexp 1.4
Hi All, With several recent bugfixes [1,2], and with previous release published almost two years ago [3], I think it is a good time to make a next, 1.4 release of the Jakarta Regexp. Please try out current svn (r232390) version [4] and test for any regressions, and vote for a release. My vote is +1. Thanks, Vadim [1] http://marc.theaimsgroup.com/?l=jakarta-regexp-devr=1b=200508 [2] http://jakarta.apache.org/regexp/changes.html [3] http://marc.theaimsgroup.com/?l=jakarta-regexp-devm=106260458007862 [4] http://svn.apache.org/repos/asf/jakarta/regexp/trunk/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: VOTE: Tomcat - TLP
Ian F. Darwin wrote: The question: I vote in support of the proposal to move Tomcat to an Apache Top Level Project as detailed in the attached Resolution. [ X ] +1 Vote in support Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download counts?
Howard Lewis Ship wrote: That seems low; how did you come up with that number? Some regexps over httpd logs. See http://www.apache.org/~vgritsenko/stats/index.html Vadim On Fri, 04 Feb 2005 09:37:49 -0500, Vadim Gritsenko [EMAIL PROTECTED] wrote: Howard Lewis Ship wrote: I'm continually asked how many downloads of Tapestry there are ... really, how many users. I realize that this is a difficult question to answer, due to the use of mirrors for downloads ... even so, is there any way to get this number? Estimate it? Guess it? 833 downloads in Jan'05. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download counts?
Henri Yandell wrote: So low can be very good, as it means people are using the mirrors. Ever looked into getting logs from the mirrors Vadim? No; I believe it will be hard to impossible to do, as those mirrors are independent entities and might not want anybody messing with theirs log files. As it is, numbers are useful to see project growth (decline), but they are not correct as absolute download numbers are. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy worries
Henri Yandell wrote: On Tue, 28 Dec 2004, Daniel F. Savarese wrote: snip/ Then we can solicit volunteers from the PMC to be committers for each project to ensure that each has at least three. Volunteering means you agree to review and adddress patches and bug reports, vote on releases, etc., but not necessarily undertake new development initiatives (unless you want to). I volunteer to play that role for regexp and I'm pretty sure Vadim wouldn't have a problem doing so for oro. Count me in. snip/ With respect to oro and regexp specifically, one of the following might help even though I don't really expect them to reawaken: 1. merge oro-dev,regexp-dev,regexp-user,oro-user into just regexp@ Very tempting to start by moving the two oro lists over to the two regexp lists. While oro is the fuller codebase, regexp has the better name. If that will not happen, I'm ok to subscribing to oro-dev. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can I use Hibernate in an Apache project without compromising the Apache License?
Henning Schmiedehausen wrote: On Tue, 2004-09-28 at 11:11, Brett Porter wrote: is not ASF License compliant? If yes, than I would really hate to have to point you at http://cvs.apache.org/viewcvs.cgi/maven-plugins/hibernate/src/main/org/apache/maven/hibernate/beans/SchemaExportBean.java?annotate=1.7 This would compromise all Maven releases that include the maven-hibernate-plugin. We distribute Binary and Source from apache.org sites... Thanks for bringing this up. I've been meaning to respond to this thread with that in mind. I think we've checked this in the past and because the ASF is not distributing the hibernate code, there wasn't a problem (as you say, hibernate is downloaded from ibiblio when the user chooses to use the hibernate plugin). So what would the answer of the first question of Oliver (can I use Hibernate in an ASF project) now be? If I got it right; Oliver wants to implement a Slide Store that uses Hibernate as back-end. According to your answer, he could do this as part of the official Slide distribution, as long as it does not contain the hibernate.jar itself (which could be downloaded as part of the build process (maven or ant)). The problem, AFAIU, is that this Maven's code now has to become LGPL licensed itself, due to LGPL license requirements. And ASF repositories can't contain LGPL code. So the answer is to pull (quickly) this code from Maven, and not to introduce to Slide. I agree, that we need a clarification (best would be a legal council backed clarification). Having to move every bit of maven code that references LGPL off-ASF would hit quite a few plugins. :-( Somebody could setup mavendev.org (see cocoondev.org) to host (L)GPL pieces. PS Copying PMC because action is required Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can I use Hibernate in an Apache project without compromising the Apache License?
Martin van den Bemt wrote: On Wed, 2004-09-29 at 13:56, Vadim Gritsenko wrote: Henning Schmiedehausen wrote: On Tue, 2004-09-28 at 11:11, Brett Porter wrote: is not ASF License compliant? If yes, than I would really hate to have to point you at http://cvs.apache.org/viewcvs.cgi/maven-plugins/hibernate/src/main/org/apache/maven/hibernate/beans/SchemaExportBean.java?annotate=1.7 This would compromise all Maven releases that include the maven-hibernate-plugin. We distribute Binary and Source from apache.org sites... Thanks for bringing this up. I've been meaning to respond to this thread with that in mind. I think we've checked this in the past and because the ASF is not distributing the hibernate code, there wasn't a problem (as you say, hibernate is downloaded from ibiblio when the user chooses to use the hibernate plugin). So what would the answer of the first question of Oliver (can I use Hibernate in an ASF project) now be? If I got it right; Oliver wants to implement a Slide Store that uses Hibernate as back-end. According to your answer, he could do this as part of the official Slide distribution, as long as it does not contain the hibernate.jar itself (which could be downloaded as part of the build process (maven or ant)). The problem, AFAIU, is that this Maven's code now has to become LGPL licensed itself, due to LGPL license requirements. And ASF repositories can't contain LGPL code. So the answer is to pull (quickly) this code from Maven, and not to introduce to Slide. Incorrect. Unless maven core depends on LPGL, which afaik doesn't. Just the plugins that depend on LGPL code need to become LPGL and probably need to move. The plugin architecture prevents the core from becoming infected. That's exactly what I'm talking about, plugin code, not whole Maven. Sorry for not being presice enough :-) Somebody could setup mavendev.org (see cocoondev.org) to host (L)GPL pieces. PS Copying PMC because action is required Ehh Maven has it's own PMC... Oops :-) I'll go with assumptions that you guys (Maven PMC) will take care of this. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can I use Hibernate in an Apache project without compromising the Apache License?
Geir Magnusson Jr. wrote: On Sep 29, 2004, at 4:56 AM, Vadim Gritsenko wrote: The problem, AFAIU, is that this Maven's code now has to become LGPL licensed itself, due to LGPL license requirements. And ASF repositories can't contain LGPL code. So the answer is to pull (quickly) this code from Maven, and not to introduce to Slide. No - LGPL isn't viral unless you make derivative works of the LGPL-ed code itself. Just using an LGPL-ed codebase as a library does not trigger the virality. According to some opinions, IIRC, import some.lgpl.stuff; triggers LGPL virality, I based my comment on this opinion. The problem is that for java, there are questions about the clarity of the provisions in the license that prevent the virality from taking effect, which is why the ASF doesn't allow LGPLed java usage. Exactly, the clarity is missing. Any progress on this front will be an improvement. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CVS-SVN Was: SVN of ECS
Henri Yandell wrote: My suggestion would be: jakarta/tomcat/tomcat-5 jakarta/tomcat/connectors jakarta/tomcat/servletapi ie) we'd delineate on definite subproject lines, rather than having projects with multiple directories in the jakarta-root. I'm not against servletapi (or any) being their own subprojects of Jakarta, or at least marketed that way, but if they are, then they should be truly setup as different to the tomcat subproject. +1 to all of the above. Vadim Hen On Tue, 28 Sep 2004, Shapira, Yoav wrote: Hi, Having lurked on this discussion so far, I have one question at this point. I've seen /jakarta/tomcat referenced. If you look at CVS, there's no such thing. Instead, there are several CVS modules for tomcat: jakarta-tomcat-5, jakarta-tomcat-4, jakarta-tomcat-catalina, jakarta-tomcat-connectors, jakarta-tomcat-jasper, jakarta-servletapi-5(*), etc. Under SVN, would these become /jakarta/tomcat/catalina or /jakarta/tomcat-catalina ? (*) = The Servlet API could be its own project, e.g. /jakarta/servlet-api, and does not have to be under the Tomcat tree. Yoav Shapira Millennium Research Informatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Updating PMC bylaws
Henri Yandell wrote: Suggested new bylaws are at: http://www.osjava.org/~hen/jakarta/management.html [X] +1 - let's do it [ ] -1 - not good Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Updating the PMC bylaws
Henri Yandell wrote: ... However, the aim for this modification is to bring it in line with reality and not future plans and we've never had a PMC member who was not a committer. Every (loose) description I've seen of a PMC describes it as the active committers to a project. Yup. So I'd like to stay with committers if possible. The PMC will contain at least 3 committers from each subproject [1] Even better: make it *active* committers. If person went inactive on the project, ideally he should be replaced with someone who is more active, in order to better represent project, and current status of the project. Vadim [1] http://www.osjava.org/~hen/jakarta/management.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [site] Sister Resources
Stefan Bodewig wrote: On Mon, 22 Mar 2004, Henri Yandell [EMAIL PROTECTED] wrote: Resources (Unofficial) gets my vote, works for me. Ditto Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] HiveMind as a Jakarta sub-project
Geir Magnusson Jr wrote: [ ] +1 I support this proposal [ ] -1 I don't support this proposal [X] 0 I abstain from voting for or against this proposal Comments : I'm not up-to-date on HiveMind :-) Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: news symlinks
Marcus Sundman wrote: Would it be possible to have symlinks like http://jakarta.apache.org/site/news/news-latest.html http://jakarta.apache.org/site/news/elsewhere-latest.html that would point to the latest news? we'd then risk people losing long term urls. probably getting apache to do temporary redirects from those urls would be ok, though. of course, i'd be interested to know what other people think on this before actually doing anything about it... Well, now one can't bookmark the news pages because the URLs change every once in a while, so something should be done. Neither symlinks nor temporary redirects are very good solutions. I think people most often want to see the latest news, e.g. a list of all news items less than N days old. If all news are on pages categorized e.g. by month then N will keep changing all the time (N=0 exactly when the month changes). Thus almost no one would see news posted in the very end of the month. I think the best solution would be to have one page with news N days old, and then have a completely separate news archive where news are categorized by month/year/whatever. The former could have news from both Jakarta and elsewhere on the same page, preventing people from having to check two URLs when reading news. The latter could have different categories for Jakarta news and other news. Seems like you are describing MovableType. Why then simply not install it? (and disable comments) Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Differences
Craig R. McClanahan wrote: The last really good (by some people's definition, I guess) flame war happened a couple of years ago ... and caused the subscription count on this list to drop from 4000 to 1500 in less than a month. I wonder what that was? :-) It is currently 718. Hope it will improve. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Slide 2.0 release: How to roll out the distributions
Oliver Zeigermann wrote: Hi again! The Slide community is just about to make a first beta release for a 2.0 version. As I have never done any releases on Apache Jakarta what is the normal distribution process? What are the steps taken once the Slide committers have decided the release actually should be rolled out? I found that these docs a very helpful: http://jakarta.apache.org/commons/releases/release.html http://wiki.cocoondev.org/Wiki.jsp?page=CocoonReleaseHowTo Do we need a vote going on in this list as well? Vote on slide-dev, and then CC vote resutls to Jakarta PMC for approval. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Differences
Ted Husted wrote: Perhaps once most of the Committers are on the PMC list, we can move the administrative nonsense there again, and let the General list be the General list again :) Looking forward to it. Do not remember when good flame worth reading last happened on this list. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] Apache Logging Services project
Ceki Gülcü wrote: Good morning to all, The log4j developers are pleased to announce that the Board of Directors of the Apache Software Foundation unanimously passed a resolution for the creation of the Apache Logging Services project. A copy of the resolution can be found at: http://nagoya.apache.org/wiki/apachewiki.cgi?LoggingApacheOrg/BoardResoluion The Logging Services project is intended to provide cross-language logging services for purposes of application debugging and auditing. I wonder, will it include only Log4J (and sister projects, as stated in resolution), or Commons Logging, Avalon LogKit will be invited too? Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] OS of choice
Henri Yandell wrote: A nice idea, and a simple way of adding in the votes, but with the issue that people without access to jakarta-site2 are unable to commit changes. If people want to send in patches, or just vote inline, then I'm sure people with access can add them. [I'm happy to do so for any I see]. Ok, here it is: * MS Windows XP - Vadim Gritsenko (came with company's notebook) * Linux - Vadim Gritsenko (desktop) Vadim Hen On Tue, 17 Dec 2002, Jon Scott Stevens wrote: I added a simple poll for Jakarta developers. http://jakarta.apache.org/site/os.html Please update the site with your preferences. -jon -- StudioZ.tv /\ Bar/Nightclub/Entertainment 314 11th Street @ Folsom /\ San Francisco http://studioz.tv/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: I win!
Jon Scott Stevens wrote: Yes, I win! http://cvs.apache.org/~rubys/committers.html Ok, that page makes me laugh. =) While in good mood, may be you could apply http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8467 ? Vadim -jon -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: I win!
Jon Scott Stevens wrote:
on 2002/12/3 12:20 PM, Vadim Gritsenko [EMAIL PROTECTED]
wrote:
Done. Attached to the bug report:
http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=4029
Done.
As an added bonus, I updated the build system to use more current standards.
ant docs fails with:
AnakiaTask is not present! Please check to make sure that
velocity.jar is in your classpath.
I guess something is wrong here (yes, I've checked out jakarta-site2).
Also, ant package-all fails because of:
Index: build.xml
===
RCS file: /home/cvspublic/jakarta-regexp/build/build.xml,v
retrieving revision 1.1
diff -u -r1.1 build.xml
--- build.xml3 Dec 2002 20:57:51 -1.1
+++ build.xml3 Dec 2002 21:18:51 -
@@ -141,7 +141,7 @@
exclude name=velocity.log/
/fileset
/copy
-copy file=../LICENSE tofile=${final.dir}/LICENSE/
+copy file=../LICENSE.txt tofile=${final.dir}/LICENSE.txt/
copy file=${build.dir}/${final.name}.jar
tofile=${final.dir}/${final.name}.jar/
/target
Thanks for applying the patch.
Vadim
-jon
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: More fun with unused/duplicate/unnecessary import statements
Tom Copeland wrote: Done: http://cvs.apache.org/~tcopeland/bad_imports_20_nov_02.htm How about adding xml-* projects into the list? Vadim Tom -Original Message- From: Lavandowska [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 20, 2002 3:26 PM To: Jakarta General List Subject: Re: More fun with unused/duplicate/unnecessary import statements This is really neat, could you add a percentage column though, just to save me from trying to do the math in my head? Thanks. --- Tom Copeland [EMAIL PROTECTED] wrote: i.e., imports from the same package. Numbers are about the same http://cvs.apache.org/~tcopeland/bad_imports_20_nov_02.htm -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
