[Request & Discussion] Extended rights for volunteers to help supporting your `micro` project

[JoeKar]

@zyedidia

This issue shall be understood as a general request to officially support you and your project micro.
Currently we've a lot of issues and PRs open, but no capability to get them into an sufficient order. What I mean is, that maybe all or some specific people currently active in trying to support here will receive the right to add (existing) labels and maybe some priority (milestone) handling to been as efficient as possible to not doing things twice and get the things sorted in the right order.

micro is a very nice editor and has very interesting approaches and it needs to be frequently maintained. :)

[RichardFevrier]

I totally agree with @JoeKar.
Actually a lot of PRs open with people behind who took some of their time and deserve at least some communication 🙂
We are a lot to love this project ❤️ and hope that it continues to grow in a good way 😌

[zyedidia]

I'm sorry for the lack of communication. Unfortunately I've been focusing on other projects recently, and the time I devote to micro has been strained. It's a blessing that so many people devote time to working on micro and I regret often leaving posts without a response. I will try to respond to the recent PRs and issues this weekend and do some general maintenance. I'll probably make a new minor release with those changes next week.

I think adding labels and milestones would be helpful. If you or others (generally people who have been engaged on the issue/PR tracker) would like to take that on, I'll look into how to make that happen. Thank you for your patience and your help in the development of micro.

[pallaswept]

That sure is a stack of issues and PRs. It's nice to see you offer to try and sort it out.

Micro is fantastic, I'm very thankful for it, and next time I need to pop by the repo to check some docs, I hope to see it appear as less of a burden to its creator and contributors, who so kindly share their work with us all.

[JoeKar]

If you or others (generally people who have been engaged on the issue/PR tracker) would like to take that on, I'll look into how to make that happen.

Yes, I would definitely appreciate that. With the help of labels we can tag what's really a bug and need to be fixed earlier, what's a feature request and what's a general question only. With the help of milestones the project can benefit of some sort of priority handling per next release or something like that.

@dmaluka:
Since you're one who is very committed to the project what do you think about it?

[dmaluka]

Sounds good, I wouldn't mind having rights to put labels like "reviewed and can be merged" or "solved and can be closed" (as a substitute for the lack of the actual rights to merge PRs or close issues ;)).

[dustdfg]

I am absolutely agree with it. And I want to add one small notice. If I open issues/PR's tab (especially PR's) and see there fresh activities (2 month - today) without any comments, I start to think that project was abandoned by owner. It usually scares people. If I see least see there some labels, I am not so prejudice

[dustdfg]

@dmaluka @JoeKar
Hello! How do you manage your version that includes all the not merged PR's? Just bunch of merge commits?

[JoeKar]

Currently I've no own branch where I track my changes (used in the PRs), but usually this would be the way to go.

@zyedidia:
Friendly reminder, since nothing really changed so far. 😉

[dmaluka]

@dustdfg

How do you manage your version that includes all the not merged PR's? Just bunch of merge commits?

Yeah, just my local branch with a bunch of merge commits for the PRs I'm interested in. I was going to upload that to my fork so that others could just use it, but I've been too lazy for that.

[JoeKar]

Before we end up in more or less the same situation again after having the capabilities of labels/milestones and what ever.
How about directly adding merge rights and extended issue rights for at least some more trustworthy people (I don't count myself here 😉)?

I've still the trust that micro will benefit from combining all of our efforts/time from every supporter.

[dustdfg]

It looks like now micro is a repo of @zyedidia and doesn't belong to https://github.com/micro-editor organization.

Anyway what I found: repository roles for organization. I think Triage role is exactly what @JoeKar described when opened this issue. Also if Writer role is to permissive it can be restricted by branch protecting in particular via branch locking.

I am not sure if I my proposal is correct from point of view what github allows but I have to propose:

1. Start using Triage role
2. Separate branch where those who have Writer role will be able to push. It will be the only place where people with Writer role will be able to push...