Add maintainers

[taz77]

Many people rely on this module. What is the process of becoming a maintainer so that issues are addressed quickly?

[LionsAd]

@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?

[WengerK]

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 https://github.com/LionsAd/drupal_ti/pull/126 to fix our tests CI. Once we would be able to trust our tests CI again, I'm sure it would be easier to maintain this project ^^.

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.

[taz77]

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

[taz77]

@WengerK Faster releases will fix the dev-master dependency you are seeing in the Packagist stats.