co maintainer offer

Hi Greg,
Help is always welcome, but before giving you an maintaining role, I would suggest that you take some open issues and submit patches to it.
What do you think?

Cheers,
Fabiano Sant'Ana

Hi Greg,

Thank you for your reaction on my call for co-maintenance, it's really appreciated.

To elaborate on wundo's remark about being a co-maintainer: the best way is typically that you provide your contributions/maintenance through patches in the issue queue, we (the current maintainers) review them and we discuss them. Over time, we can grant you CVS commit permissions for the module. That's the standard procedure on drupal.org and also how I got started before I became a real maintainer of the CAPTCHA module.

There are two important things in the CAPTCHA module that have a high priority (but unfortunately I can't allocate the required time to work on it right now)

* Drupal 7 port: It would be nice if we could make it before Drupal 7 comes out. Issue: http://drupal.org/node/670810
* Work on cachability of CAPTCHA elements. I'm thinking along the lines to add the challenge to the page with AJAX, so the page itself can be cached, but the challenge can be different for every visitor. The problem here is that AJAX in Drupal 6 is a bit tricky, especially for CAPTCHA because it puts elements on forms that are build by other modules, so we have to be careful about side effects and interactions. Issues: http://drupal.org/node/632742, http://drupal.org/node/180328

Those things are however not trivial and require a fairly large amount of knowledge about the CAPTCHA module and Drupal in general. I guess you want to start with some more "low hanging fruit". These are some issues that are tagged with "low-hanging fruit": http://drupal.org/project/issues/search/captcha?issue_tags=low-hanging%2...

And what is also very interesting for diving in and exploring the functionality of a module is writing unit tests. I already wrote some tests (see captcha.test), but there is a lot more to be covered. There is a lot of info about the test infrastructure in Drupal, but I think http://drupal.org/node/395012 is a good start.

Of course, you're also welcome to work on ideas or feature requests of your own or other issues in the issue queue (http://drupal.org/project/issues/captcha) if you want.

I hope this gives you a short overview of what you could work on. If you have any more questions about this, please don't hesitate to reply. The best place to communicate (at least about technical stuff) is in the issue queue, because other people can follow and chime in. But of course you can also contact us by mail if necessary.

Hello there,

I spend this day porting image_captcha to Drupal 7.
Nightly dev (full version) is attached:

captcha-7.x-1.0-alpha1 [2010-09-03].zip

THIS COMES WITHOUT ANY WARRANTY;
THIS PORT IS NOT 100% DONE; THERE ARE STILL WARNINGS...

... but it seems to work fine ;)

I'm not a Drupal Professional, yet, but growing every day.
I'm looking forward to release an official real alpha1-version the next days.
Therefore all code and comments will be cleaned and standalone patch will be offered.

Co-Maintaining this module would be nice- I think we'll see

R2-D8 aka heerschlag

at R2-D8 in #4: very cool, thank you!
I've just scanned through the differences (not tested the code yet), and it looks very good already.

Working with a zip is indeed cumbersome, and a patch would be much easier to review/work with.

FYI: I do my development on CAPTCHA with git and sync regularly to drupal.org's CVS. So, if you're familiar with git, you might want to fork from my git repo (branch master-d7): http://github.com/soxofaan/drupal-captcha-dev/tree/master-d7 and work from there? If git is new to you, providing patches is fine too of course :)

Apart from that, I think we should continue this "port to Drupal7" discussion at its main thread: #670810: Port to Drupal 7

Clearing issue queue.