clean up labels about community HOT 9 CLOSED

Two questions:

Remove

• cla-not-required: Is a CLA required for all PR's now?

Rename

• area/devops-support -> area/operationalization: What about just area/ops?

from community.

Contributing to Harbor does not require a CLA now that it's part of the CNCF. The cla-not-required label was for VMware employees contributing to Harbor before it was donated.

I like your proposal re: area/ops. Will amend the list. Thanks! 👍

from community.

Lazy consensus: if I don't hear any objections by 2dec2018 I'll go ahead and start cleaning up labels.

ping @goharbor/all-maintainers

from community.

Github issue is the single source of truth for work item management in Harbor.

For example, target/* have been used to track the issues in each release, which is far from optimal, but before we have agreement on another process, removing them will lost track for the planned items for each release. Same as candidate/, defer-

I agree there is a lot of inconsistency and makes it confusing. I wish to suggest the following before you take action to clean up the labels:

1. Propose a better process for work item management.
2. Propose a convention for label management, clarify the usage of them in the community call.

cc @steven-zou who has also been creating renaming the labels recently.

from community.

I personally agree with the following changes:

Remove

• COBD
• DB change
• kind/ux-fit-and-finish (use area/ui or area/ux instead)
• make
• message
• needs/validation
• new-ui
• UX (use area/ux instead)
• waiting-for-verify (use needs/repro instead)
• with-admiral

Rename

• area/devops-support -> area/ops
• area/test automation -> area/test-automation
• kind/customer-found -> found/customer
• kind/automation-found -> found/automation
• kind/longevity-found -> found/longevity (do we run longevity tests?)
• kind/nightly-blocker -> found/nightly
• need-document -> needs/documentation
• need-test-case -> needs/test-case
• need-triage -> needs/triage
• need-reproduction -> needs/repro
• pending-more-info -> pending/info
• pending-ux-review -> pending/ux-review
• photon:2.0 -> area/base-linux
• security -> area/security

other suggestions

• env_issue -> env-issue (how about kind/env-issue)
• external_integration -> external-integration (how about area/external-integration)

As for the Merge section.
area/helm-chart-repo and area/helm-chart are two different areas one is for the helm chart itself and the other is for the feature "chart repo"

from community.

I basically agree with the cleanup. And have some personal suggestions:

1. How about change found --> reporter, so that found/customer --> reporter/customer
2. Add some labels to track the status of issues, such as:

• status/new
• status/in-progress
• status/resolved

3. requirement/status/accepted --> requirement/accepted and other similar labels.
4. Keep target/* before we have other replacement.

And do we have document to guide how to use these labels.

from community.

Still planning on taking care of this. Hopefully sometime this week (if not early next).

from community.

@reasonerjt

Clear labels?

from community.

@steven-zou @reasonerjt looks like thats quiiiiite old :) shall we close that ?

from community.