You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After investing in docsify by creating docsify-themeable and docsify-tabs, it would be disappointing to learn that the project is no longer maintained. Some signs of life would go a long way towards motivating others to sign on as maintainers (myself included) if that's what's needed.
Perhaps as a supporting team member, but not as the sole maintainer.
As I mentioned above, seeing some signs of life—even if it's just base-level maintenance like merging PRs and addressing only critical fixes—would help motivate myself and others to lend a hand.
If you were willing to commit to base-level maintenance of the project moving forward, I would be willing to assist with the effort. We can work together to define exactly what "base-level" means and how to handle existing issues and PRs, as well as incoming issues and feature requests.
Given that there are zero maintainers now and no work is being done, putting a plan in place that involves even just a few hours per month would breath some life back into the project.
Sorry for late reply...
I have invited you to join the organization, then if you have any questions you can contact me via email(cinwell.li#gmail.com) or telegram(cinwell_li).
@QingWei-Li I'm in a similar position as @jhildenbiddle in that I'm making a variety of plugins and have just started using docsify for all the things. I would like to help where possible as a supporting member (not sole maintainer) as I want docsify to thrive!
If you were willing to commit to base-level maintenance of the project moving forward, I would be willing to assist with the effort. We can work together to define exactly what "base-level" means and how to handle existing issues and PRs, as well as incoming issues and feature requests.
I actually asked a similar questions, the answer is quite short ;) #754 (comment)
I would like to discuss which policy we want to drive for docsify.
For instance: I've created this pull request 11 days ago and assigned the core members to it. I still got no feedback yet.
Are too busy to check? That means either we wait until someone has time or can I merge my own pull request? If the latter, then we should define some rules and add them probably into the CONTRIBUTING:md
For instance: provide tests, explain which problem is solved, etc.
@timaschew I'm not sure who is part of the group core, or how to check.
Given I have not seen a post from @QingWei-Li I assume they are still looking for maintainers. I'm certainly open to helping, but don't have the skill to be a sole maintainer at this time (open to guidance).
I like the requirements that repos have where you need at least 2 reviewers before merging. DefinitelyTyped has cool tooling that automatically pings anyone who has previously edited the code that is being changed, so that people who know the context of the changes can review it. Maybe we consider adding something like that here. (I have not set it up before, but it works well on their repo - https://github.com/DefinitelyTyped/dt-review-tool)
I think we should definitely review the rules and guidance in the Contributing guide and the GitHub templates. I have spent some time doing that with other projects recently so happy to give that a go.
Oh, actually I was expecting to see you @jthegedus and @jhildenbiddle in the core team, but you are not part of it (yet).
Members are currently:
QingWei-Li
cheng-kang
timaschew (me)
Are you okay if I add you (@jthegedus and @jhildenbiddle) to it, so it will be easier to reach out to you all via @core.
I'm certainly open to helping, but don't have the skill to be a sole maintainer at this time (open to guidance).
Sure, that's enough for now.
I like the requirements that repos have where you need at least 2 reviewers before merging.
But this only works if the feedback delay is short. So waiting longer than a week for instance doesn't work/scale. I mean it doesn't help I think if people are busy with other stuff or having other priorities – and that's fine. But in this case we shouldn't expect to get feedback from them.
Seeing so many great projects using Docisfy is really inspiring, I would love to help the team maintain this awesome software! As a result I would probably deprecate Docute too.
paulmelero, QingWei-Li, sansnom, felangel, upupming and 2 more
We've just started using docsify in our companies internal projects, and I'm willing to include it in one of my open source projects. I'd love to be part of it to keep it healthy.
I just stumbled on an issue with dependencies in docsify-cli and I could easily make a PR for that.
Hi, folks....
First of all, this is really an awesome project and I am using this for one of my projects (https://mern.netlify.com/#/),
I am willing to chip in here and I think I can help with the docsify-cli as I have some past experience in working with CLIs (webpack-cli, https://github.com/anikethsaha/create-web-app).
So here, if you guys need help with the CLI , I can provide some 👍
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
jhildenbiddle commentedon Oct 11, 2018
What is the current maintainer status of docsify?
After investing in docsify by creating docsify-themeable and docsify-tabs, it would be disappointing to learn that the project is no longer maintained. Some signs of life would go a long way towards motivating others to sign on as maintainers (myself included) if that's what's needed.
QingWei-Li commentedon Oct 12, 2018
@jhildenbiddle
Currently no maintainer. Do you want to try?
jhildenbiddle commentedon Oct 12, 2018
Perhaps as a supporting team member, but not as the sole maintainer.
As I mentioned above, seeing some signs of life—even if it's just base-level maintenance like merging PRs and addressing only critical fixes—would help motivate myself and others to lend a hand.
If you were willing to commit to base-level maintenance of the project moving forward, I would be willing to assist with the effort. We can work together to define exactly what "base-level" means and how to handle existing issues and PRs, as well as incoming issues and feature requests.
Given that there are zero maintainers now and no work is being done, putting a plan in place that involves even just a few hours per month would breath some life back into the project.
cheng-kang commentedon Oct 18, 2018
I'm interested in joining the team 🙋♂️
Docsify is amazing!
QingWei-Li commentedon Oct 23, 2018
@cheng-kang 🤩Cool
Sorry for late reply...
I have invited you to join the organization, then if you have any questions you can contact me via email(cinwell.li#gmail.com) or telegram(cinwell_li).
jthegedus commentedon Jan 28, 2019
@QingWei-Li I'm in a similar position as @jhildenbiddle in that I'm making a variety of plugins and have just started using docsify for all the things. I would like to help where possible as a supporting member (not sole maintainer) as I want docsify to thrive!
timaschew commentedon Jan 28, 2019
@jhildenbiddle
I actually asked a similar questions, the answer is quite short ;)
#754 (comment)
timaschew commentedon Mar 3, 2019
@QingWei-Li @jhildenbiddle @jthegedus @cheng-kang
I would like to discuss which policy we want to drive for docsify.
For instance: I've created this pull request 11 days ago and assigned the core members to it. I still got no feedback yet.
Are too busy to check? That means either we wait until someone has time or can I merge my own pull request? If the latter, then we should define some rules and add them probably into the CONTRIBUTING:md
For instance: provide tests, explain which problem is solved, etc.
What do you think?
jthegedus commentedon Mar 4, 2019
@timaschew I'm not sure who is part of the group
core
, or how to check.Given I have not seen a post from @QingWei-Li I assume they are still looking for maintainers. I'm certainly open to helping, but don't have the skill to be a sole maintainer at this time (open to guidance).
I like the requirements that repos have where you need at least 2 reviewers before merging. DefinitelyTyped has cool tooling that automatically pings anyone who has previously edited the code that is being changed, so that people who know the context of the changes can review it. Maybe we consider adding something like that here. (I have not set it up before, but it works well on their repo - https://github.com/DefinitelyTyped/dt-review-tool)
I think we should definitely review the rules and guidance in the Contributing guide and the GitHub templates. I have spent some time doing that with other projects recently so happy to give that a go.
timaschew commentedon Mar 6, 2019
Oh, actually I was expecting to see you @jthegedus and @jhildenbiddle in the core team, but you are not part of it (yet).
Members are currently:
Are you okay if I add you (@jthegedus and @jhildenbiddle) to it, so it will be easier to reach out to you all via
@core
.Sure, that's enough for now.
But this only works if the feedback delay is short. So waiting longer than a week for instance doesn't work/scale. I mean it doesn't help I think if people are busy with other stuff or having other priorities – and that's fine. But in this case we shouldn't expect to get feedback from them.
timaschew commentedon Mar 6, 2019
@QingWei-Li I wanted to add @jthegedus and @jhildenbiddle to the core team but I can't. Can you do that or give me maintainer permissions, please?
32 remaining items
egoist commentedon Oct 23, 2019
Hi @QingWei-Li @timaschew author of https://github.com/egoist/docute here
Seeing so many great projects using Docisfy is really inspiring, I would love to help the team maintain this awesome software! As a result I would probably deprecate Docute too.
santoshyadavdev commentedon Oct 23, 2019
Count me in .
Zielak commentedon Nov 5, 2019
We've just started using docsify in our companies internal projects, and I'm willing to include it in one of my open source projects. I'd love to be part of it to keep it healthy.
I just stumbled on an issue with dependencies in docsify-cli and I could easily make a PR for that.
anikethsaha commentedon Nov 6, 2019
Hi, folks....
First of all, this is really an awesome project and I am using this for one of my projects (https://mern.netlify.com/#/),
I am willing to chip in here and I think I can help with the docsify-cli as I have some past experience in working with CLIs (webpack-cli, https://github.com/anikethsaha/create-web-app).
So here, if you guys need help with the CLI , I can provide some 👍
anikethsaha commentedon Nov 16, 2019
cc @QingWei-Li @timaschew @jhildenbiddle
Is there any way to contact you guys apart from github ?
I think we need someone to merge PRs of docsify-cli. as there are quite a good number of security alerts there in the dependencies.
felangel commentedon Nov 16, 2019
@anikethsaha just merged the security PRs from dependabot 👍
anikethsaha commentedon Nov 16, 2019
@felangel are you guys looking for new maintainers ?like is this issue resolved ?
felangel commentedon Nov 16, 2019
@anikethsaha I'm not sure as I only recently joined the organization
anikethsaha commentedon Nov 16, 2019
@felangel okay will wait for others to respond 👍
jamesgeorge007 commentedon Nov 18, 2019
@QingWei-Li I would love to collaborate on the
docsify-cli
project. Just shooted a couple of PR's 🎉stale commentedon Feb 4, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.