sorry folks, but I don't have time for this atm
converted to 1.6 markup
|No differences found!|
We need a PMC whose job is to look after the code which has no PMC and to aid with the code who have a PMC but have lost their that code's development community.
Some important memes that I think need to be baked in:
- Non-impacting to users. Being under this PMC does not need to involve resources being moved to their codebase, changing user list etc etc.
- The purpose of the PMC is to:
- Work with the board to define criteria for lacking community, and with other PMCs to identify areas that qualify.
- Provide restricted oversight for these codebases.
- Provide oversight for active user lists with no PMC.
- Purpose is not to:
- Rebuild community.
- Make bugfixes.
- Make releases.
- They should create:
- Document on recognizing community inactivity. ie) What types of community will they accept.
- Document on directions to go to rebuild community.
- Document on how to retire a codebase (how to move to the Attic).
On to the resolution:
Establish the Apache Attic 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 oversight of projects which otherwise would not have oversight. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Attic Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Attic Project be and hereby is responsible for the oversight of projects which otherwise would not have oversight; and be it further RESOLVED, that the Apache Attic Project be and hereby is not authorized to actively develop and release the projects under its oversight; and be it further RESOLVED, that the office of "Vice President, Apache Attic" 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 Attic Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Attic 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 Attic Project: * Henri Yandell <firstname.lastname@example.org> * Nóirín (Plunkett) Shirley <email@example.com> * Rich Bowen <firstname.lastname@example.org> * Scott Sanders <email@example.com> * Mads Toftum <firstname.lastname@example.org> * Henning Schmiedehausen <email@example.com> * Gianugo Rabellino <firstname.lastname@example.org> * Sally Khudairi <email@example.com> * Craig L Russell <firstname.lastname@example.org> * Niclas Hedhman <email@example.com> * Vadim Gritsenko <firstname.lastname@example.org> * J Aaron Farr <email@example.com> * Jeremias Maerki <firstname.lastname@example.org> * Ralph Goers <email@example.com> * Upayavira <firstname.lastname@example.org> * Brett Porter <email@example.com> * Rahul Akolkar <firstname.lastname@example.org> * Davanum Srinivas <email@example.com> * Thomas Vandahl <firstname.lastname@example.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Some Poor Sod be appointed to the office of Vice President, Apache Attic, 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.
Brain dump of topics for further discussion. They were useful in getting a feel for what Attic would do.
Different types of projects:
- Top-level project with only one or two active PMC members, and therefore cannot do releases (need 3 PMC votes for a release).
No active PMC -> Board kill.
- Maintenance - no active committers, but they come together to do the release (this is not Attic!).
- No active committers at all.
- Top-level project has a sub-project with one active committer - Top-level PMC can vote (this is not Attic!).
Possible examples (to test the types above):
- Excalibur - alive enough not to go in the Attic. Emails are answered, if a bug then Cocoon will fix it. (3)
HiveMind - (2)
- ECS - (4)
- JMeter - (5)
- Cactus - (5)
- JCS - (5)
AxKit - (4)
- OJB - (4)
- Xindice - (?)
- Quetzalcoatl - (2?)
- Santuario - (2?)
- Xang - (4)
- Crimson - (4)
- Board. Lack of reports, off to the Attic. Generally not from the Incubator.
- Is the PMC able to call a vote?
- Can releases be done?
- Close PMC down.
- SVN read only.
- Add banner to websites.
- Contextual email to user list once a year saying it's dead. Suggest alternative projects.
- Kill the dev list.
- README on archives.
- Kill builds.
- JIRA: Move to Retired projects. Update description. Point url to attic. (Make retired projects commentable?)
- Bugzilla: Stop new issues.
- Explain situation. Not enough developers, feel free to fork and let us know so we can link to you.
- Attic - logo.
email@example.com for public discussion.
- Attic PMC is join on request by any member (basically meaning that it's very open).
What to do about trademarks?
- Java package name: Yes you can keep using this (needed for forking.. comment on when to change package names?).
- Name: Cannot use the existing name - you can say "Based on Apache Xxx". If you want to use the name, email attic@.
- Maven groupId/artifactId: No you can't use this.
Links of interest: