Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintainer(s) wanted. #266

Open
gangstead opened this issue Feb 25, 2016 · 6 comments
Open

Maintainer(s) wanted. #266

gangstead opened this issue Feb 25, 2016 · 6 comments

Comments

@gangstead
Copy link

It clearly isn't supported anymore, but they got the good name on npm.

@ashb
Copy link
Collaborator

ashb commented Feb 25, 2016

As has become clear @evilstreak and I no longer have the time or headspace to maintain this project

@eviltrout Would you be interested in taking over maintenance and ownership of this project? I'm not sure if Discourse uses this anymore, or if you are still involved in Discourse either.

@ashb ashb changed the title What should I be using instead of this package? Maintainer(s) wanted. Feb 25, 2016
@eviltrout
Copy link
Contributor

Discourse does still use it, but we are committed to upgrading to commonmark, so we will unfortunately be migrating to markdown-it this year :(

@gangstead
Copy link
Author

I continued looking yesterday and came to the conclusion that markdown-it was the way to go especially for speed and ease of setup, or possibly remark if you need a lot of customizability. You wouldn't know this from searching on npm it would seem that this package is the default, markdown-it is halfway down the page and remark is no where to be seen.

NPM uses markymarkdown which is just their wrapper for markdown-it.

It sounds like the best thing to do for the community is deprecate this package. If one of the owners could run:

npm deprecate markdown "This package is no longer maintained, please consider migrating to `markdown-it` or `remark` instead"

And also put that warning at the top of the readme it would save a lot of people accidentally using an outdated & unsupported dependency based on the results of NPM Inc's terrible search.

@bripkens
Copy link

bripkens commented Mar 9, 2016

Thank you for this information @gangstead. You just saved me from some Googling and GitHub pulse comparisons! :)

@benjycui
Copy link

@gangstead I read documents of markdown-it and remark. They are great, but if I need to filter code block from markdown or re-organize content, markdown-js is a better way to do so, for I can process Json-ML directly.

@ashb
Copy link
Collaborator

ashb commented Mar 22, 2016

@benjycui Since you're unknown to start with would you mind forking (and submitting some things as PRs) so we can get to know each other a bit first?

I really appreciate someone stepping up and offering to take over, but I don't want to just hand over control to someone brand new. I hope you understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants