Posted by joachim on September 8, 2009 at 11:48am
Jump to:
| Project: | |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
eaton, would you consider appointing a maintainer for the D5 branch? I asssume it's very low down on your list of priorities to keep this up to date, but the stack of incremental patchs at http://drupal.org/node/316811 is getting longer all the time. I'm sure one of the many commenters there could be trusted to keep the 5 branch ticking over while people use it.
Comments
#1
It's been over a month and no response.
Clearly many people are still using the D5 version of this module, and helping to keep it updated.
This work would be made a LOT EASIER if the maintainer of this module appointed a sub-maintainer for the D5 branch, so we could have a stable codebase to compare, patch against, etc.
#2
D6 version also does not have an active maintainer for several month. has anyone contacted any of the current maintainers?
#3
eaton is on IRC fairly often.
#4
This pertains to the 5.x so moving there. However, I'm sure you'd probably get a more proper response if someone actually was volunteering here instead of asking eaton to assign a maintainer - do we even know if someone wants to do the job/is up to it?
#5
Drupal 5 is not maintenance any more, If this issue occurs in any version for Drupal 6 or Drupal 7 reopen this issue.