Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It's been over a year, it would be great if some of the outstanding issues in this issue queue were addressed and there was a new release.
There are nearly 30k sites using this module. That's a lot of folks who depend on this code and are leveraging it to do all manner of groovy things.
There aren't all that many open bugs, but it's clear that there's a call for new maintainers.
The project page may be out of date, but looking at activity in contrib on d.o it occurred to me that we don't really have a good process for bringing on co-maintainers. Not that there isn't a process to make it happen, but it is all very mechanical.
I've proposed a few issues that might help bring in more motivated developers:
- #2186377: Highlight projects that follow Best Practices
- #2138397: Highlight Flattr, Paypal or Whatever Opportunities on Issue Pages
- #2177459: Highlight Supporting Organizations in the Issue Queue
- #2185511: Highlight User Contributions & What They Can Do Next in Issue Queue
Ultimately though it depends on the community of folks using this code. I do think it would be beneficial to talk about giving the maintainer the support that he has asked for.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | fullcalendar-perms.png | 65.47 KB | tim.plunkett |
Comments
Comment #1
mkadin commentedThanks for posting this. I picked up this module a while back, but my work at a non-Drupal-using company has completely eaten up all of my Drupal community time. I'd really appreciate someone stepping up and taking over maintainership, as unfortunately, I'm unable to commit any time here :(
Comment #2
mgiffordArg.. Those non-Drupal-using companies... Thanks for getting back to me so quickly though and I do totally understand!
Should the Status be changed to: Seeking new maintainer
Thanks for all of your work on this module over the years @mkadin
The community needs to know this is an issue and find incentives to see that other folks step up to the plate and carry on your efforts!
Comment #3
mgiffordComment #4
mgiffordComment #5
tim.plunkett#1772204: EntityMalformedExceptions with custom entity modules has been sitting a while, and I would like to help get it in.
I don't have the time to step up as a fully committed maintainer, but I could provide some reviews and commits where needed as a comaintainer, since we use this module heavily at my $dayjob.
Comment #6
mgiffordThanks for stepping up for this @tim.plunkett! Your help with this module would be great!
In #2203331: Differentiation of the Maintainer Role I suggested a role of Interim maintainer just for this kind of situation. If there were this kind of role it would make the expectations a bit clearer for @mkadin or @eaton.
Comment #7
tim.plunkettThat's up to the maintainer when they assign the permissions.
For example, in the FullCalendar module, only I can edit the project, add more maintainers, or make a release. One other co-maintainer can commit code, the third can only assign issues to other maintainers:
There need not be any more formalized role than that and the docs on https://drupal.org/node/363367.
Comment #8
mkadin commentedThanks for stepping up Tim, I've added you with full rights, but will keep the status as 'seeking' new maintainer, and we should leave this issue open to that end.
Comment #9
scotwith1tAny reason we're still on 1.2 on this module? A new version would be most welcome...what are the blockers?
Comment #10
rcodinaI agree with @scotself We need a new release ASAP!
Comment #11
geek-merlinI can help as co-maintainer. Like tim, not full power, but i use this enuff to do some reviews, do issue housekeeping and the like.
You may want to look into views_evi or other contributions if you wonder if i know what i do ;-)
Comment #12
geek-merlinAdded an issue focused on release ;-):
#2647732: Plan for EVA 7.x-1.4 release
Comment #13
mgiffordHi Axel. Would be great if you could jump in.
@tim.plunkett, @mkadin, @eaton - can someone give him access?
Comment #14
tim.plunkett@axel.rutz, you can now commit code, assign issues, and create releases.
Comment #15
mkadin commentedThanks @tim.plunkett for changing the perms.
@axel.rutz thanks for some of your work on the issue queue in the last few days. I don't develop on Drupal anymore, but I'm glad someone is interested in picking up the work to be done here.
Of course, with great power comes great responsibility! There are a lot of sites using this module, so craft releases carefully :) Good luck on the D8 port.