Hello,

I was wondering if this module is still being maintained. The latest release of this module (7.x branch) is still unusable, and I would like to help push this module forward due to the intensive use of this module in my current project. I'm also willing to take this module over completely if you prefer. Thank you.

Comments

Title:Offer to help maintain this moduleOffer to help maintain File (Field) Paths
Project:File (Field) Paths» Drupal.org webmasters
Version:7.x-1.x-dev»
Component:Miscellaneous» Project ownership

Moving queues as per Dealing with unsupported (abandoned) projects as it's been a while. Please change the owner of File (Field) Paths to one of us. Thanks!

Status:Active» Postponed (maintainer needs more info)

Can either of you confirm whether you contacted the current owner via their contact form? That's a necessary step in the abandoned project process.

Just did. Guess we'll have to wait for two weeks before taking any further step.

Status:Postponed (maintainer needs more info)» Fixed

Best practice would be to email me before you open such an issue.

And no, it's not abandoned.

Feel free to contact me if you believe you could offer a hand as a co-maintainer.

Deciphered, I think you're mistaken about best practice. The documentation at http://drupal.org/node/251466 starts with opening an issue, with emails encouraged after linking to the issue. That's what happened here.

@sreynen,

I don't care what the documentation says, common curtesy would be to try to reach out to someone personally before initiating a takeover request, it's just being polite.

Status:Closed (won't fix)» Fixed

Deciphered, you appear to be surprised by this issue, which suggests you maybe aren't subscribed to notifications on your project. I encourage you to remedy that problem by subscribing to the project's issues. I also encourage you to review the Drupal code of conduct and consider how it might apply here.

With a clear objection from the current maintainer, we're not going to add any new maintainers to the project, so this issue is effectively resolved.

Status:Fixed» Closed (fixed)

Let's close it since we won't get any further with this.

Status:Closed (fixed)» Fixed

I'm not subscribed to the notifications anymore, you are correct, that is because I haven't had time to deal with the issues, also why in my emails to Jeffrey C I was perfectly willing to accept him as a Co-maintainer if he was able to prove himself, something he seems to pretend I didn't offer, instead it's easier to attack me in public.

I still stand by the fact that contacting a developer personally before opening this type of issue is common curtesy, it gives the developer the ability to deal with the request personally instead of needing to escalate the issue, if the developer does not respond to the personal contact then it makes sense to open said issue.

I'm not even going to touch on any of the other things that have been said here and just assume they are based on misunderstanding of the offers I made or offence that I asked proof of competency, but I will say the following:

I have not abandoned this module, but it's not the highest priority for me at the moment. I would absolutely love a co-maintainer, but I'm not just going to give anyone commit rights because in the past that has caused the module to become less stable and introduce many more issues, so if anyone wants to become a co-maintainer has to be willing to prove they are capable. The majority of requests I've received of recent are from developers who are barely able to write a patch, let alone maintain a module.

As for closing an issue, if an issue is finished you mark it as fixed, if there are no follow ups within a 2 week period it will be marked as closed automatically. You should not mark an issue as closed (fixed) yourself.

As an aside, there is also, and has been for a while, ongoing development for this module that will deal with the majority of the issues, there's just nothing that I'm am yet willing to commit.

Status:Fixed» Closed (won't fix)

This is more "closed (won't fix)" than fixed, since the original request was rejected.

For what it's worth (I suspect not much, but you never know), I deal with nearly every project ownership issue, and I've never seen another other project maintainer interpret these issues as personal attacks.

The personal attack wasn't the issue, it's comment #7 that I take as an attack, especially as that was made after I sent an email to Jeffrey C stating that I'd be happy to accept him as a co-maintainer, which I've still said in emails since his comment, all I ask is that he show me that he will care for the module, I don't think that's too much to ask of anyone who wants to take over or co-maintain a module.

Since I've got no response from him I have to assume he doesn't want to co-maintain the module after all or he doesn't believe he needs to answer to me, either way it is disappointing.

@Deciphered: I clearly understand that you don't want to grant commit access blindly (to be honest, I actually had similar experience in the past, and I end back taking the permissions back), but I'm also maintaining several modules (check my profile) so I believe you can rest assured about this part. I don't have much time to maintain the issues too but at least I can fix those critical issues (and non-critical ones that made the module unusable). It's, however, an important thing to think that since you're no longer to spend time on the project, if you should let someone do this instead. I just don't like your tone when you said you didn't care about the documentation, I might sound too harsh and I apologize too if that offended you. I really suggest we all show respect to everyone (especially webmasters since they know way more about the standard process than common users and strive to keep everything on D.o in order everyday).

Thanks @sreynen :).

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.