-
Notifications
You must be signed in to change notification settings - Fork 1
Add labels to this repo that will be helpful for community contribution #4
Comments
A few pages with some interesting additions beyond the PhET labels: |
I understand the motivation. But this repo is causing problems that affect PhET internally. And not having standard labels was never communicated to the team (a PSA would be great), which results in confusion and duplicate issues like #20, and makes it problematic to label things appropriately for internal processing. So if this repo is (by design) not going to conform to the standards of PhET's active repositories, then perhaps it should be removed from perennial/data/active-repos. That would also prevent problems like #19 and #21. |
Thanks for catching all this and taking some action and sorry for the extra work, @pixelzoom. We discussed this further and are going to continue to separate the labels here from the labels generally used for our internal processes. Errors like this should ideally be minimal in the future, as this will primarily be a documentation repository. @samreid felt we should keep community in active-repos for discoverability. Issues around linting will be addressed for consistency (#19, #21). @samreid made a change in phetsims/phet-info#210 to opt community out of a label related script along with a PSA to Slack. Issue will continue for investigating appropriate labels in anticipation of Discussions use. |
Transferred to scenerystack/community#4 |
We chose to leave out PhET internal process labels for this repo. We want to investigate which labels might be most helpful for community contributors.
I'll look around at some open source projects and see what labels exist that might be helpful to import or amend GitHub defaults.
The text was updated successfully, but these errors were encountered: