Request to co-maintain File (Field) Paths

+1 for @webwarrior to be added as co-maintainer. I was about to avoid using this module on a new site build until I saw this thread.

+1 for @webwarrior. Someone needs to revive this great module.

Please do take some help from the community. This module needs some love for Drupal 8.x and having some more people involved in triage / testing / development would be great.

HI,

I have obviously been absent for some time now, this is 100% understood. I can't guarantee my resurgence until late this year, but I am also wary to hand over the module without having some involvement.

@webwarrior, please get in contact with me via the D.o contact form, or http://twitter.com/Decipher

For 100% clarity,

I'm more than happy to hand over control of this module to anyone who is willing to add major test coverage for the existing functionality, demonstrating that they understand how the module is meant to work, and ensuring that any future development will not break the module for the large number of users.

I haven't had time to give my time away for free for a very long time, and that's unlikely to change, so I do want to have someone maintain this module, but I'm unwilling to hand it over if that causes damage to the module.

Cheers,
Deciphered.

I haven't had time to give my time away for free for a very long time, and that's unlikely to change, so I do want to have someone maintain this module, but I'm unwilling to hand it over if that causes damage to the module.

So @webwarrior is the wrong one?
Maybe another one could help here ...

Hey folks, Let's not throw the baby out with the bath water!

Having Deciphered at the wheel is one thing but if he is not at the wheel, I'd prefer *someone* at it to nobody at all. Especially as the module is not security covered at present.

#8

So @webwarrior is the wrong one?

See #7

I'm more than happy to hand over control of this module to anyone who is willing to add major test coverage for the existing functionality, demonstrating that they understand how the module is meant to work, and ensuring that any future development will not break the module for the large number of users.

If webwarrior or anyone else can provide patch(es) for the above that would be a good start.

So a goal of becoming the comaintainer should be to help stabilize, finish and improve the module. The current maintainer has requested that any new comaintainers work on test coverage, which is fair. I'd recommend that anyone who's actually interested in contributing to the module please take some time to do the following:

• Triage the issue queue for each branch.
• Come up with plan issues for new releases for each branch, if there aren't ones already.
• Work on getting existing patches to an RTBC state.
• Work out issues that should go in new releases, list the plan issues as those issues' "parent"; this helps folks understand what the plan is for future releases, and gives the maintainers some reassurance that the bigger picture is being considered.
• Learn to write tests and write patches to add test coverage; there are blog posts and videos for this, and I'd be delighted to help folks do this on the Contrib Half Hour meetings :-)

At the same time, maintainers need to be willing to share the reigns with others who are willing to put out the effort on this, especially when they're not doing any work themselves, to do otherwise is limiting the module thus the community's chance to grow and improve, and does a disservice to everyone.

I'm still interested to co-maintain the project. I had fixed the security issue for the project, joined forces to fix a bunch of tests failures here #2923206: Fix tests and tried to move forward some issues on the issue queue until somehow lost my permissions to manage the repo and the releases.

@Deciphered: It seems like voleger's efforts fit your criteria, any reason to not let him continue?

Hi @voleger,

I've sent you a DM on Slack, happy to chat.

@DamienMcKenna 100% agree.

My lack of response wasn't out of unwillingness, it was out of means of communication and relevant notifications. D.o <-> Slack @mentions notifications would be lovely ;)

Willing to talk to any who wish to discuss this matter further via Slack when time and timezones permit.

@voleger is active as a maintainer, so closing.