Hi Jeremy,

I'd like to become a co-maintainer for this module. The CVS guidelines says that I should create an issue, so here it is. Quote from the application guidelines below:

If you are applying for a CVS account because another module maintainer has agreed for you to become a co-maintainer of their module (or to take over the module completely), please ensure this agreement is publicly available by creating a issue in the project's issue queue that clearly shows the current maintainer agreeing to that fact. Under this condition just stating this in the motivation message alone is insufficient for your application to be progressed. Once you have created the issue and the current maintainer has commented on it please don't forget to place a link to that issue in your motivation message to make the CVS administrators lives a little easier.

Thanks for the module and your ongoing contributions!

Chris

Comments

jerdiggity’s picture

Hi Chris.

Yes, I'd be glad to have you as co-maintainer. Just remember the Golden Rule of Drupal. Then, let me know what it is when you get a chance. :) (Actually, I suppose it's probably along the lines of "Never hack core" but I was hoping for something a little more exciting like "God Save the Code" or something.) :)

Anyway, "Yes" -- welcome on board.

jerdiggity’s picture

Category: support » task
Status: Active » Closed (fixed)

Cleaning the issue queue... Open a new issue if you decide to follow through with this.