I've recently become the maintainer of https://www.drupal.org/project/markdown and have been looking which JS based markdown editors are the "best" out there.

I've been debating whether to use SimpleMDE or Editor.md for https://markdown.unicorn.fail.

I think I've decided that Editor.md is the better choice.

I'd like to make this the "de facto" editor for Markdown in Drupal, but it's going to need some love moving forward.

I'll likely be providing a refactoring patch soon.

Comments

markcarver created an issue. See original summary.

bhanuprakashnani’s picture

bhanuprakashnani commented

Am I eligible for becoming the co-maintainer? I really have interest in developing modules and working on them. Please let me know if it is possible. Thank you.

a65162’s picture

a65162 commented

Editor.md is a good markdown editor and I attempted to add the excellent JS to Drupal; however, I'm not good at PHP to make it works correctly on Drupal. I'm happy to see your request to become a maintainer and I have assigned the permission to you. Please take a look.

a65162’s picture

a65162 commented
Status: Active » Fixed
bhanuprakashnani’s picture

bhanuprakashnani commented

Thank you so much. Let me know whenever there is something to do. Really look forward to work with you.

markhalliwell’s picture

markhalliwell
Primary language English
commented

Am I eligible for becoming the co-maintainer?

Considering that you are a relatively new user on d.o, we ask that you provide patches to a project before requesting maintainership. Also, FWIW, hi-jacking another person's request it's generally frowned upon.

For now, I have removed you because I will be making some sweeping changes/improvements. I don't want to risk us committing different work/ideas.

I welcome your participation in the issue queues though and look forward to reviewing code. Perhaps one day in the future you can help maintain this module.

bhanuprakashnani’s picture

bhanuprakashnani commented

Sorry, but I did not know that I was hijacking your request. Now I understood. Pardon me for my behaviour, but i was very happy to be the co-maintainer. I was going through the codebase for finding issues. I had no other wrong intentions. I really look forward to again become the co-maintainer. I have seen the issue queue but there are no issues related to Editor.md. Can you assign me some task so that I can have a chance to prove my skills please. Thank you for your concern and guidance. Ill go thorugh the link you mentioned above work according to it.

Thank you @markcarver and @65162

bhanuprakashnani’s picture

bhanuprakashnani commented

I am creating an issue of updating the readme with the troubleshooting section and adding the name of markarver in the section of maintainers. Is it advisable?

bhanuprakashnani’s picture

bhanuprakashnani commented

https://www.drupal.org/project/editor_md/issues/2956892
I have created an issue and working on it.

a65162’s picture

a65162 commented

For now, I have removed you because I will be making some sweeping changes/improvements. I don't want to risk us committing different work/ideas.

You are supposed to ask me before you removed @BHANUPRAKASHNAN who was accepted to be co-maintainer by me. I understand what you worry about, but it makes me really mad at your action. Don't do that again.

markhalliwell’s picture

markhalliwell
Primary language English
commented

I apologize if my actions offended you or appeared as if I was attempting to circumvent the "ownership" of this module from you.

That was not my intent.

No offense to @bhanuprakashnani, but casually asking to become a co-maintainer on my legitimate request (as I am the maintainer of https://www.drupal.org/project/markdown and wish to "marry" these projects) was not appropriate.

One of the primary reasons I opened this issue is because one of the ethos in the Drupal community is "collaboration rather than competition".

I did not want to create a new project when one already existed and my goal is to work with everyone to make this module even better.

As someone who has been working in and with the Drupal community for a decade, I recognize @bhanuprakashnani's eagerness to help but must also acknowledge their relatively "new" status. They are not yet familiar enough with the "ins and outs" of this community to understand what it truly means to be a project maintainer (in the Drupal eco-sphere).

There are a lot of nuances and "gotchas" that come with maintaining a project on d.o, the least of which are adhering to Drupal Coding Standards.

I was granted permission (by you) to administer/co-maintain other maintainers of this project. I simply felt it was within the purview of my newly granted status to redirect @bhanuprakashnani's desire to help with this project by guiding them towards are more patch based role (for now).

I will be opening a new issue shortly that will be the basis of the refactoring work I have been adamantly working on for https://markdown.unicorn.fail.

bhanuprakashnani’s picture

bhanuprakashnani commented

So when can I be eligible to become the co-maintainer? I am a new user, I accept. But I would become experienced if I get into new things and learn them I guess. Anyways thank you @markcarver. thank you @a65162 for the support. looking forward to work with this module. thank you.

markhalliwell’s picture

markhalliwell
Primary language English
commented

So when can I be eligible to become the co-maintainer?

There's no official "checklist" on how to become a maintainer.

Ultimately it's up to the current maintainer(s) to determine what "criteria" they choose as "eligible".

Personally, I tend to look at how fresh (new) they are to the community and what their code looks like.

Generally speaking, however, the most common way is to just help issues along with patches and reviews.

I have seen some become maintainers rather quickly due to their abundant help in a particular project's issue queue.

Over time, you can accumulate commit "credit" (git attribution) and issue "credit" (name in git commit messages) on your profile which will go a long way towards helping to affirm your experience (see my profile for an example).

As with many things though, most of it is just a matter of time.

bhanuprakashnani’s picture

bhanuprakashnani commented

Ok @markcarver. I will work for the module. At present there are no open or active issues for the module. I have got credits and commits for other module contributions. Assign me some work regarding this module if possible. Thank you.

markhalliwell’s picture

markhalliwell
Primary language English
commented

After I have done most of the refactoring, I will for sure :D

bhanuprakashnani’s picture

bhanuprakashnani commented

Thank you so much.

a65162’s picture

a65162 commented

I apologize if my actions offended you or appeared as if I was attempting to circumvent the "ownership" of this module from you.

The main reason is not about you avoid "ownership" of this module. You didn't tell me any reason before you have removed @bhanuprakashnani from this project, for he was added by me so I need to know why @bhanuprakashnani needs to leave. Your action is as same as @bhanuprakashnani's hi-jacking your request. It is not appropriate.

I agree with your point so I didn't add him back to the project. If you think he has any ability to maintain the module, just give him an opportunity to accomplish his dream :D.

So when can I be eligible to become the co-maintainer?

Well, you should follow @markcarver's advice. It would be better for you.

bhanuprakashnani’s picture

bhanuprakashnani commented

@a65162. Apologies for my action. And thank you for giving me this much support and considering my enthusiasm. I would never hijack any other's request. And yes I will follow markcarver's advice and fulfill my wish to become the co-maintainer of this module. Sorry and thank you to @a65162 and @markcarver. Looking forward to work with both of you.

Status: Fixed » Closed (fixed)

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