Skip to content

Looking for Maintainer #603

Closed
Closed
@QingWei-Li

Description

@QingWei-Li
Member

As you can see, this project is now rarely maintained. First, I think the project is basically stable. Second, I am busy recently.

So I am looking forward to joining the docsify team to help refine and fix the issue.

😇

Activity

jhildenbiddle

jhildenbiddle commented on Oct 11, 2018

@jhildenbiddle
Member

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

QingWei-Li commented on Oct 12, 2018

@QingWei-Li
MemberAuthor

@jhildenbiddle
Currently no maintainer. Do you want to try?

jhildenbiddle

jhildenbiddle commented on Oct 12, 2018

@jhildenbiddle
Member

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

cheng-kang commented on Oct 18, 2018

@cheng-kang
Contributor

I'm interested in joining the team 🙋‍♂️

Docsify is amazing!

QingWei-Li

QingWei-Li commented on Oct 23, 2018

@QingWei-Li
MemberAuthor

@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).

pinned this issue on Jan 23, 2019
jthegedus

jthegedus commented on Jan 28, 2019

@jthegedus
Contributor

@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

timaschew commented on Jan 28, 2019

@timaschew
Member

@jhildenbiddle

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)

timaschew

timaschew commented on Mar 3, 2019

@timaschew
Member

@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

jthegedus commented on Mar 4, 2019

@jthegedus
Contributor

@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

timaschew commented on Mar 6, 2019

@timaschew
Member

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.

timaschew

timaschew commented on Mar 6, 2019

@timaschew
Member

@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?

47 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @timaschew@jhildenbiddle@Zielak@TheGreenToaster@QingWei-Li

        Issue actions

          Looking for Maintainer · Issue #603 · docsifyjs/docsify