I've created a new
spreadsheet to keep track of the
specification documents.
The sheet is based on the specifications documents that
Bill provided. You'll notice two columns on the "Raw Data" tab
labeled "Directory" and "File" that reference the contents of
the ZIP file that I can't currently share with the group.
With the first pass, I've made what I believe are very good
guesses at the names of the specifications. I'll adjust these
as I go through the restructuring reviews. I'll likely also
copy over the specification scope statements so that we have
them all in one place (this feels like something that might be
useful). Feel free to fix anything that I've missed.
I've added some columns to track that I've turned projects
into specification projects, that we've gotten the necessary
approvals to contribute the documents, and that we've
contributed the documents. I'll update these columns as I work
through these events.
I've started creating some pivot tables to show the data in
different format. There's a pie chart on the "Spec Rights
Acquired" tab that shows progress in our JCP Copyright License
exercise. I'l likely tweak this chart's presentation a little;
the number will increase over the next couple of days as we
sort through the first batch of specification documents that
we believe that we've acquired the necessary rights for.
The "Specs by Project" tab has a pivot table that shows the
relationship between projects and specifications. I believe
that what's there reflects reality. I used the
Relationships chart as a guide in
a few cases. Let me know if you notice anything that looks out
of place.
I noticed in particular, that there are five specifications
associated with the Jakarta EE Stable APIs project (the PMC
decided today that there were only four). Note that I have an
actual document for every entry in the "Raw Data" page, so
everything there is real.
Comments welcome.
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
