Dear sir/madam,
I'm a college student at Shanghai Maritime University. I've been learning Drupal for more than a year. I have a certain understanding of the development and documentation of Drupal community. And I also know how to use the issue queue to help others and get help. Recently, In my school project, I have a lot of work with the signup module. But I find that this module is updated slowly, and there are still many problems in the 7.x version. In addition, signup module still have 420 open issues and 113 open bug reports. I want to try to maintain this module. Learning from this work and helping the community. So I write this letter to you, hope you can give me the opportunity.
Thanks!
Jerenus
Comments
Comment #1
dwwThanks for the offer to help! Agreed, this module is once again in sad shape. :/ A quick search reveals that you've only participated in 2 issues in the signup queue, although in both cases it was to post a patch (and the patches seem good based on a very quick skim). So, that's a great track record for participating by contributing patches. ;)
I'm once again having doubts about the future of this module and code. Honestly, in D7, the entity signups module seems like a better underlying architecture, although I haven't tried using it, have no idea what state it's in, etc. Believe it or not, the only site I ever personally used signup.module on was for Drupal 4.6. So I don't really have any direct interest in this anymore, and have been maintaining it "for fun" ;) and because for a while there, people were interested in hiring me to work on it. But that's dried up (as has my available time for such things). So, my first instinct is to say: "sure, go for it!".
However...
A) I'd like the other current co-maintainer, ezra-g to have a chance to chime in with his thoughts, concerns, intentions and wishes.
B) I'd like to seriously discuss if it's really a good idea to continue to maintain all this code, or just put some energy into a migration path and then help signupentity (or whatever it's called) mature and develop.
C) If you're going to become a co-maintainer, I think it'd be wise to start by focusing on bug fixes and getting a 7.x-1.0 release out the door before working on any major restructuring or new features.
Thanks again!
-Derek
Comment #2
jerenus commentedDerek,
Thank you for your reply. There is a few days from the release of this issue. I think I may need to add some ideas. Like you said that if I'am going to become a co-maintainer, bug fixes and 7.x-1.0 release out is the main work at the beginning. In addition, I would close attention to the Drupal 8. And I will try to use better entity on this project. Furthermore, I'm taking the time to write the Signup Services module which is based on Signup module and Services module. I will also add more rules in the signup core module. Although only a beginning, I think that will be a good start. This module has a lot of work to do, but it stopped now. I hope it gets better, so I'll try my best to do it if I can get this chance.
Thanks.
Jerenus
Comment #3
dwwThanks for the reply. I'll try to track down ezra-g via other channels, since he's apparently not seeing this issue on its own. ;)
Cheers,
-Derek
Comment #4
ezra-g commentedHi Jerenus,
Thanks for offering to help!
It would be great to see you demonstrate your knowledge here by participating in the queue through reviewing and writing patches. Once you've done that, please update the issue here.
Comment #5
jerenus commentedHi ezra-g, dww
Very sorry for the late reply. In the process of resolving previous issues, I summed up the following questions.
1, A large number of patches can't be reviewed. The consequence of this problem is that there will be a lot of repetitive work for reroll.
2, Now there is no clear direction of the development of signup module. So except repair BUG, the module can not be explicitly formulated milestone of development progress.
3, Another problem is the slow updates, and the stable version has not been released. In this case, Fewer and fewer people are willing to continue or begin to use this module. At the same time, we lost a lot of contributors.
4, Development version of the code is a bit confusing now, the file path is not very clear and well-organized.
For these problems, I propose the following ideas.
1, Giving at least one active managers. As I apply before, if the community felt that I might be able to help on this module, I still really want to be this module's co-maintainer.
2, I think the most important thing is to help the module slimming now. Without damaging the function and use it, we need to put the directory structure more clearly.
3, In this process, there will be a lot of problems and unexpected. Problems will be raised by the community, and we can efforts together to solve and improve this module.
4, Stable version should be release, while it seems still far from stable version. But I believe that as long as people keep contributions, this module will develop good.
I know the rules of Drupal is Do-ocracy. But there are too many not critical issues for this module. We can first strive to build the module and prepare for the upcoming Drupal 8. Then come back around and fix the remaining issues before. So that we can have more contributors and more time.
Now, I hope to be the co-maintainer of this module. Then I can put some of my previous contribution patchs and others' to the right place and do what I mentioned above. Without our community, we are unable to maintain a simple module.
Thanks!
Jerenus
Comment #6
lightsurge commented@dww #1
I presume you mean Entity Registration module? I'm finding it difficult to move to that module. It seems based around registrations just being registrations, not bound to specific datetimes, so essentially you could register onto anything, not just content with a date. So it doesn't do the nice out of the box things that signup does, like send reminders close to a date, or close signups when an event has past.
The equivalent to uc_signup, commerce_registration, also seems even less mature in terms of preventing over-booking.
And both in general just don't seem to do as much for events out of the box.
Don't mean to hijack this thread, just wanted to say I miss this module ;)
Comment #7
igorik commentedHi Ezra, Dww, don't you think that it is already time to add some maintainer for this project?
If Janus is still available, it can be good start.
Much better as no maintainer now.
I found entity registration very interesting, but rough on edges, and in some functional ways too and very user unfriendly.
On the other side, signup was always very user friendly with its simple signup node form, views, etc.
Maybe in the future there can be good benefit from both these modules, or maybe there will come something like entity signup and it will be much better than entity registration.
I think nobody nows what comes, now it is time to wake up and just open door for new maintainer :P
thanks to everybody for their inputs.
Comment #8
jerenus commentedYes, strongly agree. And I am still available. We all hope that this module can wake up. So I will be very happy to contribute to this great module.
Comment #9
igorik commentedComment #10
igorik commentedComment #11
jerenus commentedThe maintenance status is still actively maintained, but the last commit of this module is at "January 22, 2014 8:47" for 6.x-1.x. We don't want to see this module going to dead. As I said two years ago, I still available for maintain this project. Seem we still have a few projects' feature based on this module. Because the lack of management of this module for a long time, most of the patches need to be rerolled... I really want to help this module coming back.
Comment #12
jerenus commentedComment #13
SeanA commentedThere are quite a few patches that need to be reviewed. I humbly suggest starting there.
https://www.drupal.org/project/issues/signup?status=8
Since there haven't been any changes in a while, most of the patches probably still apply. Or can be easily rerolled.
Comment #14
avpadernoComment #15
avpadernoComment #16
avpadernoI am closing this issue, as there haven't been follow-up actions as per Taking over unsupported (abandoned) projects (which isn't just about unsupported or abandoned projects).