> -Original Message-
> From: Benedikt Ritter [mailto:brit...@apache.org]
> Sent: Friday, November 29, 2013 5:37
> To: Commons Developers List
> Subject: Re: [CHALLENGE] Move All of Commons to the Dormant
>
[snip]
>
> Well, it's end of November now. So it&#
er
> Date:11/29/2013 05:36 (GMT-05:00)
> To: Commons Developers List
> Subject: Re: [CHALLENGE] Move All of Commons to the Dormant
>
> 2013/10/15 Henri Yandell
>
>> I contend that all of the Commons components are inactive and should move
>> to the Attic/Dormant
I have partial interest in daemon and net because I use these at work or other
project.
Gary
Original message
From: Benedikt Ritter
Date:11/29/2013 05:36 (GMT-05:00)
To: Commons Developers List
Subject: Re: [CHALLENGE] Move All of Commons to the Dormant
2013/10/15
2013/10/15 Henri Yandell
> I contend that all of the Commons components are inactive and should move
> to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
> present a dormancy challenge at any time, I'm challenging all of Commons
> Proper.
>
> I've made a file in SVN:
>
>
On 19 Oct 2013, at 17:22, Henri Yandell wrote:
On Sat, Oct 19, 2013 at 7:25 AM, Christian Grobmeier
wrote:
Being in the attic is NOT a permanent thing. Get active developers,
leave
the attic. If a project doesn't make any sense, stay in the attic.
We are having an attic but called it "dormant"
On Sat, Oct 19, 2013 at 7:25 AM, Christian Grobmeier wrote:
> On 18 Oct 2013, at 9:24, Jörg Schaible wrote:
>
> Hi Christian,
>>
>> Christian Grobmeier wrote:
>>
>> On 17 Oct 2013, at 18:12, Paul Benedict wrote:
>>>
>>> I am glad to hear being "dormant" is not the same thing as being in
th
On 18 Oct 2013, at 9:24, Jörg Schaible wrote:
Hi Christian,
Christian Grobmeier wrote:
On 17 Oct 2013, at 18:12, Paul Benedict wrote:
I am glad to hear being "dormant" is not the same thing as being in
the
"attic"
Why?
Because "attic" means more or less that we not even intend to work o
I agree. The only reason [imaging] has been "dormant" for so long is
that I am busy making large changes that have taken many months to
write, so it's not really that dormant after all.
I understand the desire to do something about the current state of
Commons, but please don't make things harder
Hi Christian,
Christian Grobmeier wrote:
> On 17 Oct 2013, at 18:12, Paul Benedict wrote:
>
>> I am glad to hear being "dormant" is not the same thing as being in
>> the
>> "attic"
>
> Why?
Because "attic" means more or less that we not even intend to work on this
component anymore. E.g. we d
On 17 Oct 2013, at 18:12, Paul Benedict wrote:
I am glad to hear being "dormant" is not the same thing as being in
the
"attic"
Why?
I also prefer that being "dormant" doesn't cause a SVN/GitHub folder
move.
Why? It's pretty easy actually.
The projects should just live where they are, eve
On 17 Oct 2013, at 18:03, Phil Steitz wrote:
> On 10/17/13 5:52 AM, Christian Grobmeier wrote:
>> On 17 Oct 2013, at 2:39, Henri Yandell wrote:
>>
>>> On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
>>>
On 16 October 2013 12:25, Christian Grobmeier
wrote:
> If nobody is willing to put
I am glad to hear being "dormant" is not the same thing as being in the
"attic"
I also prefer that being "dormant" doesn't cause a SVN/GitHub folder move.
The projects should just live where they are, even when sleeping. Only move
them if they actually go into an "attic"
On Thu, Oct 17, 2013 at
On 10/17/13 5:52 AM, Christian Grobmeier wrote:
> On 17 Oct 2013, at 2:39, Henri Yandell wrote:
>
>> On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
>>
>>> On 16 October 2013 12:25, Christian Grobmeier
>>> wrote:
If nobody is willing to put a component to "dormant" state,
then the
lab
On 17 Oct 2013, at 2:39, Henri Yandell wrote:
On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
On 16 October 2013 12:25, Christian Grobmeier
wrote:
If nobody is willing to put a component to "dormant" state, then the
label doesn't make any sense. I would vote to remove the dormant
state in
ge
On Wed, Oct 16, 2013 at 11:14 PM, Jörg Schaible wrote:
> Henri Yandell wrote:
>
> > My first thought was "We should delete that page". :)
>
> Done at least for "Release In Progress", last change 4 years ago. Funny
> enough it had a line for Collections 4.0 ;-)
>
> There's a lot of obsolete data i
Henri Yandell wrote:
> My first thought was "We should delete that page". :)
Done at least for "Release In Progress", last change 4 years ago. Funny
enough it had a line for Collections 4.0 ;-)
There's a lot of obsolete data in the wiki.
- Jörg
---
On Tue, Oct 15, 2013 at 12:33 AM, Emmanuel Bourg wrote:
> Le 15/10/2013 09:13, Henri Yandell a écrit :
>
> > Related; here's the output of a 2006 script I've dusted off to show the
> > number of commits and from who to each component in 2013:
> >
> > http://people.apache.org/~bayard/ActivityRepor
On Wed, Oct 16, 2013 at 4:59 PM, sebb wrote:
> On 16 October 2013 12:25, Christian Grobmeier wrote:
> > If nobody is willing to put a component to "dormant" state, then the
> > label doesn't make any sense. I would vote to remove the dormant state in
> > general.
> > If we don't have any need of
On 16 October 2013 12:25, Christian Grobmeier wrote:
> If nobody is willing to put a component to "dormant" state, then the
> label doesn't make any sense. I would vote to remove the dormant state in
> general.
> If we don't have any need of a specific component we can put it to
> attic.apache.org
My first thought was "We should delete that page". :)
On Wed, Oct 16, 2013 at 4:26 AM, Ted Dunning wrote:
> Careful there. Hen might suggest making that list dormant.
>
> Sent from my iPhone
>
> On Oct 16, 2013, at 0:38, Jörg Schaible wrote:
>
> > BTW: We have already a "challenge" result, i
Ted Dunning wrote:
> Careful there. Hen might suggest making that list dormant.
Why tyke care, it just reflect the current state then ;-)
>
> Sent from my iPhone
>
> On Oct 16, 2013, at 0:38, Jörg Schaible wrote:
>
>> BTW: We have already a "challenge" result, it's just terribly out of
>> d
Careful there. Hen might suggest making that list dormant.
Sent from my iPhone
On Oct 16, 2013, at 0:38, Jörg Schaible wrote:
> BTW: We have already a "challenge" result, it's just terribly out of date:
> https://wiki.apache.org/commons/CommonsPeople
If nobody is willing to put a component to "dormant" state, then the
label doesn't make any sense. I would vote to remove the dormant state
in general.
If we don't have any need of a specific component we can put it to
attic.apache.org too.
No need to duplicate things.
If we don't have a "dorm
Hi Hen,
Henri Yandell wrote:
> I contend that all of the Commons components are inactive and should move
> to the Attic/Dormant. In line with Phil's recent suggestion that anyone
> can present a dormancy challenge at any time, I'm challenging all of
> Commons Proper.
>
> I've made a file in SVN:
Ralph Goers wrote:
>
> On Oct 15, 2013, at 8:50 AM, Gary Gregory wrote:
>
>> On Tue, Oct 15, 2013 at 11:30 AM, Ralph Goers
>> wrote:
>>> Personally, I like the idea of having a last release date AND a list of
>>> people who are active in the project. The only problem is that people
>>> who go
On Oct 15, 2013, at 8:50 AM, Gary Gregory wrote:
> On Tue, Oct 15, 2013 at 11:30 AM, Ralph Goers
> wrote:
>> Personally, I like the idea of having a last release date AND a list of
>> people who are active in the project. The only problem is that people who go
>> inactive rarely remove themse
On 10/15/13 12:13 PM, Roger L. Whitcomb wrote:
> I'd like to put my name down as interested (but not active) for lang,
> beanutils, collections, launcher, and exec; and active (meaning we're
> using them and have patches, suggestions in the wings) for logging, vfs
> and csv.
Added to logging, csv,
I'd like to put my name down as interested (but not active) for lang,
beanutils, collections, launcher, and exec; and active (meaning we're
using them and have patches, suggestions in the wings) for logging, vfs
and csv.
BTW, I've added a VFS-compatible component to Apache Pivot and we've
discusse
On 10/15/13 9:50 AM, Matt Benson wrote:
> AFAIK Bernd is not an ASF committer, but a very motivated contributor to
> VFS.
OK, sorry. The more the merrier!
Done.
Phil
>
> Matt
>
>
> On Tue, Oct 15, 2013 at 11:26 AM, Phil Steitz wrote:
>
>> On 10/14/13 11:27 PM, Bernd Eckenfels wrote:
>>> I am
AFAIK Bernd is not an ASF committer, but a very motivated contributor to
VFS.
Matt
On Tue, Oct 15, 2013 at 11:26 AM, Phil Steitz wrote:
> On 10/14/13 11:27 PM, Bernd Eckenfels wrote:
> > I am not happy about the challange, but if you have the file open can
> you please add me as active contrib
On 10/14/13 11:27 PM, Bernd Eckenfels wrote:
> I am not happy about the challange, but if you have the file open can you
> please add me as active contributor to VFS2? Thanks.
What is your ASF username?
Phil
>
>> Am 15.10.2013 um 06:14 schrieb Phil Steitz :
>>
>>> On 10/14/13 8:55 PM, Henri Yand
That would be a no. :)
Matt
On Tue, Oct 15, 2013 at 11:06 AM, Honton, Charles wrote:
> This automation, along with other infrastructure to attract new developers
> already exists in several commercial source forges. Do Apache policies
> allow development to be hosted at GitHub or the like?
>
This automation, along with other infrastructure to attract new developers
already exists in several commercial source forges. Do Apache policies
allow development to be hosted at GitHub or the like?
Regards,
chas
On 10/15/13 8:50 AM, "Gary Gregory" wrote:
>On Tue, Oct 15, 2013 at 11:30 AM, R
On Tue, Oct 15, 2013 at 11:30 AM, Ralph Goers
wrote:
> Personally, I like the idea of having a last release date AND a list of
> people who are active in the project. The only problem is that people who go
> inactive rarely remove themselves from the list.
The only to solve that is with automat
Personally, I like the idea of having a last release date AND a list of people
who are active in the project. The only problem is that people who go inactive
rarely remove themselves from the list.
Ralph
On Oct 15, 2013, at 7:48 AM, Jörg Schaible wrote:
> Hi Gary,
>
> Gary Gregory wrote:
>
On 10/15/13 1:11 AM, Xavier Detant wrote:
> Hi all,
>
> I'm not a commiter nor an active contributor, nevertheless, I use commons
> every days and I clearly do not want to see them die. The reason I'm not
> active is a matter of time (but it's just a matter of organization) and a
> matter of being
Hi Gary,
Gary Gregory wrote:
> On Tue, Oct 15, 2013 at 2:15 AM, Phil Steitz
> wrote:
>> On 10/14/13 10:59 PM, Paul Libbrecht wrote:
>>> Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
I couldn't disagree more. Dormant/attic means the project has leprosy.
I don't know the answer to thi
On 10/14/13 11:50 PM, Jörg Schaible wrote:
> Phil Steitz wrote:
>
>> I just killed a checkout that was grabbing all trunks to get this
>> file. Is there a way to check out just the file, or can we move it
>> somewhere easier to get to?
> svn co -N https://svn.apache.org/repos/asf/commons/trunks-pr
I don't like the idea of putting inactive components in the attic -- unless
there is some unreasonable length of time that goes by without any
development (3 years?). People who want to get things out of the attic are
usually a sole passionate fellow. Can a sole fellow unilaterally get a
component
Le 15/10/2013 14:35, Gary Gregory a écrit :
> the web site can say "last released on -mm-dd, no new
> releases planned".
I like this idea, but unless you automate the site update it adds an
extra manual step to the release process.
Emmanuel Bourg
---
On Tue, Oct 15, 2013 at 2:15 AM, Phil Steitz wrote:
> On 10/14/13 10:59 PM, Paul Libbrecht wrote:
>> Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
>>> I couldn't disagree more. Dormant/attic means the project has leprosy. I
>>> don't know the answer to this, but wondering, has there ever been
On Tue, Oct 15, 2013 at 1:33 AM, Dave Brosius wrote:
> I couldn't disagree more. Dormant/attic means the project has leprosy. I
> don't know the answer to this, but wondering, has there ever been a commit
> to an attic'ed project? I personally would never think of doing that.
It is already hard e
On Tue, Oct 15, 2013 at 12:59 AM, Henri Yandell wrote:
> Three values jump out to me:
>
> * First is for our users. Having code available that no one is supporting
> while giving the appearance of support (ie: active Commons) is a bad
> experience.
We are all volunteers with limited time availabl
On Tue, Oct 15, 2013 at 12:40 AM, Dave Brosius wrote:
> I vote -1 to this process. I see no value in attic-izing projects.
I agree. The attic means graveyard IMO, resurrection is (usually) a
big deal, just ask Miracle Max.
Gary
>
>
>
>
> On 10/14/2013 11:55 PM, Henri Yandell wrote:
>>
>> I cont
ssage -
> From: Paul Libbrecht
> To: Commons Developers List
> Cc:
> Sent: Tuesday, October 15, 2013 2:59 AM
> Subject: Re: [CHALLENGE] Move All of Commons to the Dormant
>
> Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
>> I couldn't disagree more. Dorman
On 10/15/2013 10:31 AM, Torsten Curdt wrote:
I monitor commits, rarely check JIRA, follow and sometimes answer mails and
close to never develop code for that component anymore - maybe once or
twice a year when I go through JIRAs.
Now what?
I appreciate the initiative but don't see this working
I monitor commits, rarely check JIRA, follow and sometimes answer mails and
close to never develop code for that component anymore - maybe once or
twice a year when I go through JIRAs.
Now what?
I appreciate the initiative but don't see this working too well for me.
If this was all just one repo
Hi all,
I'm not a commiter nor an active contributor, nevertheless, I use commons
every days and I clearly do not want to see them die. The reason I'm not
active is a matter of time (but it's just a matter of organization) and a
matter of being afraid of doing something wrong. Clearly, it seams li
Le 15/10/2013 09:13, Henri Yandell a écrit :
> Related; here's the output of a 2006 script I've dusted off to show the
> number of commits and from who to each component in 2013:
>
> http://people.apache.org/~bayard/ActivityReport.html
Nice, I suggest taking into account the commits under src/ja
On 10/14/2013 10:59 PM, Paul Libbrecht wrote:
Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
I couldn't disagree more. Dormant/attic means the project has leprosy. I don't
know the answer to this, but wondering, has there ever been a commit to an
attic'ed project? I personally would never th
On Tue, Oct 15, 2013 at 12:00 AM, Emmanuel Bourg wrote:
> Le 15/10/2013 07:33, Dave Brosius a écrit :
> > I couldn't disagree more. Dormant/attic means the project has leprosy. I
> > don't know the answer to this, but wondering, has there ever been a
> > commit to an attic'ed project? I personall
Le 15/10/2013 07:33, Dave Brosius a écrit :
> I couldn't disagree more. Dormant/attic means the project has leprosy. I
> don't know the answer to this, but wondering, has there ever been a
> commit to an attic'ed project? I personally would never think of doing
> that.
+1
I wouldn't use such a st
Phil Steitz wrote:
> I just killed a checkout that was grabbing all trunks to get this
> file. Is there a way to check out just the file, or can we move it
> somewhere easier to get to?
svn co -N https://svn.apache.org/repos/asf/commons/trunks-proper/
;-)
-
Phil,
> The proposal is not to move it anywhere, just designate it as
> dormant so people know no one is currently working on it. Honestly,
> it is basically *acknowledging* its currently dead state.
Absolutely!
> If you intend to work on it, you can commit to the svn file hen posted top
> of t
I am not happy about the challange, but if you have the file open can you
please add me as active contributor to VFS2? Thanks.
> Am 15.10.2013 um 06:14 schrieb Phil Steitz :
>
>> On 10/14/13 8:55 PM, Henri Yandell wrote:
>> I contend that all of the Commons components are inactive and should mov
On 10/14/13 10:59 PM, Paul Libbrecht wrote:
> Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
>> I couldn't disagree more. Dormant/attic means the project has leprosy. I
>> don't know the answer to this, but wondering, has there ever been a commit
>> to an attic'ed project? I personally would ne
Le 15 oct. 2013 à 07:33, Dave Brosius a écrit :
> I couldn't disagree more. Dormant/attic means the project has leprosy. I
> don't know the answer to this, but wondering, has there ever been a commit to
> an attic'ed project? I personally would never think of doing that.
As probably the only pe
On 10/14/13 10:33 PM, Dave Brosius wrote:
> I couldn't disagree more. Dormant/attic means the project has
> leprosy. I don't know the answer to this, but wondering, has there
> ever been a commit to an attic'ed project? I personally would
> never think of doing that.
There have been commons compon
On 10/14/13 9:59 PM, Henri Yandell wrote:
> Three values jump out to me:
>
> * First is for our users. Having code available that no one is supporting
> while giving the appearance of support (ie: active Commons) is a bad
> experience.
> * Second (generally for the ASF) is that if we have code we c
I couldn't disagree more. Dormant/attic means the project has leprosy. I
don't know the answer to this, but wondering, has there ever been a
commit to an attic'ed project? I personally would never think of doing that.
On 10/15/2013 01:22 AM, Benedikt Ritter wrote:
Am 15.10.2013 um 07:14 sc
> Am 15.10.2013 um 07:14 schrieb Dave Brosius :
>
> Perhaps for new users, however there are lots of projects currently using
> these libraries. We are extending the middle finger to them by doing this. I
> would come away thinking i'm not going to risk using any Apache library, if I
> they w
Perhaps for new users, however there are lots of projects currently
using these libraries. We are extending the middle finger to them by
doing this. I would come away thinking i'm not going to risk using any
Apache library, if I they will just yank away the next project i choose
to use sometim
Three values jump out to me:
* First is for our users. Having code available that no one is supporting
while giving the appearance of support (ie: active Commons) is a bad
experience.
* Second (generally for the ASF) is that if we have code we can't maintain,
because there is no one who can handle
I vote -1 to this process. I see no value in attic-izing projects.
On 10/14/2013 11:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
present a dormancy challenge at
svn co -N https://svn.apache.org/repos/asf/commons/trunks-proper
Happy to move it, also happy to have people pick up a bit of SVN usefulness
:)
I've lifted the definition to:
"(you monitor commits, JIRA, mail, and develop code for that component)"
On Mon, Oct 14, 2013 at 9:27 PM, Phil Steitz
Thanks! I'm a committer in the sandbox, but I haven't ventured into
proper yet. I was hoping to get Commons Convert promoted to proper
someday. In the meantime I would be happy to work on CSV.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 9:32 PM, Phil Steitz wrote:
On 10/14/13 9:26 PM, Adrian Crum wrote:
> I am willing to help out with CSV. ID = adrianc.
Done :)
Phil
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 10/14/2013 9:14 PM, Phil Steitz wrote:
>> On 10/14/13 8:55 PM, Henri Yandell wrote:
>>> I contend that all of the Commons
On 10/14/13 9:14 PM, Phil Steitz wrote:
> On 10/14/13 8:55 PM, Henri Yandell wrote:
>> I contend that all of the Commons components are inactive and should move
>> to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
>> present a dormancy challenge at any time, I'm challengin
I am willing to help out with CSV. ID = adrianc.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 9:14 PM, Phil Steitz wrote:
On 10/14/13 8:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line
On 10/14/13 8:55 PM, Henri Yandell wrote:
> I contend that all of the Commons components are inactive and should move
> to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
> present a dormancy challenge at any time, I'm challenging all of Commons
> Proper.
>
> I've made a fi
70 matches
Mail list logo
