Taking over PageEar (a.k.a. Page Peel, Peel Ad, Peel Away or Magic Corner)

I have been working on this module that looks not being maintained any more for more than one year. Is now 6 week since I started this issue and I had no answer.

I has provided my new module to test and some people reported it is working fine. It is a totally new rewrite of the module that gives new features and now does not depend on a non GPL project than previous version does. Here is the issue with new version and tests: http://drupal.org/node/513952

I would like to maintain the module and release the new version.

It would be my first incursion on CVS so if this is accepted I would like some help to do things the correct way.

One of the features on the module is managed through visibility (by user, by language, by page like blocks). In previous version this was managed through another module (conditions) that I think provided with visibility options by site and by domain too that for now I'm not providing. So my idea is to make that previous version still available for those who want to continue using it.

As I say I'm not too familiar with CVS, though I think I understand the basics, and I'm not totally sure how to proceed. My idea is to branch to avoid afecting the previous version. The new module rewrite I worked in, has 5.x version too, so I suppose that would be another branch too.

Anyway those are things I would like someone to help me clarify if this is accepted.

Thanks in advance.

This comes from this postponed issue:

http://drupal.org/node/473496

(there is no way to contact old maintainer)

I'm sorry I have to ask for help on CVS use but it is something only to prevent doing something wrong. Really any problem to deal with CVS. Only would like to clarify before doing something wrong.

As an example clarify // $Id$ on all files that would be change properly by drupal CVS and what I said before about the correct way to proceed about branching.

Thanks.

• If there is no response, move the issue to the webmasters queue.
• Change the title to something like, "PROJECT_NAME appears to be abandoned" and list your reasons for this, as well as noting that the maintainer has not responded. If you feel the project is not only abandoned but badly broken (unusably so), mention your reasons for that as well. Please include a link back to the project page to make it easier for the admin.
• A site maintainer (or higher) should carefully review the project. If s/he agrees with the assessment, s/he can then add a note to the project page that the project is in need of a new maintainer and link to a replacement module if one exists. Here is a template that can be used:
  

  Note: As of YYYY/MM/DD, this module appears to no longer be supported. If you are interested in taking this module over, or you as the module maintainer feel this message has been posted in error, please reply to [link to webmasters issue].

• If the site maintainer / admin agrees the project is badly broken and not recommended to use, s/he should unpublish all of the releases as well. If a replacement project is known, link to that project. This should only be done if absolutely necessary as unpublishing the releases will cause update status to notify everyone currently using the project that it is no longer supported. Because of the effects on the users, the site maintainer / admin should install the module first to verify that it is unusable before taking this step.

This is what it say's here --> http://drupal.org/node/251466

The procedure has been followed correctly; manfer first opened a report in the module issue queue, and then he moved the report to the Drupal.org webmasters issue queue; from when he opened the support request, and when he moved the report, 2 weeks have passed.

Thanks, may I do something more, or just wait to be accepted and get the CVS account?

drupal.org/cvs-account

Automatically closed -- issue fixed for 2 weeks with no activity.