Replies: 2 comments 1 reply
-
Thank you @remrama for thinking this through! Some feedback:
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Thanks for the information! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm considering some updates to the labels that the YASA repository uses for Issues, PRs, and Discussions and would like some community feedback first. cc @raphaelvallat
Add a
docs
ordocumentation
label with a short description like: Related to online documentation. Right now docs-related Issues typically get tagged withenhancement
, but this would be a useful distinction. Most changes to documentation are small and easily clumped together, so when working on docs it'd be nice to filter by this label.Remove the
duplicate
label. As of last month, Issues/PRs/Discussions can be "Closed as duplicate". (This hasn't been used yet in YASA anyways.)Update the
help wanted
label description. If I understand this label, it's a casual request or offer for assistance from a new developer (something akin to agood first issue
label). I like this idea a lot but the description should be updated to match that if so; maybe something like Good first issue for newcomers, Looking for assistance, or just changing the current to Extraattentionassistance is needed.Remove the
invalid
label or clarify it's purpose in the description. Is this separate frombug
? I think it could be removed, but if I'm missing a strong reason to keep it I think we should reword its single-sentence description for clarity. Maybeinvalid
is like a minorbug
? If so, I think we already have that case covered since there is bothbug
andurgent
(so abug
without an associatedurgent
implies a minor bug).Remove the
question
label and emphasize theQ&A
Discussions. By far my most controversial take lol. But I've always thought that facing the "where do I post" question on any GitHub repo with both Issues and Discussions can be rough, and having a "questions" in YASA Issues and "Q&A" in YASA Discussions probably doesn't help. But more importantly, I think that the nature of YASA brings along many newcomer questions about more general sleep-science things, like how the detection algorithms work and such, and that the Discussions are a better place for those questions to linger. These aren't really "Issues" in the technical sense since they don't relate to codebase changes, but I do think the YASA repo is a great place to ask them! I think they would be better placed in the Discussion section because (a) the "marked as answered" feature is nice, (b) they don't clutter up Issues, which feel more pressing to developers, and (c) they can linger much longer in Discussions for others to view. We could be clearer in the FAQ docs about where to post based.Beta Was this translation helpful? Give feedback.
All reactions