Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Step one: Strategy for democratizing merges #10

Open
DrewMcArthur opened this issue Feb 19, 2021 · 8 comments
Open

Step one: Strategy for democratizing merges #10

DrewMcArthur opened this issue Feb 19, 2021 · 8 comments
Labels
Feature A Feature is a service that fulfills a stakeholder need.

Comments

@DrewMcArthur
Copy link

The first step (imo) is getting a protocol setup to democratize merging.

First issue we could practice on is licensing, issue #4. Here’s my first idea of how this might go, obviously subject to change and improvement (i’m hopping on the discord after i post this)

  1. Describe the issue and potential solutions
  2. Setup some timeline bringing us from formulating ideas for solutions, or full solutions if scope allows (like the license issue; easy to make a PR for each potential license)
  3. solutions should be linked to the original issue
  4. once solutions have been fleshed out, and we feel like we’re ready to proceed (how do we determine that? time? thumbs up?)
  5. then a countdown begins, or a deadline X days later is created. whichever PR has the most thumbs up by this deadline will then get merged, and all others related to the issue should be closed and link to the winner.

how’s that sound? any suggestions? i just typed that quickly on my phone to get the ideas out there so lmk

@literit
Copy link

literit commented Feb 19, 2021

I think that that would work

@DrewMcArthur
Copy link
Author

DrewMcArthur commented Feb 19, 2021

@adnmoh3 not really relevant to this issue, can you maybe ask in the discord, or somewhere else that’s being talked about? ty!!

@hackerncoder
Copy link

@DrewMcArthur Is there a discord?

@literit
Copy link

literit commented Feb 19, 2021

If there is a discord, can you add me? my username is w4e#3178.

@DrewMcArthur
Copy link
Author

@hackerncoder @literit so there apparently was, but then we crashed it. i never got on to see for myself, lol

@hackerncoder
Copy link

hackerncoder commented Feb 19, 2021

My idea:

An issue is created, people talk about it and give ideas for solutions. Once enough options has been proposed and talked about (again, how we do that?) a new issue for voting is created. If there are more solutions than the 8 emojies we should use comments where we vote using a specific emoji, otherwise we (can) define an emoji (you know it's gotta be rocket) for each of the solutions (in the post) and people react with the emoji corresponding to the solution they want to vote. This issue is for voting only, therefore it should link to the other issue where discussion takes place. Then the countdown starts (or however we decide when to end the voting).
The reason I create an issue instead of PRs is that it is more organized, keeping everything in one place where you vote is easier than having to keep track of however many PRs there are. This also keeps the PRs for actual PRs.

@zoox101
Copy link
Contributor

zoox101 commented Feb 20, 2021

Is this standard practice for any open source community? It sounds like an interesting idea, but I suspect it may be very difficult to implement.

@zoox101 zoox101 added the Feature A Feature is a service that fulfills a stakeholder need. label Feb 20, 2021
@hackerncoder
Copy link

hackerncoder commented Feb 20, 2021

I don't believe so.

I think most OSS don't go as much into having community in on decisions as is suggested here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature A Feature is a service that fulfills a stakeholder need.
Projects
None yet
Development

No branches or pull requests

4 participants