Project dead? #192
Labels
Comments
|
I hope not. It didn't seem to be a slow fizzling out, either—he was pretty active, until he wasn't. Hope he's doing alright. |
|
He seems pretty active on his twitter account. Maybe we can contact him there. I can't, I don't have a Twitter account. |
|
I sent him a DM there but didn't get a response :/ |
|
he seems quite involved in war comments. @dominickpastore can you try again ? |
|
Bumping for interest |
|
If someone else wants to message him, feel free, but I prefer not to send him more messages off-platform. |
|
Has someone plans to create a fork if it? |
|
I have a fork with #175 for my Markdown editor MarkdownEdit but I'm not actively developing it |
danakj
added a commit
to danakj/subspace
that referenced
this issue
Aug 17, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
danakj
added a commit
to danakj/subspace
that referenced
this issue
Aug 18, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
danakj
added a commit
to danakj/subspace
that referenced
this issue
Aug 18, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
danakj
added a commit
to danakj/subspace
that referenced
this issue
Aug 18, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
danakj
added a commit
to danakj/subspace
that referenced
this issue
Aug 18, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
danakj
added a commit
to chromium/subspace
that referenced
this issue
Aug 18, 2023
We formed md4c to add the functionality into the parser, so point the git submodule to that fork. The md4c project seems to be unmaintained which is why we did it that way. mity/md4c#192 Then move markdown parsing to the generate step so that we can track repeated self links per-page and increment a counter on each one to make them unique. Add missing Result::and_then() to support this use of Result. It still needs tests (and the Copy overload).
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm following the project for some time now and the creator hasn't commited for over a years now neighter has he wrote any comments on issues/pull requests.
That's why I'm windering if this project is dead.
The text was updated successfully, but these errors were encountered: