Codeberg/Documentation
42
199
Fork
You've already forked Documentation
161

State of CONTRIBUTORS.md #275

Closed
opened 2022年11月01日 20:40:29 +01:00 by lhinderberger · 1 comment
Contributor
Copy link

Hi everyone 👋

I just noticed that the CONTRIBUTORS.md that we currently keep in this repo hasn't been updated in over a year and doesn't contain the names of all contributors (as listed in the commit history) either.

Keeping the file up-to-date manually would probably not be feasible, as proven by its current state 😉 So the question is, what to do with it? I could imagine a number of scenarios:

  • Drop it entirely, maybe clarify in the README and/or LICENSE that copyright is owned collectively by all contributors, as listed in the commit log
  • Replace its contents with a link to an auto-generated list of contributors - Not sure if that's possible on Gitea, but it's a fairly common thing some projects do over on Github
  • Write a script that updates the file automatically from the commit log, run that script in CI - Caveat: Would require us to set up CI 😉
  • Something entirely different I didn't think of

What are your opinions on this?

Hi everyone 👋 I just noticed that the CONTRIBUTORS.md that we currently keep in this repo hasn't been updated in over a year and doesn't contain the names of all contributors (as listed in the commit history) either. Keeping the file up-to-date manually would probably not be feasible, as proven by its current state :wink: So the question is, what to do with it? I could imagine a number of scenarios: - Drop it entirely, maybe clarify in the README and/or LICENSE that copyright is owned collectively by all contributors, as listed in the commit log - Replace its contents with a link to an auto-generated list of contributors - Not sure if that's possible on Gitea, but it's a fairly common thing some projects do over on Github - Write a script that updates the file automatically from the commit log, run that script in CI - Caveat: Would require us to set up CI :wink: - Something entirely different I didn't think of What are your opinions on this?

I'd just get rid of it.

I'd just get rid of it.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/mstruebing-editorconfig-checker-3.x
renovate/lycheeverse-lychee-0.x
renovate/font-awesome
renovate/prettier-3.x
renovate/pagefind-1.x
renovate/markdownlint-cli2-0.x
renovate/markdown-it-14.x
renovate/davidanson-markdownlint-cli2-0.x
renovate/pipelinecomponents-yamllint-0.x
renovate/11ty-eleventy-3.x
renovate/node-lts-slim
renovate/npm-pnpm-vulnerability
renovate/lock-file-maintenance
ci_pr_close_no_preview
pr-554
pr/554
gitea-icons-shortcode
No results found.
Labels
Clear labels
Codeberg Pages
Issues affecting Codeberg Pages
Documentation Usability
Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
This is related to the generation of the documentation, not to the content itself
Priority: High
The priority is high
Priority: Low
The priority is low
Priority: Medium
The priority is medium
Reviewed: Confirmed
Something has been confirmed
Reviewed: Duplicate
Something exists already
Reviewed: Invalid
Something was marked as invalid
Reviewed: Wontfix
Something won't be fixed
Status: Blocked
Status: Help wanted
Contributions are welcome!
Status: In progress
Work is in progress
Status: Needs feedback
Feedback is needed
Status: Ready for Review
Work is completed
Status: Review
Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Documentation#275
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?