Mozdev Project Adoption Policy
The user interested in adopting a project makes a formal request to firstname.lastname@example.org. This initiates the adoption procedure. Emails sent by the user directly to the existing project owner or the project's mailing list are not a valid means of communicating adoption requests. IRC conversations, forum, wiki, blog entries, and other communications do not constitute legitimate adoption requests, even if those communications are with mozdev staff.
mozdev confirms receipt of the adoption request and determines whether or not the project is an adoption candidate. A project is not a candidate for adoption unless:
- The project is listed on the inactive projects list at http://www.mozdev.org/projects/inactive.html
- mozdev, in its sole discretion, deems the project is a candidate for adoption.
If mozdev determines the project is a candidate for adoption, mozdev sends emails and/or other electronic communications to the project owner(s) asking for permission to grant administrative privileges to the project to the requesting user. The schedule for this contact is:
- First email: sent within a week of the original adoption request (providing step 2 has been met)
- Second email: if no reply has been received, sent one week after first email
- Third email: if no reply has been received, sent one week after second email
If no email reply has been received two weeks after the third email, the requesting user is given adoption privileges by assignment of administrative rights to the project. If the project owner replies to mozdev within the stated period asking the user be granted adoption privileges, the user is granted such privileges. If the project owner replies to mozdev within the stated period asking the user not be granted adoption privileges, the user is not granted adoption privileges. If the project owner replies to mozdev after the stated period asking the user not be granted adoption privileges: the original project owner has the right to request that his project be returned to him. If it is not possible for the original and new project owners to agree to mutually satisfactory terms, control of the project reverts to the original owner. The new owner is welcome to fork the code, subject to accordance with the original license, and create a new project. Under no circumstances will mozdev arbitrate between project owners; project owners must communicate with each other directly.
If there are multiple existing project owners, any one of the project owners can veto the adoption request.
When a project is adopted by a new owner, the previous owner(s) retain(s) their commit privileges so they can continue to work on their project if they choose.
The new project owner must read the mozdev copyright policy at http://www.mozdev.org/copyright.html. He should understand that certain project pages and materials may not be eligible for adoption because they are not open-source licensed. mozdev has no power to assign or reassign any copyrights.