-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add maintainers #127
Comments
@taz77 That's great to hear. The most active maintainer is @WengerK right now. I would say the process would be to make some pull requests (with passing tests -- if that is still possible) have them be merged by @WengerK and then apply for maintainership? [I see you already made pull requests] I am generally okay to add maintainers, but as many rely on this module obviously we need to be careful there as well ;). @WengerK Thoughts? |
I'm more than open to have some help to maintain this project ^^. Indeed, we have to be quite careful when changing anything on our API to prevent breaking change. Or release some breaking change version but a lot of people use dev-master as dependency (unfortunately) Also, for now, I would say we should focus on #126 to fix our tests CI. What do you think @taz77 - would you help me on this PR ? I'm still struggling with Drupal 8 / Behat tests ... it's the only test failing which prevent me squashing & merge this PR. |
I maintain a lot of Drupal modules on Drupal.org and that is what I use Drupal_TI. I been using Travis because D.O's homegrown Jenkins wasn't that user-friendly. Yes, be glad to help with #126 Here is my D.O profile: https://www.drupal.org/u/perignon |
@WengerK Faster releases will fix the dev-master dependency you are seeing in the Packagist stats. |
Many people rely on this module. What is the process of becoming a maintainer so that issues are addressed quickly?
The text was updated successfully, but these errors were encountered: