Skip to content
This repository has been archived by the owner on Nov 15, 2024. It is now read-only.

Add labels to this repo that will be helpful for community contribution #4

Closed
brettfiedler opened this issue Mar 6, 2023 · 4 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@brettfiedler
Copy link
Member

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.

@brettfiedler brettfiedler added the documentation Improvements or additions to documentation label Mar 6, 2023
@brettfiedler brettfiedler self-assigned this Mar 6, 2023
@brettfiedler
Copy link
Member Author

A few pages with some interesting additions beyond the PhET labels:

@pixelzoom
Copy link

pixelzoom commented Mar 12, 2023

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 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.

@brettfiedler
Copy link
Member Author

brettfiedler commented Mar 13, 2023

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.

@brettfiedler
Copy link
Member Author

Transferred to scenerystack/community#4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants