Want to take over the Auto Copy extension

RESOLVED FIXED

Status

addons.mozilla.org Graveyard
Administration
--
minor
RESOLVED FIXED
10 years ago
2 years ago

People

(Reporter: djc, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: 

I've gone through the Project Adoption process over at mozdev, and am now the proud new maintainer for the Auto Copy extension. Now, I'd like to be able to update the listing on addons.mozilla.org for the extension, but of course I'm unable to do so given the fact that I cannot access the extension as a developer. The reason I've taken over the project is that the author hasn't responded to either my or mozdev's email messages, so I cannot ask him to add me to the maintainers on AMO. It would be nice if AMO recognized mozdev's adoption process.

http://www.mozdev.org/drupal/blog/New-project-adoption-policy

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
(Reporter)

Comment 1

10 years ago
David Boswell (david@mozdev.org) walked me through Project Adoption, but he seems to have no bugzilla account around here.
(Reporter)

Comment 2

10 years ago
CC'ing David.

Comment 3

10 years ago
I can confirm that Dirkjan is the new project owner of the autocopy.mozdev.org project.  

http://autocopy.mozdev.org/members.html

Since the project had been inactive for some time it was eligible for adoption.  I'm not sure if AMO has an adoption policy (if it does we might want to look in to syncing them up) but I can vouch for Dirkjan on mozdev.

Comment 4

10 years ago
Given that AMO doesn't have an official policy on project adoption, for now, we'll accept MozDev's adoption process. I've added your AMO email address, Dirkjan, as an addition author on Auto Copy. Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
(Assignee)

Updated

2 years ago
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.