Project organization

[nicoulaj]

Related: sorin-ionescu#1239

Hi guys,

This project has been created a couple months ago and it has not received much love (last commit one month ago, pull requests are not answered).

I got pinged by confused users on IRC and twitter, so I think this project organization needs to be clearly defined, and I suggest the following actions:

• Clearly define who are the project leaders Clearly define who are the project leaders #43
• Clearly define what are the project goals (maintenance only, new features ?) Define the goals of this fork #44
• Clearly define how contributions can be made and accepted (what it accepted, who can merge, review process ?) PR approval process #41
• Make all of this appear clearly in the README Clearly define who are the project leaders #43 documenting PR approval process defined in #41 #45
• Copy issues and PRs to this repo (there are tools for this, eg: https://github.com/google/github-issue-mover) community fork: pending issues and PRs from the original repo #1

[facastagnini]

Hey guys!

Sorry that I went silent for a month, but I took time off to travel. I have been dedicating some time in March merging features and fixes, and I will continue doing so. I will be addressing @nicoulaj 's concerns in the coming weeks.

EDIT: I am back :)

[Aeon]

@facastagnini I think, as discussed on sorin-ionescu#1239, it would be great to have a team of maintainers, so it's not blocked on one person's business/interest level

[johnpneumann]

Agreed on above and would be willing to dedicate time to assist with things where I can/necessary especially given that the previous repo was "abandoned" and I really enjoy prezto over the alternatives that I've found.

[paulmelnikow]

I'd be happy to help with triaging and migrating issues and PRs from the old repository.

Have already started poking at them, see sorin-ionescu#1242 (comment) .

[nicoulaj]

I have invited both of you to the team of committers. Also, I have removed 4 other initial committers who have not given any sign of life.

The current team is:

• @facastagnini
• @johnpneumann
• @paulmelnikow

If you want to join the team, please speak up!

[paulmelnikow]

Thanks! Look forward to helping.

[johnpneumann]

Awesome! I'll probably be sparse this week, but I'll try and get things in either early morning or late night.

[dvcrn]

Also, I have removed 4 other initial committers who have not given any sign of life.

Apologies, things have been unexpectedly busy work-wise here. I'm hoping to help in the future though!

[facastagnini]

I just created #41 to formalize some guidelines about PR approval.

[facastagnini]

related #38

[johnpneumann]

We should also start labeling issues, so we can track down what's a bug, what's a question and/or conversation, etc.

[paulmelnikow]

How about Bug, Feature, Question, and Project to start? We could use Project for threads like this one, #3, etc.

[johnpneumann]

Also think that a bikeshedding label would be useful so that someone doesn't get sucked into a rabbit hole of things that hurt their brain with no end result.

[paulmelnikow]

Opened #44 to discuss the project goals.

[paulmelnikow]

Accepted is a nice label to put on a bug or feature ticket, to indicate that we agree the functionality should be added / fixed. The ESLint project uses it. Having vetted tasks makes it easier for new contributors to find a way to plug in.

Looks like we will need to ask @nicoulaj to create these labels.

[paulmelnikow]

@nicoulaj would you please:

• Add "project"
• Rename "help wanted" to "accepted"
• Rename "enhancement" to "feature"
• Remove "invalid" and "wontfix"

Added: nm, looks like we have access

[facastagnini]

I have been updating @nicoulaj's top comment to clearly indicate where each bullet point is being address.

[paulmelnikow]

@johnpneumann I added a "needs bikeshedding" tag, taking a cue from ESLint, to indicate the thread is going to be a deep dive. Is that what you have in mind?

[johnpneumann]

@paulmelnikow - Yeah that works. Can we change it so that there are no spaces in labels? Underscore or dash to separate words. I know that it degrades readability to a certain degree, but it makes it easier for scripting against the api (say if we wanted to migrate all issues from sorin to here and label them, from_sorin or transferred_from_sorin).

[paulmelnikow]

@johnpneumann could we touch base at https://gitter.im/zsh-users/prezto ?