-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Project still alive? #724
Comments
+1 |
The project not being worked on is not an "issue" with the code, and posting observations like these to the issue tracker is just cluttering it up. If you want to ask the maintainer about this project's future, please just contact him directly. |
@webbedspace i feel that it's important to raise the issue to make other who probably are thinking the same, aware of whats happening. I have many times seeked the issuetracker to see if this question have been asked, and if a response have been made. Sometimes this issue can spark the contribution spirit in someone who will fork the project and keep it maintained somewhere else. Its all about sheeding light on an issue with the repository. |
👍 |
@Snorlock Good point. And since this project's last commit would be nearly 7 months ago ( and 127 PRs waiting to be merged ), it's easy to doubt that if this project is still on the track. |
Yeah I believ it myself, but I want a comment from @chjj |
+1 |
i'd say this project is dead.. can anyone recommend a reliable fork to switch to? If not, does anyone have a day or two free to create one and work through the pile of outstanding PRs? |
👍 |
@75lb Not a fork, but https://github.com/markdown-it/markdown-it is the most active markdown plugin for js right now, it was a fork of https://github.com/jonschlinkert/remarkable. |
How about https://github.com/showdownjs/showdown? |
The Code doesn't age. |
@wifiextender it is kind of sad that now there is a code vulnerability in it and we can't get that fixed. Is there an ability to move this to another maintainer? npm rights and such @chjj |
@chjj vscode is using this and they are moving away from it because of lack of movement on the project... |
+1 |
Please see #756 |
Closing for cleanup |
With this many issues and PRs, I wonder if the project still lives when its 7 months since last update?
The text was updated successfully, but these errors were encountered: