Per our conversation, would like to be a co-maintainer of this module with you ...
puzzlemaster - April 5, 2009 - 23:35
| Project: | Views Alpha Pager |
| Version: | HEAD |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Following the guidelines set out here: http://drupal.org/cvs-application/requirements - I would like you to confirm our discussion to bring me on as a co-maintainer of the Views Alpha Pager module.
#1
The first thing you could do is to test patches that fix bugs (not new features). Apply the patch, make sure it applies cleanly, test it, you might need to think it through a little bit and make sure that the patch really solves all the cases, or if the patch is done in a good way. I'd like all my modules to be secure, internationalizable and adhere to coding standards. Not everyone does a great job with using t(), l(), and check_plain(), or with spacing and curly bracket placement. If their missing stuff like this, and you think that the patch is fundamentally sound after testing it, reroll the patch to fix these things. If you test a patch and think it's good, you can mark it as RTBC. You'll need to ping me to ask me to look at it. And I apologize in advance if you need to ping me more than once ... but you might need to. I'll review the RTBC and commit them.
Once you get your CVS commit access, I'd still like to review your stuff for a bit. But I might ask you to make the commit. And once we're both comfortable then you'll be able to handle these things on your own.
The second thing you could do is just help people in the issue queues by telling them how they can or can not use the module. Most issues are probably non-issues.