Marking issues as: "good-first-issue", "help-wanted", and "beginner-friendly"

[marlitas]

This issue will track and link issues in phetsims common code repos that we believe are good candidates for open source contributions.

[marlitas]

In Scenery:

"good-first-issue":

• [x] - https://github.com/phetsims/scenery/issues/1363
• [x] - https://github.com/phetsims/scenery/issues/1262

"beginner-friendly":

• [x] - https://github.com/phetsims/scenery/issues/1231
• [x] - https://github.com/phetsims/scenery/issues/1208
• [x] - https://github.com/phetsims/scenery/issues/1203
• [x] - https://github.com/phetsims/scenery/issues/1581
• [ ] - https://github.com/phetsims/scenery/issues/64

"help-wanted":

• [x] https://github.com/phetsims/scenery/issues/904

[marlitas]

Joist

"good-first-issue":

• [x] - https://github.com/phetsims/joist/issues/807
• [x] - https://github.com/phetsims/joist/issues/273 (this needs some more breakdown and specificity though)

"help-wanted":

• [x] - https://github.com/phetsims/joist/issues/732
• [x] - https://github.com/phetsims/joist/issues/557
• [x] - https://github.com/phetsims/joist/issues/537
• [ ] - https://github.com/phetsims/joist/issues/931 (this seems like it would be straightforward to implement but needs a designer...)

[marlitas]

Sun

"help-wanted":

• [x] https://github.com/phetsims/sun/issues/777
• [x] https://github.com/phetsims/sun/issues/653
• [x] https://github.com/phetsims/sun/issues/200

"good-first-issue":

• [x] - https://github.com/phetsims/sun/issues/749
• [x] - https://github.com/phetsims/sun/issues/659
• [ ] - https://github.com/phetsims/sun/issues/555 (this chipaway needs to be triaged and also clarify what would be expected form a contributor)
• [ ] - https://github.com/phetsims/sun/issues/523 (this is another contender that needs more clarity, and also removing the instructions related to PhET-iO)
• [x] - https://github.com/phetsims/sun/issues/522
• [x] - https://github.com/phetsims/sun/issues/351

[marlitas]

Axon

"good-first-issue":

• [x] - https://github.com/phetsims/axon/issues/334

"help-wanted":

• [x] - https://github.com/phetsims/axon/issues/410
• [x] - https://github.com/phetsims/axon/issues/41

[marlitas]

Kite

"beginner-friendly":

• [x] https://github.com/phetsims/kite/issues/76
• [x] https://github.com/phetsims/kite/issues/56 (It would be easy to simplify the instructions here for a beginner to feel comfortable, but as is right now doesn't feel beginner-friendly).

[marlitas]

Tambo

"good-first-issue":

• [x] https://github.com/phetsims/tambo/issues/87

[marlitas]

Dot

"beginner-friendly":

• [x] https://github.com/phetsims/dot/issues/96

"good-first-issue":

• [x] https://github.com/phetsims/dot/issues/49
• [x] https://github.com/phetsims/dot/issues/38

"help-wanted":

• [ ] https://github.com/phetsims/dot/issues/4 (I would want to check in with devs on this before opening it up... it has the potential to be an open source chipaway, but I feel like we just haven't made a decision on what we want. It's also incredibly old)

[marlitas]

This is my first pass at identifying some issues. I tried to stay away from things that really involved or interacted directly with phet-io. Many will need a clear summary or explanation of next steps for someone to feel confident going into it.

My next steps will be to triage these again and add labels.

@brettfiedler are there any other common-code repos you would like me to hit that are missing here? I did: Scenery, Joist, Sun, Axon, Kite, Tambo, and Dot

[marlitas]

Issues that need outside input or additional work before they are ready for the public:

• https://github.com/phetsims/scenery/issues/64 (This needs dev input to determine which way we want to go.)
• https://github.com/phetsims/sun/issues/555 (this chipaway needs to be triaged and also clarify what would be expected form a contributor)
• https://github.com/phetsims/sun/issues/523 (this is another contender that needs more clarity, and also removing the instructions related to PhET-iO)
• https://github.com/phetsims/joist/issues/931 (this seems like it would be straightforward to implement but needs a designer...)
• https://github.com/phetsims/dot/issues/4 (I would want to check in with devs on this before opening it up... it has the potential to be an open source chipaway, but I feel like we just haven't made a decision on what we want. It's also incredibly old)

[marlitas]

Over to @brettfiedler for next steps.

EDIT: I can't assign anyone, so you'll have to assign yourself?

[zepumph]

I love these new labels. Thanks for doing this. I found this issue while adding labels to a new repo, and had a couple thoughts here.

• I was noticing that they don't adhere to our github label conventions, in which they get a prefixed "class" with a colon. Perhaps all of these could be added to type:XX? Or maybe community: or pose: if we want something new and specific to POSE. Not sure what is best, but organization sounds preferable given the complexity and size of our label system.
• I also wanted to note that we already have dev:help-wanted, perhaps we should get rid of that label, and make all of those labels have this label? Not sure what's best.
• It doesn't look like this was added to all repos consistently, For example phetcommon doesn't have these labels, but it is in the github label system in phet-info, so when I added "all labels to new repo" over in https://github.com/phetsims/soccer-common/issues/5, it did pick up these labels. I think that keeping consistent labels in every single repo (unless we need a label for one specific repo, like we have in chipper) is best.

[marlitas]

@zepumph The reason they are not prefixed with a colon is because we want these labels to be picked up by github as "goog-first-issue", "help-wanted", etc. that they market to github users. Generally github has a list of issues from different open source projects that have these labels for those that may want to contribute to those projects. Adding a prefix would break this for us and our issues would no longer be bundled in there which would be very un-POSE like of us.

I also wanted to note that we already have dev:help-wanted, perhaps we should get rid of that label, and make all of those labels have this label? Not sure what's best.

That label has been used (i know by me and SR) to communicate when we might need help from another PhET dev on an issue. We used this alot for CAV. I did not eliminate it because those types of issues should not get mixed into the POSE "help-wanted" issues.

I think that keeping consistent labels in every single repo is best.

I'm fine with this. @brettfiedler would you like me to add these to every single repo?