I've been using Drupal since 2009 and some modules saved my life. I'm quite new to the Drupal framework and currently needing some functionnalities that i've not found in current modules.
I actually found a module that i could co-maintain (Auto Assign Role) instead of creating an almost same module.
I'm working on Drupal 7 and have been writing a similar module since the D7 Port of auto assign role does not provide yet all the functions that it should do (User registration form altering not implemented yet : #983612: 'Allow user to choose' functionality doesn't work).
I also given to my module the opportunity to work with Profile 2 (i think with D7, Content Profile is not the best solution for this module anymore) by changing dynamically the displayed Profile 2 fields according to the chosen role(s) (using #states) during the registration.
Hi, i already contacted the module's current maintainer and posted a patch in the issue #983612: 'Allow user to choose' functionality doesn't work.
Do I have to create a new issue especially for the co-maintenance application ? The CVS application requirements page says "Create an issue in the module's issue queue requesting co-maintainership", but the "co-maintenance application" choice in the module's issue form is not available (whereas i can see it here under the "Component" drop-down menu)
It's enough the title is Offering to become co-maintainer.
What we really need is a report where the current maintainer clearly states s/he accepts you as co-maintainer. The title is not important for us, but should be a title that makes clear to the maintainer what you are asking for (as any issue reports).
The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
If your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
Comments
Comment #1
ben kuper commentedI actually found a module that i could co-maintain (Auto Assign Role) instead of creating an almost same module.
I'm working on Drupal 7 and have been writing a similar module since the D7 Port of auto assign role does not provide yet all the functions that it should do (User registration form altering not implemented yet : #983612: 'Allow user to choose' functionality doesn't work).
I also given to my module the opportunity to work with Profile 2 (i think with D7, Content Profile is not the best solution for this module anymore) by changing dynamically the displayed Profile 2 fields according to the chosen role(s) (using #states) during the registration.
Comment #2
avpadernoHello, and thank you for applying for a CVS account.
Please read http://drupal.org/cvs-application/requirements to understand what you are supposed to do to get a CVS account to be co-maintainer.
Comment #3
ben kuper commentedHi, i already contacted the module's current maintainer and posted a patch in the issue #983612: 'Allow user to choose' functionality doesn't work.
Do I have to create a new issue especially for the co-maintenance application ? The CVS application requirements page says "Create an issue in the module's issue queue requesting co-maintainership", but the "co-maintenance application" choice in the module's issue form is not available (whereas i can see it here under the "Component" drop-down menu)
Comment #4
avpadernoIt's enough the title is Offering to become co-maintainer.
What we really need is a report where the current maintainer clearly states s/he accepts you as co-maintainer. The title is not important for us, but should be a title that makes clear to the maintainer what you are asking for (as any issue reports).
Comment #5
avpadernoPlease read all the following and the links provided as this is very important information about your CVS Application.
Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:Migrating from CVS Applications to (Git) Full Project Applications.