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

Add new label for asking community to share thoughts and votes on features and PRs #17882

Closed
OrlinVasilev opened this issue Nov 28, 2022 · 13 comments
Assignees
Labels

Comments

@OrlinVasilev
Copy link
Member

OrlinVasilev commented Nov 28, 2022

Hello Community,

we need a way to address the need for your feedback on features and PRs related to Harbor which includes operator and helm and terraform-provider. This way we want to make everyone more engaged and informed about the future of Harbor development!

Please vote on:

  1. community-voting-required
  2. community-feedback-required
  3. requires-community-input
  4. community-feedback-requested
  5. propose another more welcoming and inclusive label :)

We will use that label to mark PRs and discussion that need public input and review by MANY folks :)

Thank you!
Orlix

@OrlinVasilev OrlinVasilev self-assigned this Nov 28, 2022
@wy65701436
Copy link
Contributor

requires-community-input +1

@Vad1mo
Copy link
Member

Vad1mo commented Nov 30, 2022

I like community-feedback-required. Reason for feedback is that is less narrow as only voting

@MarcelMue
Copy link

requires-community-input Is best to me - it's most direct and to the point.

@david-caro
Copy link

+1 for community-feedback-required, or community-feedback-needed (sounds slightly more welcoming, as requesting many reviews, not just one to get unblocked), even community-feedback-wanted if it's not blocking at all.

@OrlinVasilev
Copy link
Member Author

OrlinVasilev commented Dec 1, 2022

+1 community-feedback-required - it's more warm and welcoming
+0.5 :) requires-community-feedback - it's more actionable , but more demanding

@qnetter
Copy link
Contributor

qnetter commented Dec 1, 2022 via email

@github-actions
Copy link

github-actions bot commented Feb 3, 2023

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@mohitsharma-in
Copy link

community-feedback-required +1

@chris-short
Copy link

Something more "needs" based than "requirement" based: community-feedback-needed

@nedhanks
Copy link

nedhanks commented Feb 6, 2023

I like community-feedback-required .

@github-actions
Copy link

github-actions bot commented Apr 8, 2023

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions
Copy link

github-actions bot commented Jun 9, 2023

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Jun 9, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants