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

Discussion: Should we keep CONTRIBUTORS.md #19948

Closed
mkaz opened this issue Jan 29, 2020 · 2 comments
Closed

Discussion: Should we keep CONTRIBUTORS.md #19948

mkaz opened this issue Jan 29, 2020 · 2 comments
Labels
[Type] Discussion For issues that are high-level and not yet ready to implement.

Comments

@mkaz
Copy link
Member

mkaz commented Jan 29, 2020

During the update of the main README file in #19743, @youknowriad brought up if we should keep the contributors file here

I wonder if it's time to retire that file. I understand its purpose (non-code contributions) but it's a challenge to keep up to date and I'm not sure the difference with code contributors is huge. (anyway a separate discussion)

This ticket is here to open the discussion. My two cents is to remove, it is a confusing file and not accurate. The majority of people in the file are also on the contributors tab within Github, also do we need the mapping of usernames Github => WordPress?

Open to suggestions for ways to honor and show our appreciation to non-code contributors who are valuable to the project.

@talldan talldan added the [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. label Feb 6, 2020
@mkaz
Copy link
Member Author

mkaz commented Apr 22, 2020

This ticket was brought up in today's core-editor chat by @Soean

Questions raised:

  • Was it ever supposed to be used for code contributors in the first place?
  • Is there an alternative place where contributors can get credited? if I google "Gutenberg contributors" it's the first link, and other links aren't very relevant
  • The contributors page on Github only shows the top 100 contributors for the selected time range.

Suggestions:

  • Maybe we remove code contributors from the file, and only list non-code contributors and add a link to Github contributor list
  • Could we use something like: https://allcontributors.org/

@youknowriad youknowriad added [Type] Discussion For issues that are high-level and not yet ready to implement. and removed [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. labels Jun 4, 2020
@youknowriad
Copy link
Contributor

This file was just removed.

I forgot about the existence of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Discussion For issues that are high-level and not yet ready to implement.
Projects
None yet
Development

No branches or pull requests

3 participants