Conversation
Re-records the label-set decision from QuantEcon/meta#324 as a worked Standard-type QEP, per QEP-1's rollout. Defines the standard label set (18 core + 2 lecture), the labelling policy, and the one behavioural change (retire status labels in favour of native GitHub PR lifecycle). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Apply the final decisions from QuantEcon/meta#324: - infrastructure split approved (no longer flagged open) - Q2 rollout is a staged pilot on lecture-python-programming, then wider - add the separate `qe gh labels prune` step (one-by-one review) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
QEP-2: Standard GitHub Label Set and Labelling Policy
Status: Draft · Type: Standard · Discussion: QuantEcon/meta#324
This is the DRAFT of QEP-2, re-recording the label-set decision from QuantEcon/meta#324 as a worked
Standard-type QEP — step 2 of QEP-1's rollout. It's opened as a draft so we can keep iterating on the wording before it goes up for a decision; the substantive calls in #324 are all settled.What it defines
new-lecture,editor) = 20, with standard names, colours, and descriptions. The core 18 also becomes the org-level default for new repos.questionvsdiscussand adiscussclosing convention; automation labels are bot-applied.in-work/ready/review/blocked) in favour of native GitHub (Draft PRs, "Ready for review", review requests, issue dependencies). Onlydo-not-mergesurvives.Decisions from #324, folded into this draft
infrastructuremaintenance→ 20 labels (18 core)discuss(@jstac)#f904a0, split cleanly fromquestiondocumentation(@xuanguang-li)#b08968, off the blue "new content" familygood first issue/help wantedspacing (@longye-tian)blocked?lecture-python-programmingfirst, then roll out more widelydiscussexit)qe gh labels syncadditive; a separateqe gh labels prunereviews non-standard labels one-by-oneNotes / open to wording feedback
infrastructurecolour is a placeholder#006b75— its existing colour (#BF3E89) would clash with the newdiscusspink, so it needs a fresh distinct hue. Suggest a better one if you have a preference.infrastructureinQuantEcon/cli'slabels.yml(it's currently listed as amaintenancealias).qep-candidate(meta-only) label is deliberately out of scope here — he flagged it for #325, not this rollout.Decision deadline
To be set by the author. Since #324 reached consensus by its 17 June deadline, this is largely a formalisation — a short comment window (≈1 week) is likely enough.
🤖 Generated with Claude Code