[drupal-devel] Becomming a contributor for the project module
Hi All, I recently added two new patches for the project module. I appreciate developers are busy people, but it's now been over a week and no-one has committed the patches and only one person has reviewed a patch: http://drupal.org/node/29050 http://drupal.org/node/29061 I would like to make a few further changes to the project module and even write my own modules for Subversion/CVS integration and have applied for committer status (over a week ago now) but have yet to hear back. Is there a moratorium on new committers? Is someone already looking after the project module? If not, what is the likelihood that I could be made a committer? TIA... -- Ricardo Gladwell <ricardo.gladwell@gmail.com>
Hi Ricardo,
I recently added two new patches for the project module. I appreciate developers are busy people, but it's now been over a week and no-one has committed the patches and only one person has reviewed a patch:
http://drupal.org/node/29050 http://drupal.org/node/29061
I would like to make a few further changes to the project module and even write my own modules for Subversion/CVS integration and have applied for committer status (over a week ago now) but have yet to hear back. Is there a moratorium on new committers? Is someone already looking after the project module? If not, what is the likelihood that I could be made a committer?
It is always the best idea to directly contact the module maintainers, and ask for permission to commit changes and additions, and/or bring your patches to their attention. I for one have been (and I am) quilty of not doing much maintanance on modules showing up as maintained by me, but in case I see some positive takeover offer, I mostly grant and let the module evolve. Since project module is an integral part of the Drupal project, and is heavily used on drupal.org, it is a different matter however. Anyway, you need to contact the maintainer(s) directly. Regards, Gabor Hojtsy
On 29/08/05, Gabor Hojtsy <gabor@hojtsy.hu> wrote:
It is always the best idea to directly contact the module maintainers, and ask for permission to commit changes and additions, and/or bring your patches to their attention. I for one have been (and I am) quilty of not doing much maintanance on modules showing up as maintained by me, but in case I see some positive takeover offer, I mostly grant and let the module evolve. Since project module is an integral part of the Drupal project, and is heavily used on drupal.org, it is a different matter however. Anyway, you need to contact the maintainer(s) directly.
With all due respect , I would have thought posting issues in the bug database against the project module and then, when that didn't work, posting to the devel mailing list here would be sufficient to at least attract someone's attention. What with all the hoops I need to jump through just to get a couple of minor patches submitted to the project module, I'm beginning to feel that the effort outweighs the benefits. I will endeavour to contact the module maintainers, but if anyone else get's the time to review the patches or, failing that, review my CVS access submission, I would be most grateful. Kind regards... -- Ricardo Gladwell <ricardo.gladwell@gmail.com> http://www.ax0n.uklinux.net/
Ricardo Gladwell wrote:
With all due respect , I would have thought posting issues in the bug database against the project module and then, when that didn't work, posting to the devel mailing list here would be sufficient to at least attract someone's attention.
What with all the hoops I need to jump through just to get a couple of minor patches submitted to the project module, I'm beginning to feel that the effort outweighs the benefits. I will endeavour to contact the module maintainers, but if anyone else get's the time to review the patches or, failing that, review my CVS access submission, I would be most grateful.
Well, Ricardo, most people are working on Drupal in their spare time or at least do contribute on a larger scale then what are they paid for. IMHO this should be considered. Things often take time. Especially with the project module, which is not used in too wide circles because of it is (perceived to be?) too drupal.org specific. Gabor
On 29/08/05, Gabor Hojtsy <gabor@hojtsy.hu> wrote:
Well, Ricardo, most people are working on Drupal in their spare time or at least do contribute on a larger scale then what are they paid for. IMHO this should be considered. Things often take time. Especially with the project module, which is not used in too wide circles because of it is (perceived to be?) too drupal.org specific.
I appreciate people are busy and you will notice I mention that in my original message. I also noted that I'm quite happy to go in myself and make the changes if people are busy, but if I can't do either then I can't do anything except pester people here and elsewhere then it becomes a bit of a waste of my own scarce time. -- Ricardo Gladwell <ricardo.gladwell@gmail.com> http://www.ax0n.uklinux.net/
On Mon, 29 Aug 2005, Ricardo Gladwell wrote:
On 29/08/05, Gabor Hojtsy <gabor@hojtsy.hu> wrote:
It is always the best idea to directly contact the module maintainers, and ask for permission to commit changes and additions, and/or bring your patches to their attention. I for one have been (and I am) quilty of not doing much maintanance on modules showing up as maintained by me, but in case I see some positive takeover offer, I mostly grant and let the module evolve. Since project module is an integral part of the Drupal project, and is heavily used on drupal.org, it is a different matter however. Anyway, you need to contact the maintainer(s) directly.
With all due respect , I would have thought posting issues in the bug database against the project module and then, when that didn't work, posting to the devel mailing list here would be sufficient to at least attract someone's attention.
Well, it often doesn't. Especially if the maintainer is bogged down with other work.
What with all the hoops I need to jump through just to get a couple of minor patches submitted to the project module, I'm beginning to feel that the effort outweighs the benefits. I will endeavour to contact the module maintainers, but if anyone else get's the time to review the patches or, failing that, review my CVS access submission, I would be most grateful.
I will have a look as time permits. I don't have much time, though. Cheers, Gerhard
participants (3)
-
Gabor Hojtsy -
Gerhard Killesreiter -
Ricardo Gladwell