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.

Sign up for GitHub

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

Jump to bottom

Refactor CONDUCT.md: #1807

Open
jpmcb opened this issue Sep 14, 2022 · 2 comments
Open

Refactor CONDUCT.md: #1807

jpmcb opened this issue Sep 14, 2022 · 2 comments
Assignees
@jpmcb
Labels
admin For general admin tasks to be done usualy by maintainers help-wanted An issue that the maintainers would like help resolving lifecycle/frozen Prevents GitHub actions from labeling issues / PRs with stale and rotten

Comments

@jpmcb
Copy link
Collaborator

jpmcb commented Sep 14, 2022

From the CONDUCT.md:

Deprecation of Go versions or dependent packages will only occur in major releases.

It's been awhile since I read that deprecation policy but I'm not sure I agree with it anymore: we should in theory be able to drop "supported" versions of our dependencies without having any breaking changes to the core functionality of cobra. People could still use cobra without issue it just wouldn't be "supported".

...

It'll never be sustainable for us to make major releases with how fast Go deprecates it's versions.

Originally posted by @jpmcb in #1783 (comment)

It's time we revisited the conduct and current community agreement. Pr to come!
@jpmcb jpmcb self-assigned this Sep 14, 2022
@jpmcb jpmcb added admin For general admin tasks to be done usualy by maintainers help-wanted An issue that the maintainers would like help resolving labels Sep 14, 2022
@umarcor
Copy link
Contributor

umarcor commented Sep 14, 2022

Context: #1232

@github-actions
Copy link

The Cobra project currently lacks enough contributors to adequately respond to all issues. This bot triages issues and PRs according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed.
    You can:
  • Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

@jpmcb jpmcb added the lifecycle/frozen Prevents GitHub actions from labeling issues / PRs with stale and rotten label Nov 15, 2022
@umarcor umarcor mentioned this issue Nov 25, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpmcb jpmcb

Labels
admin For general admin tasks to be done usualy by maintainers help-wanted An issue that the maintainers would like help resolving lifecycle/frozen Prevents GitHub actions from labeling issues / PRs with stale and rotten
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpmcb @umarcor