As I've seen some users request patch commitment on a branch of the project I've been working on #241155: Root Title, Min. Level, Limit and Dept and people have suggested me to take this step as seen on this forum entry, I formally requesting to be a co-maintainer of this project. This would be a first experience so I will try my best to abide by the principles already instated and am more than willing to help develop and follow rules. I'm also willing to sit back and just be a junior co-maintainer ; whatever it take to make the cut, simply tell me or point me to a guideline.

Thank you for your consideration. I'd appreciate explanations along with your reply.

Comments

David Lesieur’s picture

Hi William,

First, I want to thank you for your enthusiasm towards the project. I've been swamped with other projects lately and I'm aware that I have not been as good a maintainer on this module as I would like to be. However, Menu Trim is not abandoned.

Although you have shown great openness about all of my comments, which is great, I found it very difficult to communicate with you and get understood. I felt that you did not understand the normal patch contribution process. I did not manage to untangle all your submissions, so at some point I gave your issues a lower priority, which is one of the reasons why you did not hear much from me lately. You kept editing your previous comments on issues, and have submitted either complete rewrites of the module or multiple inter-dependent patches, which made the issue queue unmanageable.

My understanding is that you need and are looking for a mentor, which is also great, but unfortunately I only have time to give a few advices once in a while, and cannot provide help on a continuous basis.

Because of the above reasons, I feel I cannot, at the moment, grant you co-maintainer status. I feel sorry because I know that you really want to do everything right. I sure hope that my comments do not sound too harsh. You have shown great willingness to learn, and I'm sure that if you could find someone with a just little more time to work with, things could go fine.

Note that I think you have worked on valuable features, and that I still intend to review your patches when time allows.

Best regards,
David.

DynV’s picture

In this case, would you please then grant anyone else you deem knowledgeable and/or responsible enough as a co-maintainer ? I've been waiting for quite a while to have my contributions reviewed and, as stated in my first post, the consensus is my contributions should move forward. I'm editing my comments as I'm not a native English speaker so I simply rephrase them but seldomly change their signification.

Your comments are not too harsh, they're realist, I'm not fully ready to be a maintainer and stated so. I was only asking to be a junior co-maintainer. Now that I know you had frustrations about me and didn't even shared them with me, I see we'd have trouble working together, I like things to be on the table which is why I showed the forum entry with my frustrations, I think it's being considerate. Please realize this project haven't moved forward for almost a year now and I'd like my hard work to be integrated in the community as in this patch state, only a tiny portion of people interested in this module are using my contributions.

I've been thinking about forking this module for a while now and, as I'm sure you're really busy, gave you plenty time to make the module go forward. I think it would be great if you could pretty soon find time to maintain the module or find a suitable co-maintainer. I hate forks but I hate more having proper hard work wasted. Please give me your thoughts on the module next move and time frames of those.

David Lesieur’s picture

I'm always open to grant CVS access to other interested and capable parties, and have done so on other modules. So far, no one except you has shown interest in taking such responsibility for Menu Trim.

Note that I too like things to be "on the table", and that's the reason I took the time to explain my point of view here. Saying I had "frustrations" about you is an overstatement — I just did not find the time to help more on getting your issues forward.

The module is currently stable with no critical issues. The next steps are to review patches/issues when time allows.

cog.rusty’s picture

Do you think it would be practical to give DynV access under the agreement of using a new branch, you know, "new features", "experimental" etc?

David Lesieur’s picture

My impression is that a sandbox would be a better place for experiments. He will have to get a CVS account first, though.

AjK’s picture

DynV CVS account application has been approved. I leave it for you all to decide what to do next.

DynV’s picture

@AjK thanks for taking the time you took to evaluate my case. :)

David Lesieur’s picture

Status: Active » Closed (won't fix)