We've done all the necessary things (note to self: check it's all
recorded): IP, website, developer community, development, release, added
committers and PMC members.
I haven’t heard anyone disagreeing with the idea of graduating ... now
would be a good time to speak up if you've forgotten to send email about
something. :-)
So I think we're in good shape. One part of graduation is board
resolution and one part of that is the description of the project in a
few words.
The template is
https://svn.apache.org/repos/private/committers/board/templates/podling-tlp-resolution.txt
(not public but the graduation discussions are).
There are two slots: DESCRIPTION and PROJECT.
== Recent Examples
Apache Bean-Validation (BVAL)
http://s.apache.org/IV2
Apache Gora
http://s.apache.org/OyO
Apache Empire
http://s.apache.org/QsQ
== PROJECT
I'm assuming the project name is "Apache Jena". !!!
As this is already well known, I don't think a full name check is needed
but I did a quick spot check using Bing (Google uses Google+ to skew
results - I get us for "jena" as #1 hit)
Bing "Jena" ==>
#1 Wikipedia page about the town in Germany
#2 Jena-uk - a manufacturer of aluminium containers
#3 Our incubator site
#4 Wikipedia page about a significant recent history event in Jena,
Louisiana, US.
... stuff about binoculars (Carl Zeiss started in Jena, DE)
(aside - all the hits go to http://incubator.a.o/jena -- they seem to
have taken on board the redirections openjena and SF)
== DESCRIPTION
This fits in two paragraphs:
.... establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to ${DESCRIPTION-AND-SCOPE}
for distribution at no charge to the public.
and
.... responsible for the creation and maintenance of software
related to ${DESCRIPTION-AND-SCOPE};
looking at other resolutions, they don't have to be the same. Or very long.
= Proposal for Description
Our issue for a description that does not mess up Stanbol, Clerezza
Any23 and any possible future projects. Obviously, in a short
description, its not going to be precise to Jena, and it needs to be
open to things that Jena might receive in the future.
First text:
[[
the processing, storage and retrieval of semantic web data
]]
which does not say "publish" which I would have if it included "linked
data".
Second text (same)
Alternative:
s/semantic web data/linked data/
I chose "semantic web" as it's about the base technology, not the
manifestation, "linked data" - this isn't primarily for marketing.
We could add "tools" but I'm happy that tools are a delivery of the
technology.
Other suggestions, refinements etc etc most welcome. Wordsmithing these
things is not my strong point.
Andy
Putting it all together:
(this is not a final draft)
-------------------------------------------------------------------
X. Establish the Apache Jena Project
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 the processing, storage
and retrieval of semantic web data 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 Jena Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Jena Project be and hereby is
responsible for the creation and maintenance of software
related to the processing, storage and retrieval of
semantic web data and be it further
RESOLVED, that the office of "Vice President, Apache Jena" 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 Jena Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Jena Project; 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 Jena Project:
* <Include PMC here -- mentors - who is continuing?>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that John Smith
be appointed to the office of Vice President, Apache Jena, 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 Jena 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 Jena Project; and be it further
RESOLVED, that the Apache Jena Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Jena podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Jena podling encumbered upon the Apache Incubator
Project are hereafter discharged.
