to the old location, in case there are
other download pages / links lurking somewhere...
Hen
On Fri, Nov 11, 2011 at 4:08 PM, sebb seb...@gmail.com wrote:
At present, BSF, BCEL and JCS downloads still use /dist/jakarta/proj.
I've just started the process of moving JMeter files to the new JMeter
At present, BSF, BCEL and JCS downloads still use /dist/jakarta/proj.
I've just started the process of moving JMeter files to the new JMeter
TLP, so I thought I might as well do the same for the remaining
Jakarta downloads.
This is what I propose for the Commons moves:
- copy (cp -p) archives
Looks good, though I'm not sure the redirect on the mirror adds you
much value. I'd do it if it's standard practice, otherwise skip.
Hen
On Fri, Nov 11, 2011 at 4:08 PM, sebb seb...@gmail.com wrote:
At present, BSF, BCEL and JCS downloads still use /dist/jakarta/proj.
I've just started
Apache Commons have voted to accept BCEL and JCS. Accordingly, the SVN
repositories and websites for the two projects will be moved shortly.
I will reply this email when that is done.
-
To unsubscribe, e-mail: general-unsubscr
Vote result:
Jakarta has voted to move BCEL and JCS to Commons; there were no
objections to the moves.
dbrosius, asmuts, tv, seade - Please subscribe to dev@commons if
you're not already on it.
I will now start the acceptance vote over in Commons.
-Rahul
On Wed, Jun 22, 2011 at 10:38 PM
+1
Gary
On Jun 22, 2011, at 22:38, Rahul Akolkar rahul.akol...@gmail.com wrote:
After reasonable support to the idea on Jakarta and Commons lists,
this is a vote to move BCEL and JCS to Apache Commons.
As part of the move, I'll nominate any active committers for Commons
karma (so far
On 2011-06-23, Rahul Akolkar wrote:
After reasonable support to the idea on Jakarta and Commons lists,
this is a vote to move BCEL and JCS to Apache Commons.
+1
Stefan
-
To unsubscribe, e-mail: general-unsubscr
On 23 June 2011 03:38, Rahul Akolkar rahul.akol...@gmail.com wrote:
After reasonable support to the idea on Jakarta and Commons lists,
this is a vote to move BCEL and JCS to Apache Commons.
As part of the move, I'll nominate any active committers for Commons
karma (so far: dbrosius, asmuts
On Thu, Jun 23, 2011 at 7:09 AM, sebb seb...@gmail.com wrote:
On 23 June 2011 03:38, Rahul Akolkar rahul.akol...@gmail.com wrote:
After reasonable support to the idea on Jakarta and Commons lists,
this is a vote to move BCEL and JCS to Apache Commons.
As part of the move, I'll nominate any
After reasonable support to the idea on Jakarta and Commons lists,
this is a vote to move BCEL and JCS to Apache Commons.
As part of the move, I'll nominate any active committers for Commons
karma (so far: dbrosius, asmuts, tv -- anyone else, please ping this
thread).
Since neither may have
bringing this up on dev@commons.
-Rahul
On Mon, May 30, 2011 at 4:13 PM, Rahul Akolkar rahul.akol...@gmail.com
wrote:
This initial email is cross-posted, but lets keep the thread on dev@jakarta.
Jakarta is no longer a sustainable home for Java libraries like BCEL
and JCS. Commons, OTOH
@jakarta.
Jakarta is no longer a sustainable home for Java libraries like BCEL
and JCS. Commons, OTOH, is widely suited to such components and has a
much more active community. Therefore, I want us to explore the
possibility of moving BCEL and JCS to Commons. Assuming there is
interest in doing so
This initial email is cross-posted, but lets keep the thread on dev@jakarta.
Jakarta is no longer a sustainable home for Java libraries like BCEL
and JCS. Commons, OTOH, is widely suited to such components and has a
much more active community. Therefore, I want us to explore the
possibility
Le 30/05/2011 22:13, Rahul Akolkar a écrit :
This initial email is cross-posted, but lets keep the thread on dev@jakarta.
Jakarta is no longer a sustainable home for Java libraries like BCEL
and JCS. Commons, OTOH, is widely suited to such components and has a
much more active community
On 30 May 2011 21:24, Luc Maisonobe luc.maison...@free.fr wrote:
Le 30/05/2011 22:13, Rahul Akolkar a écrit :
This initial email is cross-posted, but lets keep the thread on
dev@jakarta.
Jakarta is no longer a sustainable home for Java libraries like BCEL
and JCS. Commons, OTOH, is widely
On 07/06/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:
On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
On 06/06/07, Roland Weber [EMAIL PROTECTED] wrote:
sebb wrote:
s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
No, CVS tag = SVN tag
No. SVN
Hi Thomas,
If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I understood the release-then-vote-policy
means
On 06/06/07, Roland Weber [EMAIL PROTECTED] wrote:
Hi Thomas,
If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what
sebb wrote:
s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
not trunk and from which you can get a named historic version
(=revision?) of what used to be in trunk :-)
It's called level in CMVC, and I just don't want to spend
my time on learning a separate
On 06/06/07, Roland Weber [EMAIL PROTECTED] wrote:
sebb wrote:
s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
No, CVS tag = SVN tag
not trunk and from which you can get a named historic version
(=revision?) of what used to be in trunk :-)
In SVN, there
Hi Sebastian,
So a release can be developed in a branch or the trunk; before the
release is finally built the current files should be copied to a
subdirectory of tags.
The tags subdirectory should not be updated once created.
The branch was the correct term. You copy trunk into a branch
in
Jakarta JCS 1.3 is now available. JCS is a distributed caching system
written in Java. This release is the first official release of JCS under
the Jakarta Project.
JCS 1.3 has been uploaded to the usual places and is/will soon be
available in either binary or source form from the following
On 06/06/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
Jakarta JCS 1.3 is now available. JCS is a distributed caching system
written in Java. This release is the first official release of JCS under
the Jakarta Project.
Probably a good idea to send the e-mail to:
[EMAIL PROTECTED]
as well
folks ([EMAIL PROTECTED]).
Best regards
Henning
On Wed, 2007-06-06 at 20:26 +0200, Thomas Vandahl wrote:
Jakarta JCS 1.3 is now available. JCS is a distributed caching system
written in Java. This release is the first official release of JCS under
the Jakarta Project
, Roland Weber [EMAIL PROTECTED] wrote:
Hi Thomas,
If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I
On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
On 06/06/07, Roland Weber [EMAIL PROTECTED] wrote:
sebb wrote:
s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
No, CVS tag = SVN tag
No. SVN tag == SVN branch == shallow directory copy.
There is just a
On 04/06/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Sorry for the delay in responding.
The NOTICE file is much clearer, and the Xerox license is identified,
so I am withdrawing my -1.
When the rules have been clarified, the next release can implement any
changes if necessary.
Could you create an example on how you would consider the structure and
content as acceptable so that we can understand what you want to have?
Thanks
Henning
sebb schrieb:
On 04/06/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Sorry for the delay in
On 05/06/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:
Could you create an example on how you would consider the structure and
content as acceptable so that we can understand what you want to have?
Thanks
Henning
I thought I already had done so:
On 27/05/07, sebb
Thomas Vandahl wrote:
Voting has closed. Here are the results:
+1 votes:
Hanson Char [EMAIL PROTECTED]
Thomas Vandahl [EMAIL PROTECTED]
* Henning Schmiedehausen [EMAIL PROTECTED]
* Aaron Smuts [EMAIL PROTECTED]
* Scott Eade [EMAIL PROTECTED]
* Rony G. Flatscher [EMAIL PROTECTED]
0
If you vote again your vote is binding too :)
Mvgr,
Martin
Thomas Vandahl wrote:
Hi Sebastian,
sebb wrote:
However:
http://apache.org/dev/apply-license.html
says much the same, and seems to be policy.
As you can see from the SVN tag JCS_1_3 and the artifacts at my site,
your
On 04/06/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
Hi Sebastian,
Hi
sebb wrote:
However:
http://apache.org/dev/apply-license.html
says much the same, and seems to be policy.
As you can see from the SVN tag JCS_1_3 and the artifacts at my site,
your concerns have been addressed and
sebb wrote:
Sorry for the delay in responding.
The NOTICE file is much clearer, and the Xerox license is identified,
so I am withdrawing my -1.
When the rules have been clarified, the next release can implement any
changes if necessary.
Sebastian
Thanks, I will clarify the result now,
Martin van den Bemt wrote:
If you vote again your vote is binding too :)
Next time. Thanks again for voting me in.
Bye, Thomas.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Thomas,
I could not find any information about whether Rony Flatscher is a
member of the PMC
In the committers-only SVN module is a file board/committee-info.txt
which lists the PMCs of all Apache projects. It's (supposed to be ;-)
the authoritative source. Rony Flatscher is listed there as
on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I understood the release-then-vote-policy
means. I have committed the latest changes and moved the tag, however.
If Rony is a PMC member we have a result of 3 +1 votes, which should be
sufficient. However its up
changes his vote. As by his last mail on the topic, the content in
SVN did not get fixed. If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN
in
SVN did not get fixed. If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I understood the release-then-vote
commit those changes to SVN and give Sebastian some time to
change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I understood the release-then-vote-policy
means. I have committed the latest changes and moved the tag, however
Thomas Vandahl wrote:
Actually, it's more than that. But so be it. I will update the files on
my site and kindly ask for a re-vote.
Done. I chose the separate LICENSE file. The maven2-POM is also part of
the distribution.
Bye, Thomas.
Thomas Vandahl wrote:
Thomas Vandahl wrote:
Actually, it's more than that. But so be it. I will update the files on
my site and kindly ask for a re-vote.
Done. I chose the separate LICENSE file. The maven2-POM is also part of
the distribution.
The maven2 pom is what I was holding
sebb wrote:
I find the current NOTICE rather misleading - it looks as though the
whole of JCS is licensed under a Xerox licence.
I think it's therefore important to fix this.
From re-reading the NOTICE file, I agree with you. My proposal to solve
this is the following:
---8---
Apache
On 30/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
I find the current NOTICE rather misleading - it looks as though the
whole of JCS is licensed under a Xerox licence.
I think it's therefore important to fix this.
From re-reading the NOTICE file, I agree with you. My proposal
sebb wrote:
The NOTICE file is not supposed to contain any licenses.
I beg to differ, but I will not go into this again.
I suggest you remove the Xerox license header from it, and add it to
the LICENSE file, with the appropriate introduction.
The LICENSE.txt file is supposed to contain the ASL
On 30/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
The NOTICE file is not supposed to contain any licenses.
I beg to differ, but I will not go into this again.
I suggest you remove the Xerox license header from it, and add it to
the LICENSE file, with the appropriate
On Wed, 2007-05-30 at 19:00 +0100, sebb wrote:
The NOTICE file is not supposed to contain any licenses.
What makes you think so? I am still a bit stumped that you so strongly
insist on this. Is there any reference (besides the cited httpd project)
to that?
Best regards
On 5/30/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:
On Wed, 2007-05-30 at 19:00 +0100, sebb wrote:
The NOTICE file is not supposed to contain any licenses.
What makes you think so? I am still a bit stumped that you so strongly
insist on this. Is there any reference (besides the cited
Yep, I know this.
Status
Version: 0.52
Effective Date. N/A (proposed)
== non binding.
If it were in effect, then yes, the paragraph
--- cut ---
* Reciprocity
Required by some Components: Some included third-party works are
licensed under terms that require distribution of
On 30/05/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:
Yep, I know this.
Status
Version: 0.52
Effective Date. N/A (proposed)
== non binding.
However:
http://apache.org/dev/apply-license.html
says much the same, and seems to be policy.
Full license text should go in LICENSE and attributions and notices in NOTICE..
Mvgr,
Martin
Henning Schmiedehausen wrote:
Well, I understand it differently and Thomas (probably looking at other
projects) did this too:
- LICENSE.txt contains the terms under which the software is licensed.
Hi,
uhm, this is as ambiguous as before. Do you consider third-party license
a notice (the foo library is distributed under the foo license as shown
here) or a license in its own right and you would put in into LICENSE.
According to http://apache.org/dev/apply-license.html#new, the LICENSE
file
to http://apache.org/dev/apply-license.html#new, the LICENSE
file is a copy of http://www.apache.org/licenses/LICENSE-2.0.txt
And is that *really* important?
I find the current NOTICE rather misleading - it looks as though the
whole of JCS is licensed under a Xerox licence.
I think it's therefore
Well, I understand it differently and Thomas (probably looking at other
projects) did this too:
- LICENSE.txt contains the terms under which the software is licensed.
This is Apache License 2.0
- NOTICE contains attributions to included code and the licenses that
it is included under. Some
sebb wrote:
I don't think so. The NOTICE is not supposed to contain the license.
It doesn't. It contains what I understand as license header of that
one Xerox file and the associated copyright notice.
Bye, Thomas.
-
To
discussion on the JCS developer list, the first official
release of JCS (version 1.3) after leaving the Turbine project is ready
to vote on.
You can find the created artifacts here:
site: http://people.apache.org/~tv/jcs/
jars: http://people.apache.org/~tv/jcs/jar/
dist: http://people.apache.org/~tv
On 27/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
I don't think so. The NOTICE is not supposed to contain the license.
It doesn't. It contains what I understand as license header of that
one Xerox file and the associated copyright notice.
Sorry to keep going on about this,
The license under which the code gets licensed to our end users is in
LICENSE.txt.
Copyright notices and optional third-party licenses under which the code
got licensed to us is in NOTICE.
Thomas did the right thing.
Best regards
Henning
sebb schrieb:
On 27/05/07,
On 27/05/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote:
The license under which the code gets licensed to our end users is in
LICENSE.txt.
Copyright notices and optional third-party licenses under which the code
got licensed to us is in NOTICE.
Are you sure?
That does not seem to agree
Hi folks,
After much discussion on the JCS developer list, the first official
release of JCS (version 1.3) after leaving the Turbine project is ready
to vote on.
You can find the created artifacts here:
site: http://people.apache.org/~tv/jcs/
jars: http://people.apache.org/~tv/jcs/jar/
dist
Thomas Vandahl wrote:
Now, shall we release JCS as it is published there?
[X] +1 Yes, JCS 1.3 should be released
[ ] 0 I do not care
[ ] -1 No (give reasons)
Bye, Thomas.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could not find it in SVN.
Sourcefiles:
There should probably be AL2.0 headers
sebb wrote:
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could not find it in SVN.
Sourcefiles:
There should probably
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could
sebb wrote:
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Project Team: both tv and jvanzyl are committers
Actually my contributions are very small, so I'm fine with the
contributor status.
But you _are_ still a committer...
Surely it is up to Thomas to decide how he
sebb wrote:
But you _are_ still a committer...
Yes, but then, everybody else in Jakarta is also potentially a committer
for JCS and we would not want to list them all.
By, Thomas.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On 26/05/07, Scott Eade [EMAIL PROTECTED] wrote:
sebb wrote:
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Project Team: both tv and jvanzyl are committers
Actually my contributions are very small, so I'm fine with the
contributor status.
But you _are_ still a
sebb wrote:
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could not find it in SVN.
Sourcefiles:
There should probably
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote:
sebb wrote:
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could
Can someone please give the user asmuts developer
rights to the JCS project on JIRA.
Cheers,
Aaron
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Done. jakarta-admin and jakarta-developer groups added.
Hen
On Thu, 6 Jul 2006, Aaron Smuts wrote:
Can someone please give the user asmuts developer
rights to the JCS project on JIRA.
Cheers,
Aaron
-
To unsubscribe, e
Date: 2005-03-12T09:11:37
Editor: HenriYandell
Wiki: Jakarta Wiki
Page: JCS promotion to SLP
URL: http://wiki.apache.org/jakarta/JCS promotion to SLP
Mail list change done; thanks Roy.
Change Log
Date: 2005-03-01T21:05:57
Editor: HenriYandell
Wiki: Jakarta Wiki
Page: JCS promotion to SLP
URL: http://wiki.apache.org/jakarta/JCS promotion to SLP
no comment
Change Log:
--
@@ -9,7 +9,7 @@
Either
Date: 2005-02-21T19:30:17
Editor: HenriYandell
Wiki: Jakarta Wiki
Page: JCS promotion to SLP
URL: http://wiki.apache.org/jakarta/JCS promotion to SLP
Jira issue entered for mailing list change.
Change Log
Date: 2005-02-14T14:23:53
Editor: HenriYandell
Wiki: Jakarta Wiki
Page: JCS promotion to SLP
URL: http://wiki.apache.org/jakarta/JCS promotion to SLP
JCS plans
New Page:
= Promotion of JCS =
== Bugzilla change ==
Looks to be in Scarab. Are we migrating out of this? Does
Henning Schmiedehausen wrote:
Hi,
the subject is already the question: Is anyone moderating
turbine-jcs-dev and turbine-jcs-user @ jakarta?
The moderator for both lists is quintonm at apache.org
See docs/resources.txt in the committers module for a way to
get this information yourself.
Christian
moderating
turbine-jcs-dev and turbine-jcs-user @ jakarta?
The moderator for both lists is quintonm at apache.org
See docs/resources.txt in the committers module for a way to
get this information yourself.
Christian
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
Done.
--- Noel
-Original Message-
From: Henning Schmiedehausen [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 12, 2004 8:44
To: Christian Geisert
Cc: Jakarta General Mailinglist; Apache Infrastructure
Subject: Re: Who is moderating Jakarta Turbine JCS mailing lists?
Hi
Hi,
the subject is already the question: Is anyone moderating
turbine-jcs-dev and turbine-jcs-user @ jakarta?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de
problem as long as there are
developers maintaining the code
IMHO
1 the pmc is unable to demonstrate oversight.
2 there are a large number of pmc people who believe that umbrella
sub-projects don't work.
as far as i was concerned the consensus was that whatever the JCS team
wanted was cool
that you'd be an ideal candidate :)
Hi,
thanks. :-)
I'm willing to subscribe to JCS for watching the developers there and
help them getting out a release. We should try to get genuine
interest
from their side to push JCS ahead.
it'll either have to go forward or go back. the pmc can't really
allow
On 12 Dec 2003, at 09:28, Henning Schmiedehausen wrote:
On Thu, 2003-12-11 at 21:07, robert burrell donkin wrote:
hi henning
you don't need to be a committer to act as a mentor. from what i've
heard, i'd say that you'd be an ideal candidate :)
Hi,
thanks. :-)
I'm willing to subscribe to JCS
. :-)
I'm willing to subscribe to JCS for watching the developers there and
help them getting out a release. We should try to get genuine interest
from their side to push JCS ahead.
it'll either have to go forward or go back. the pmc can't really allow
it to drift any more. if there isn't any activity
On Thu, 2003-12-11 at 21:07, robert burrell donkin wrote:
hi henning
you don't need to be a committer to act as a mentor. from what i've
heard, i'd say that you'd be an ideal candidate :)
Hi,
thanks. :-)
I'm willing to subscribe to JCS for watching the developers there and
help them
hi henning
you don't need to be a committer to act as a mentor. from what i've
heard, i'd say that you'd be an ideal candidate :)
we need more eyes on more lists. what worries folks (including myself)
is that there aren't really very many pmc eyes on the JCS list. this
means that there's
I'd do it, but I'm not personally involved in JCS. IMHO Martin Poeschl
(who is a Turbineer _and_ works with JCS) would be perfect but I know
that he will be on holidays for a longer time (either already is or will
be soon. Martin?).
Martin did the Turbine 2.2 release and most of the Torque
I'll be available in January to get started. Let me know what is
involved in a release.
-Original Message-
From: Henning Schmiedehausen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 2:51 AM
To: Jakarta General List
Subject: Re: [POLL] Future Of Turbine-JCS
I'd do
On 8 Dec 2003, at 11:10, Christopher Lenz wrote:
Am 08.12.2003 um 09:03 schrieb Stefan Bodewig:
Can anybody with a better memory for commons than I have recap why the
httpclient traffic list has been split off? Did the httpclient
developers want a list of their own or have the developers for the
, Aaron Smuts wrote:
Sounds good. Less disruption on the way to a release would be best.
Aaron
-Original Message-
From: Henning Schmiedehausen [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2003 3:22 AM
To: Jakarta General List
Subject: Re: [POLL] Future Of Turbine-JCS
IMHO too complex
On 8 Dec 2003, at 21:07, Costin Manolache wrote:
Henri Yandell wrote:
On Wed, 2 Oct 2002, Costin Manolache wrote:
Or even better - since jakarta has a single PMC, it could also have
a single
list of committers ( most of them in the single PMC ).
Each PMC member can vote about any jakarta issue
On 8 Dec 2003, at 04:20, Phil Steitz wrote:
snip
Then maybe
instead of breaking it on code-base, we could break it on concept:
jakarta-bugs
jakarta-announce
jakarta-dev
jakarta-pmc
jakarta-ideas
jakarta-site
or something. I'm assuming it'll be too noisy, but it is a logical
question to ask based
35
Tapestry 110
Tomcat 982
Turbine 271
Turbine-JCS 10
Velocity 244
I think there are more lists than that.
(*) using MARC as Gump is not listed in eyebrowse.
OK, the total is 6953, more than three times the traffic
IMHO too complex. If there is already a JCS list (is there? As you can
see, I'm a Turbine committer but I have zero overlap with JCS. In fact I
didn't even know that this is a turbine sub-sub project for quite some
time ;-) ), let's keep it. We want to build community? Let's _not_ fold
Am 08.12.2003 um 09:03 schrieb Stefan Bodewig:
Can anybody with a better memory for commons than I have recap why the
httpclient traffic list has been split off? Did the httpclient
developers want a list of their own or have the developers for the
other commons components been overwhelmed by
Sounds good. Less disruption on the way to a release would be best.
Aaron
-Original Message-
From: Henning Schmiedehausen [mailto:[EMAIL PROTECTED]
Sent: Monday, December 08, 2003 3:22 AM
To: Jakarta General List
Subject: Re: [POLL] Future Of Turbine-JCS
IMHO too complex
promotion to a full sub-project.
+1 but direct drop only if the move to the commons is accompanied by a
release (1.0 or 0.something, I don't care).
the way that i'd like to see a potential drop working is by folding the
jcs user and development lists into the commons lists first. this would
allow
There is also the problem of external dependencies ( if any ). At
least
some
of the people on commons preffer commons as more-or-less standalone
tools,
that don't require a lot of 'framework'. I don't know JCS, but if it
can
be used as a standalone library - it would be great to get
has more
than one repository, karma for a repository may be given out only on
request) and one development mailing list. so i'd like to prohibit any
sub-sub-projects like jakarta-turbine-JCS.
- robert
-
To unsubscribe, e-mail
for reasons of security, if a sub-project has more
than one repository, karma for a repository may be given out only on
request) and one development mailing list. so i'd like to prohibit any
sub-sub-projects like jakarta-turbine-JCS.
Or even better - since jakarta has a single PMC, it could
On Wed, 2 Oct 2002, Costin Manolache wrote:
Or even better - since jakarta has a single PMC, it could also have a single
list of committers ( most of them in the single PMC ).
Each PMC member can vote about any jakarta issue - including releases of
each sub-project, etc. If the distinction
Henri Yandell wrote:
On Wed, 2 Oct 2002, Costin Manolache wrote:
Or even better - since jakarta has a single PMC, it could also have a single
list of committers ( most of them in the single PMC ).
Each PMC member can vote about any jakarta issue - including releases of
each sub-project, etc. If
1 - 100 of 139 matches
Mail list logo
