These steps are to be completed by the newly-formed PMC. If you already have a PMC and want to create a new sub-project, see the list of project-specifc tasks.
- Decide that you want to establish a PMC
- Decide on an initial PMC membership
(APR did this by fiat, based on existing contributors and clients of the library)
Before submitting a resolution to the board for approval, have the new PMC decide some basics:
- Mission statement
- PMC chair
You will also need to determine bylaws and guidelines, including:
- Project procedures (CTR vs RTC? release management? etc)
- Voting procedures
- Committer access process
- PMC membership process
These are easily borrowed from other Apache projects and then enhanced and consolidated to meet your project's particular needs.
Submit the resolution to the board.
Once the board has approved the resolution, your project PMC can work together with the Infrastructure team to get your project established. To help facilitate this, you are requested to file separate issue tracker requests for each category of item in this list: core, qmail, SVN, httpd, mailing lists. For each mailing list and SVN repository you desire, you will need to follow the list of project-specifc tasks.
After the above is done by the infrastructure team, please review the tasks that the new PMC should do.