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

Establish and explain emoji convention #359

Closed
john-rodewald opened this issue Oct 22, 2022 · 5 comments
Closed

Establish and explain emoji convention #359

john-rodewald opened this issue Oct 22, 2022 · 5 comments

Comments

@john-rodewald
Copy link
Member

To get an idea of pull request/issue urgency, we could explicitly establish a convention of labelling them with emoji. It's also possible to sort by emoji count - this gives an idea of which things are in high demand.

Proposal

  • 👍 I would like to have this fixed
  • 👀 I'm aware of this, I've seen this

A similar idea has been mentioned in https://discourse.nixos.org/t/improving-developer-experience/21629.


It's such a well-known idea that it has already found some use without us being explicit about it.
The explicit information should be easy to find.

@yukiisbored
Copy link
Member

yukiisbored commented Oct 22, 2022

Right now, it's unclear where to put this information. This information is mainly useful for both users and contributors. If it's solely for contributors, we can simply put it in the contributor guide.

But, as this is also useful for users who lurk issues or found an issue which affects them, this information should be visible to them if we wish them to follow the same convention.

I'm thinking maybe a pinned issue which that's well titled and contains information on everything related to how to respond to issues.

Though at the same time, using 👍 is universal so we can put it somewhere visible and actively link people to it (f.e. when someone replies "I want this" or "+1" to an issue instead of using the 👍 reaction).

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2022-10-22-documentation-team-meeting-notes-12-nixcon-edition/22689/1

@infinisil
Copy link
Member

infinisil commented Nov 10, 2022

We discussed this in the meeting today, we think it would be good to have this in the issue template for nix.dev, nixpkgs, nix, something like

Leave a 👍 if you also want this issue fixed

Also include a link to some blurb that mentions how issues can be sorted by 👍 count to find the most wanted ones.

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2022-11-24-documentation-team-meeting-notes-17/23619/1

infinisil added a commit to NixOS/nixpkgs that referenced this issue Dec 1, 2022
Adds a small text to each issue and the PR template to encourage people to use
:+1:'s for issues they're also interested in. See
NixOS/nix.dev#359 for more information
fricklerhandwerk added a commit to fricklerhandwerk/nix that referenced this issue Dec 1, 2022
decided on the @NixOS/documentation-team, see NixOS/nix.dev#359 for more information
infinisil added a commit to tweag/nixpkgs that referenced this issue Dec 1, 2022
Adds a small text to each issue and the PR template to encourage people to use
:+1:'s for issues they're also interested in. See
NixOS/nix.dev#359 for more information
infinisil added a commit to tweag/nixpkgs that referenced this issue Jan 18, 2023
Adds a small text to each issue and the PR template to encourage people to use
:+1:'s for issues they're also interested in. See
NixOS/nix.dev#359 for more information

Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>
infinisil added a commit to tweag/nixpkgs that referenced this issue Nov 21, 2023
Adds a small text to each issue and the PR template to encourage people to use
:+1:'s for issues they're also interested in. See
NixOS/nix.dev#359 for more information

Co-Authored-By: Valentin Gagarin <valentin.gagarin@tweag.io>
@fricklerhandwerk
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

5 participants