Requesting to become co-maintainer of RE: Comment subjects
| Project: | Re: Comment subjects |
| Version: | 6.x-1.4 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | kiamlaluno |
| Status: | fixed |
Jump to:
sinasalek is willing to become a co-maintainer of this module
precedents (resumed for short, detailed bellow):
- the maintainer became unresponsively
- last actions taken a year ago
- pending RTBC issue since late May (half year ago)
- I have attempted to contact him in several ways with respect of comment_subject's co-maintenance
- now sinasalek is willing to become a co-maintainer of comment_subject
precedents (in chronological sort):
- (October 8, 2008)
I started a discussion (brainstorm) with ahoeben, the maintainer of comment_subject
#318438: Support for other kind of default subjects
#318443: Integration with token (new branch request)
Note that initially both got a "won't fix" but latter (that same day) the maintainer re-opened the second one
- (November 6, 2008)
Last released versions of comment_subject: 4.7.x-1.4, 5.x-1.4 and 6.x-1.4
Currently commits status of the comment_subject project reads
ahoeben - 21 commits
last: 51 weeks ago, first: 2 years ago
- (May 25, 2009)
webchick found a bug on the last release and provided the "quick fix" patch (missing core = 6.x on .info) which has been marked RTBC since May 25, 2009 without getting committed.
#472740: Impossible to enable this module in Drupal 6
- (September 13, 2009)
I uploaded to the issue queue a draft version of what integration with token could be for testing purposes
http://drupal.org/node/318443#comment-2037994
- (September 14, 2009)
Satisfying feature requested by those who tested the draft version I uploaded updated draft versions and also a patch for 6.x HEAD, both of them addressing a new 6.x-2.x-dev branch
http://drupal.org/node/318443#comment-2038526
http://drupal.org/node/318443#comment-2044736
- (September 15, 2009)
I mailed the maintainer (though contact form) with the following message:
Are you no longer maintaining comment_subject?
the issue queue has an old bug with a proposed patch waiting for review
I also would like to jump into token support, which certainly claims for a new branch,
users are currently testing a drafted version I proposed and submitting more feature requests alreadyI would like to maintain a 2.x-dev branch for token support, regretfully I can't become co-maintainer since I'm unable to use CVS due to firewall restrictions
Would be much trouble for you if I provide you with the minor releases of a 2.x-dev branch and you commit changes?
That way I could be a kind of co-maintainer but you would be doing all the CVS commitsIMHO your module's popularity will get boosted with token support, which might be the final passport to D7 core
Note that the provided draft doesn't requires token module as a dependency, it just get more tokens if token module is enabled, otherwise it can handle its own token replacement as core does for mails and other stuffsWaiting to hear from you
Regards,
Antonio
- (September 15, 2009)
In addition to the attempt to contact the maintainer through mail, I changed an issue title to make explicitly that maintenance tasks were pending. Since there the title reads
Integration with token (new branch request)
http://drupal.org/node/318443#comment-2043210
- (September 16, 2009)
I asked (on the group contributed-module-ideas) for someone to commit the RTBC patches on the issue queue of comment_subject, being at that time RTBC old enough and without being committed (yet now a days they remain RTBC but uncommitted).
I also asked (on a forum) for an available CVS committer that would be able to commit on my behalf (since I'm firewalled), one of the aimed targets was comment_subject's co-maintenance
http://groups.drupal.org/node/26952
http://drupal.org/node/577636#comment-2042242
- (October 27, 2009)
sinasalek and I started conversations for him to commit my contributions
http://drupal.org/node/577636#comment-2198410
- (November 3, 2009)
sinasalek and I decided to request co-maintenance of comment_subject. The code is already on the issue queue and users are interested/motivated and requesting new features of an uncommitted patch.
#1
subscribed
#2
I have marked #621790: Co-maintenance request: project comment_subject, user sinasalek as duplicate of this report.
#3
As arhak mentioned , i'm willing to become the maintainer of comment_subject project. thanks.
We want to get back this popular module to life :)
#4
@#2 please, read above detailed explanation
I've been trying to contact the maintainer of comment_subject since September 15, 2009
both: through mail and issue queue with explicitly sentences and polite manners
#5
Dealing with abandoned projects talks of 14 days from when such report has been opened; therefore, the 14 days are from November 3.
#6
yes, we got it from start
I apologize, my bad.
I thought that the attempts through:
- contact form,
- plus the groups request http://groups.drupal.org/node/26952,
- plus issue #318443: Integration with token (new branch request)
where enough
after all the request is about co-maintenance, nobody is declared the project as abandoned.
this issue is currently waiting 14 days to be moved to webmasters issue queue.
I'm deeply sorry for bothering you with this kind of situation.
#7
There have not been any bothering at all.
I completely understand the need to resolve a stale situation, but at the same time we need to consider who first created the project.
I don't see any reasons to not make sinasalek co-maintainer of the project, but we need to follow the procedure.
#8
tomorrow will be 14 days since this issue was opened
finally we'll be able to open another branch for Token integration (alpha)
#9
If the current maintainer doesn't reply, tomorrow at this hour I will make sinasalek co-maintainer of the module.
#10
Please go ahead. By now it is apparent that there are others who are more deserving of being maintainer of this module. Sorry for the wait.
#11
I made the changes as per previous comment from ahoeben.
Thanks for the reply, ahoeben.
#12
@ahoeben
please, no hard feelings, we are not claiming for full maintenance BUT co-maintenance
your issue queue is pretty much clean
only two old bug fixes waiting for commit #472740: Impossible to enable this module in Drupal 6 & #574830: disabled subjects not working after comment_update_6002
and new requests seems to be achievable having some token integration: #318443: Integration with token (new branch request) & #582464: dropdown list of predefined (fixed) subjects
please, don't give up this module of yours,
we'll try to ease some burden around maintenance, but you should keep being the lead
we would like to open a new branch for experimenting with Token integration (alpha)
but we expect for your reviews/criticisms before releasing beta/RC
also, there is a pending fight to get into core #138632: Generate comment subjects from parent subject (re:...) & #223680: Please review the patch for Drupal core
maybe having more community support for D8
#13
Thanks @KiamLaLuno, and also @ahoeben for sharing this useful module.