commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Wiedmann <jochen.wiedm...@gmail.com>
Subject Re: [DISCUSS] Mission Statement for Commons...
Date Mon, 07 Oct 2013 10:16:42 GMT
I believe that the problem is Commons structure. To have one big project
which such a lot of subprojects blocks building a small community. You're
not supposed to be a part of the small subproject, but the big community
"Commons". While the former would be appealing for a newcomer, the latter
just doesn't work (too many unknown people).

I have no alternatives to offer, but my feeling is we should attempt to
build smaller, more centralized parts with separate mailing lists, etc.
Obviously, this might lead to a Jakarta-ization, but there are worse things
than being split into subprojects.





On Sun, Oct 6, 2013 at 8:30 PM, James Carman <james@carmanconsulting.com>wrote:

> All,
>
> The Apache Commons project seems to be languishing as of late and we
> need some rejuvenation.  Perhaps we should try to define our mission
> as a project.  What are our goals?  What do we want to accomplish?
> Who are our users/customers?  What non-functional qualities do we want
> our software to exhibit?  How do we want to conduct ourselves?  How
> often do we want to do releases?  What else?
>
> Sincerely,
>
> James
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
"That's what prayers are ... it's frightened people trying to make friends
with the bully!"

Terry Pratchett. The Last Hero

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