The module PageEar (a.k.a. Page Peel, Peel Ad, Peel Away or Magic Corner) (http://drupal.org/project/pageear) looks abandoned for about one year by now and I would like to take over it. I have tried to contact the maintainer using contact form on his user profile but no answer. Then I wrote an issue (http://drupal.org/node/460470) but I had no answer from maintainer either.

I have the code just worked and I posted it in a comment in same issue. It is tested and working fine. Just totally prepared to make a dev snapshot.

I even have just another version just prepared which would solve one of other requests made in that module issue queu (more than one Pageear on a website managing each pageear visibility as blocks visibility are managed, by languages, roles and pages).

I know how to work with CVS by now. I have read the documentation and I have tested how to use it. I worked with two modules in eclipse, using the anonymous access to cvs. And I installed my own CVS Server to do more testing. I still don't know how to branch with eclipse (to branch it obligates me to make a version tag too) but I know how to work from command line (http://drupal.org/handbook/cvs/quickstart). I have just practised the command line with my personal CVS Server and know how to checkout, branch, tag, add, and commit which are the things I would need to do.

I saw the CVS drupal dojo screencast that shows how to deal with the project page too.

I'm trying to follow steps from this article (http://drupal.org/node/251466) if this is not the correct way I would be pleased if you could give me some advice.

Thanks in advance.

Comments

damien tournoud’s picture

damien tournoud commented
Status: Active » Postponed

Please start by opening an explicit "is module X abandoned?" in this module issue queue, as described in http://drupal.org/node/251466:

1. File an issue in that project's queue under the "support request" category stating your request to take over maintainership. If you have a patch for the module, mention that as well, as it shows you are already working on the code.

manfer’s picture

manfer commented

Ok, I just did (http://drupal.org/node/473584). I suppose now I must wait.

More or least I had done that question in the previous referenced issue. And I supossed it could be enough looking the maintainer activity too.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

The report put in the issue queue for the project that you think is abandoned to ask if the module is abandoned must be titled Is Xyz still maintained?; if you don't get any answer to that, then you can pass the report here, after you changed the title to Xyz seems abandoned.

manfer’s picture

manfer commented

Ok, I changed title to "is Xyz still maintained?" Of course with module name and no Xyz. I suppose that is what you mean.

What I don't understand is what exactly means: "if you don't get answer, then pass report here, after change the title to Xyz seems abandoned".

With pass report here, you mean change title on the module issue and then reply on this issue with a link to the one on the module or it means to move the module issue to this Drupal.org webmasters project?

If the answer is move it I suppose I have to change the project field from Xyz (name of project) to Drupal.org webmasters in edit issue settings.

I also suppose I should wait to see if I get an answer on the issue before "moving it here" or "reply here with a link to the issue" whatever the way is the correct to proceed.

In meanwhile if you clarify this two questions it would be highly appreciated:

How much to wait?
And after that, change title, and proceed with a reply here with a link to the issue or move the issue to this project?

Thanks.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

If the answer is move it I suppose I have to change the project field from Xyz (name of project) to Drupal.org webmasters in edit issue settings.

Yes, that was what I meant. I am sorry if I was not clear enough. Of course this is normally done so because you open first the support request in the project issue queue, and only when you don't get an answer, you move it to this issue queue. In your case, after you waited 2 weeks without to get any answers, you report the fact here.
If you get an answer from the current maintainer, then you can tell him you would like to become co-maintainer, and you explain how you think to contribute with the module.

The time you should wait is at least 2 weeks that are calculated from the moment you wrote the support request.

Good luck with this.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Postponed » Closed (duplicate)

Le sigh... this is a duplicate of #473584: Taking over PageEar (a.k.a. Page Peel, Peel Ad, Peel Away or Magic Corner)

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer