In message <[EMAIL PROTECTED]
.com.au>, [EMAIL PROTECTED] writes:
>> I think something folks are missing is that if J-C moves to A-C, then
>> all J-C committers become A-C PMC Members and can change the rules that
>> don't make sense once A-C has incorporated J-C. For example, and it's
>
>I'm fai
On Tue, Dec 23, 2003 at 09:18:43AM -, Stephen Colebourne wrote:
>...
> I'll say again - the Board could avoid this damage by
> choosing to ACT rather than REACT.
I don't think that I can stress this enough: the Board is too far removed
to "ACT" properly. We can certainly take actions, but it w
> I know exactly how you feel. The basic problem is that Jakarta, and
> Jakarta-Commons, are now incapable of taking any decisions on contentious
> issues. They are too large - too large for the discussion, too many
mails,
> too many personalities and and inability to hold a vote.
I think that
I know exactly how you feel. The basic problem is that Jakarta, and
Jakarta-Commons, are now incapable of taking any decisions on contentious
issues. They are too large - too large for the discussion, too many mails,
too many personalities and and inability to hold a vote.
IMHO, the only hope is f
"Daniel F. Savarese" <[EMAIL PROTECTED]> wrote on 23/12/2003 11:09:24 AM:
>
> In message
<[EMAIL PROTECTED]>, Ga
> ry Gregory writes:
> >Well, now I am switched around to a "-1" as well :-(
> >
> >> From: Rodney Waldhoff
> >> 1) a-c organization: I think the organizational structure of
> >> apa
Daniel F. Savarese wrote:
In message <[EMAIL PROTECTED]>, Ga
ry Gregory writes:
Well, now I am switched around to a "-1" as well :-(
From: Rodney Waldhoff
1) a-c organization: I think the organizational structure of
apache-commons (one list per component, balkanized karma rights, etc.) is
bad fo
--On Tuesday, December 23, 2003 11:16 AM +1100 [EMAIL PROTECTED] wrote:
Is it not possible to run CVS without shell accounts? Doesn't sourceforge
work this way?
SourceForge provides restricted shell accounts to people with commit access on
a 'dedicated' CVS box that does nothing else. And, they
> -Original Message-
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 22, 2003 14:47
> To: Jakarta Commons Developers List
> Subject: RE: [codec] [proposal] Moving To Apache Commons
>
> Alright, all around - moving to Subversion is ou
day, December 22, 2003 10:33
> To: Jakarta Commons Developers List
> Subject: Re: [codec] [proposal] Moving To Apache Commons
>
> As a contributor to and user of commons-codec, I'm voting -1.
>
> My reasons, as I've described in more detail on the apache-commons list
&g
As a contributor to and user of commons-codec, I'm voting -1.
My reasons, as I've described in more detail on the apache-commons list
and probably others, are:
1) a-c organization: I think the organizational structure of
apache-commons (one list per component, balkanized karma rights, etc.) is
ba
bclipse.tigris.org/. Bummer they do not support the current
3.0.m
> version.
>
> Gary
>
> > -Original Message-
> > From: Gary Gregory [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 19, 2003 19:15
> > To: 'Jakarta Commons Deve
On Sat, Dec 20, 2003 at 11:21:39AM -0500, Henri Yandell wrote:
> On Fri, 19 Dec 2003, __matthewHawthorne wrote:
>...
> > I was recently forced to switch to Subversion at work. I haven't yet
> > tried to install a server, but the client and client-ssl were pretty
> > simple -- I just installed the
David Graham wrote:
I agree with everything Martin said. I often read codec messages and if
it wasn't hosted in Jakarta commons I wouldn't have worked on the
DigestUtils code. Granted, that code is a very small piece of codec but I
think it says a lot about the community that people unrelated to
On Dec 20, 2003, at 2:47 AM, Stephen Colebourne wrote:
To go to A-C means to have no supporting community other than codec
developers.
Will you ask for your own mailing list?
I would not.
or be on the same list as Serf?
Or be here on the same list as jxpath, digester, io, etc? I do not see
the d
On Dec 20, 2003, at 6:33 AM, Dirk Verbeeck wrote:
-0, unless there is a real plan to port codec to another language (in
the very near future), I would ask you to remain at jakarta-commons.
Testing the waters of Apache Commons is a good idea but the real test
is: Can Apache commons build a cross
I agree with everything Martin said. I often read codec messages and if
it wasn't hosted in Jakarta commons I wouldn't have worked on the
DigestUtils code. Granted, that code is a very small piece of codec but I
think it says a lot about the community that people unrelated to a
particular project
On Sat, 20 Dec 2003, Tim O'Brien wrote:
> Enough people profess interest in using this product, but only a few
> committers (myself and Gary) actually go about the business of
> contributing. Believe it or not, I think that components get lost in
> the signal to noise ratio of the Jakarta Commons
On Fri, 19 Dec 2003, __matthewHawthorne wrote:
> Henri Yandell wrote:
> >>#1. Commons Codec will be hosted on Subversion
> >
> > -1
> >
> > I've not been able to install the server on Linux, or the client-ssl on a
> > Mac with ease. Partly this is my own damn stupidity I suspect, but I'm
> > co
-0, unless there is a real plan to port codec to another language (in
the very near future), I would ask you to remain at jakarta-commons.
Testing the waters of Apache Commons is a good idea but the real test
is: Can Apache commons build a cross-language community?
Testing Subversion & Jira sho
From: "Tim O'Brien" <[EMAIL PROTECTED]>
> Stephen Colebourne wrote:
> >Will you ask for your own mailing list?
> I don't see why not. I would prefer this for a few reasons. First, I
> think that the shared mailing list is distracting from the focus needed
> to produce quality software. Second, I
Stephen Colebourne wrote:
I understand the fustrations of J-C that might cause this proposal. I do
fear the result of this change though. However, I believe that an individual
component has the right to decide its own fate within J-C. So all I can do
is indicate my -0 to the change at the moment a
Henri Yandell wrote:
On Fri, 19 Dec 2003, Tim O'Brien wrote:
To this end, I propose that Jakarta Commons Codec be officially
transformed into Apache Commons Codec.
-0, in that I'm in favour of trying to push for an entire, or large, J-C
to A-C-ish move. We're pretty soon going to have the
I understand the fustrations of J-C that might cause this proposal. I do
fear the result of this change though. However, I believe that an individual
component has the right to decide its own fate within J-C. So all I can do
is indicate my -0 to the change at the moment as I don't think alternative
Henri Yandell wrote:
#1. Commons Codec will be hosted on Subversion
>
-1
I've not been able to install the server on Linux, or the client-ssl on a
Mac with ease. Partly this is my own damn stupidity I suspect, but I'm
competent on both platforms and would expect it to work pretty easily.
I do want
On Fri, 19 Dec 2003, Tim O'Brien wrote:
> To this end, I propose that Jakarta Commons Codec be officially
> transformed into Apache Commons Codec.
-0, in that I'm in favour of trying to push for an entire, or large, J-C
to A-C-ish move. We're pretty soon going to have the kind of situation in
w
d in a great IDE.
So, take all of this with a grain of salt from some who just likes eclipse
too much :-)
Gary
> -Original Message-
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 19, 2003 19:47
> To: Jakarta Commons Developers List
> Subj
Gary Gregory wrote:
#1. Commons Codec will be hosted on Subversion
-1, unless I can use Eclipse to access the repos. Can Subversion work in
some kind of CVS compatibility mode? Using a CLI is such a pain.
When did ASF development become tied to Eclipse functionality? I've
noticed this ov
> > #1. Commons Codec will be hosted on Subversion
> -1, unless I can use Eclipse to access the repos. Can Subversion work in
> some kind of CVS compatibility mode? Using a CLI is such a pain.
> Ah I see "Actually subclipse can be used with Eclipse 2.1.0 and 2.1.1."
> on http://subclipse.tigris.o
On Dec 19, 2003, at 6:56 PM, Tim O'Brien wrote:
Codec, a small - probably the smallest - piece of code in
Jakarta-land. Is well suited for inclusion in Apache Commons. I
propose that Codec be used as a guinea pig of sorts to test the waters
of Apache Commons. It is not language specific, and
9:15
> To: 'Jakarta Commons Developers List'
> Subject: RE: [codec] [proposal] Moving To Apache Commons
>
> > -Original Message-
> > From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 19, 2003 18:56
> > To: [EMAIL
> -Original Message-
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 19, 2003 18:56
> To: [EMAIL PROTECTED]
> Subject: [codec] [proposal] Moving To Apache Commons
>
> Codec, a small - probably the smallest - piece of code in Jakarta-
Codec, a small - probably the smallest - piece of code in Jakarta-land.
Is well suited for inclusion in Apache Commons. I propose that Codec be
used as a guinea pig of sorts to test the waters of Apache Commons. It
is not language specific, and it is something that could be excised from
the
32 matches
Mail list logo
