commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: [DISCUSS] Putting several unmaintained components to dormant
Date Mon, 14 Oct 2013 09:04:42 GMT
Wearing my old Attic fart hat - something is dead when there is no one left
to turn the light out. Something is inactive when it couldn't pass a vote
to keep the project alive (ie: 3 +1s).

So that's one way to do this. Make a file in SVN. Put each component in it
(include the sandbox perhaps). Ask everyone to vote by putting their name
next to a component.

Any component failing to get 3 names is a goner [aka up for debate, but the
point of the debate is to convince others to add their name to the
component]. Any component with zero names is a goner, kaput, deceased.

Hen



On Wed, Oct 9, 2013 at 12:17 PM, Benedikt Ritter <britter@apache.org> wrote:

> Hi,
>
> I think Phil came up with the idea to try to focus on the components that
> we are able to maintain and put all other stuff to dormant. Here is the
> list of components that I think really are proper:
>
> - CLI
> - Codec
> - Collections
> - Compress
> - Configuration
> - CSV
> - Daemon
> - DBCP (?)
> - Email
> - Functor
> - Imaging (?)
> - IO
> - JCI
> - Lang
> - Logging
> - Math
> - Net
> - Pool (?)
> - Proxy
> - SCXML (after recent interest)
> - VFS
> - Weaver
>
> All other stuff can go dormant because there is currently nobody who
> maintains it. Still a pretty long list. Thoughts? Anything missing?
>
> Benedikt
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message