[Project_owners] New project adoption policy

[Eric H. Jung]

Hello,

Earlier this year, there was confusion in the mozdev community surrounding mozdev's project
adoption policy. This is the policy to be followed when a project hosted at mozdev has been
abandoned and another project owner wishes to adopt that project.

As a result of the misunderstanding, we vowed to refine the policy and to make it more clear. We
surveyed the existing mozdev project owners, asking for their opinions on adoption policy. Using
the prevailing opinions as our guide, our discussions have concluded, and the following policy has
been adopted.

We hope the policy is now more clear, and that you feel it protects access to your hard work. If
you have any questions, please ask. This policy will be posted at http://mozdev.org shortly.

Thank you,
Eric H. Jung
mozdev board of directors


MOZDEV PROJECT ADOPTION POLICY

1. The user interested in adopting a project makes a formal request to feedback at mozdev.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.
2. 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:

  a. The project is listed on the inactive projects list at
http://www.mozdev.org/projects/inactive.html
  and
  b. mozdev, in its sole discretion, deems the project is a candidate for adoption.

3. 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 secondemail

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.

4. 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.
5. 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.