APACHE COMMONS PROJECT STATUS: -*-indented-text-*-
Last modified at [$Date: 2002/10/20 20:08:36 $]
Release:
none yet; still defining mission :-)
Resolved Issues:
o The Commons will be language-agnostic.
o Projects that are "in scope" are defined as:
- Existing components that are, or would be, useful to multiple
projects
Pending issues:
o Enabling Reply-to on the @commons lists:
+1: aaron, coar, donaldp, geirm
-1: fitz, gstein, jerenkrantz, striker, jim
o The name 'Commons' has caused some heartburn with the
Jakarta community because of the Jakarta-Commons project.
Should we rename to avoid conflicts and keep the peace?
Conflicts would include Java namespace as well as
philosophical aspects.
+1:
+0: coar (i'm willing)
-0: jerenkrantz
-1:
o If we rename, to what? What words/names describe our
purpose?
- toolbox
- util
- library
- suite (sweet?)
- belt (as in bat-belt or tool-belt)
- mcgiver
- ?
What is the project's mission? Our statement of goals/mission/vision
should arise from the answers to the following and other questions:
(jim notes that defining something after the fact seems very backwards
and broken)
o Should it be a parent of reusable code projects used by other
parts of the ASF?
+1: coar, donaldp (if compatible communities), gstein
+0: fitz, striker
-0: jerenkrantz, jim
o Should commons have an sandbox component to ease infrastructure
burden on smaller code bases?
+1: coar, donaldp, jerenkrantz, gstein
0: aaron
-1: jim (the PMC is about reusability, not sandbox)
o What types of components would be appropriate for this
project? ("in scope")
- Tools that help/promote reusability?
Hypothetical: ant, jlibtool, ASF-based autoconf
+1: jerenkrantz, gstein, striker
-1:
- Reusable libraries?
Hypothetical: serf, regexp
+1: jerenkrantz, gstein, striker
-1:
- Development frameworks?
Hypothetical: avalon
+1:
-1:
- Donations that don't cleanly fit into any other projects, but
do fit the goals of the commons?
+1: coar, jerenkrantz, fitz,
donaldp (if it fits the community reqs),
gstein (but the Incubator can claim a donation first; it
only arrives here if the Incubator says it is worthy)
+0: striker (it either belongs in commons or it doesn't, other
projects aren't relevant here, unless they are
'the obvious home')
-1: aaron, jim (otherwise commons becomes a junk drawer)
- Donations that don't cleanly fit into any other projects, and
don't fit the goals of commons?
+1:
-0: gstein (what are the "goals of commons"?)
-1: coar, jerenkrantz, striker, fitz, jim
- Donations that could fit but have a more obvious (proper) home which
has already rejected it?
+1: coar, donaldp, gstein (note the "might fit" term)
-0:
-1: jerenkrantz, jim, aaron, striker, fitz
- Existing ASF components whose committers believe that they
are a better fit under commons and the commons PMC agrees?
(If this component were brought up as new, we would accept it.)
+1: coar, donaldp, jerenkrantz, striker, gstein, fitz
+0: aaron (we need to refine this point, but I like it in general)
-1: jim (by this definition httpd could be in commons)
(gstein says: see the "if" part; we wouldn't accept httpd)
(jim says: until we better define what the PMC would or
would not accept, then this seems too wishy-washy to me)
- Packages being worked on by Apache developers, with a clear
affiliation, that can't or won't be bundled? (E.g., an
httpd module)
+1: coar, donaldp
-1: jerenkrantz, striker, gstein, fitz, jim
Current mission/charter as approved by the board:
'The Apache Commons PMC hereby is responsible for the creation
and maintenance of software related to reusable libraries and
components, based on software licensed to the Foundation.'
The complete text of the resolution that was passed is:
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to reusable libraries and
components, for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Commons PMC", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED, that the Apache Commons PMC be and hereby is
responsible for the creation and maintenance of software
related to reusable libraries and components, based on software
licensed to the Foundation; and be it further
RESOLVED, that the office of "Vice President, Apache Commons"
be and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Commons PMC, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Commons PMC; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Commons PMC:
Aaron Bannert
Ken Coar (chair)
Peter Donald
Justin Erenkrantz
Brian W. Fitzpatrick
Jim Jagielski
Geir Magnusson Jr.
Greg Stein
Sander Striker
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ken Coar be and
hereby is appointed to the office of Vice President, Apache
Commons, to serve in accordance with and subject to the
direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache Commons PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Commons Project.
#
# Local Variables:
# mode: indented-text
# tab-width: 4
# indent-tabs-mode: nil
# tab-stop-list: (4 6 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80)
# End:
#
