Create a label for open-source-ecosystem issues
samreid opened this issue · 1 comments
We have a number of issues that relate to PhET's position in the open source ecosystem. I'll create it momentarily, but I wanted to document some discussions around the naming of it.
Sam Reid
Oct 26th at 11:20 AM
@emilym
suggested the open source label would be better as “type:open-source-community” and that sounds OK to me. Please vote with 👍 👎 or comment in the thread
👍
4
17 replies
Chris Malley
9 days ago
To me, the community and the product are 2 different and related things under the “open-source” umbrella. Not everything that is a “community” decision is a “product” decision, and visa versa.
Sam Reid
9 days ago
@pixelzoom
what label do you recommend?
Sam Reid
9 days ago
Inviting
@emilym
Chris Malley
9 days ago
I was OK with what we decided in dev meeting (which I can’t recall now), though I suspect that anything we decide now may diverge from the terminology we decide on in the future, as things solidify.
Sam Reid
9 days ago
dev meeting we decided “type:open-source-ecosystem”
Chris Malley
9 days ago
To me, that’s preferrable to ‘community’, because it encompasses community, product, and everything having to do with open-source that’s related to PhET. I’d also be fine with just “type:open-source”.
👍
2
Chris Malley
9 days ago
And I agree with our decision (which I think
@mjkauzmann
pointed out) to generally not use abbreviations like “type:ose” for labels.
Michael Kauzmann
🌴 9 days ago
I like type:open-source-ecosystem (edited)
👍👍:skin-tone-2:
3
Kathy Perkins
9 days ago
Just wondering - do you not abbreviate because then its not transparent to users outside our team?
Chris Malley
9 days ago
See
@mjkauzmann
post in https://phetsims.slack.com/archives/C6HPE0J91/p1666800611561929
Marla Schulz
9 days ago
What worries me about open-source-ecosystem is that it will feel too specific in the future. Are we thinking this will relate to anything open-source, or is specifically developer issues to enhance, maintain, and build an open source ecosystem? I guess I'm on the opposite end of
@pixelzoom
where ecosystem to me seems to specifically encapsulate product and not community, but that may just be semantics I need to adjust in my head.
Michael Kauzmann
🌴 9 days ago
What if you think of "our project" as the ecosystem. That is what I like about it. just "open-source" feels like, "about what"? We are open-source, but not phet-io code, does it apply to creating code that is open source?
Marla Schulz
9 days ago
I think I’m mis-reading something… to say “our project” is the ecosystem, but the phet-io code is not part of that ecosystem, so is then phet-io code not part of “our project”?
I think the label being slightly open ended is kind of the point right? We don’t want it to get too overly specific before it begins. Looking through some already created labels I see:
phet-io:breaking-api-change
phet-io:collaboration
phet-io:event-stream
phet-io:record-and-playback
phet-io:save-and-load
In these examples phet-io is the general/open-ended part of the label, and then it is followed by a descriptor. I imagine that as the open source project grows similar things will be necessary with “open-source” or “open-source-ecosystem”, etc. (edited)
Kathy Perkins
9 days ago
What if you think of "our project" as the ecosystem. That is what I like about it. just "open-source" feels like, "about what"? We are open-source, but not phet-io code, does it apply to creating code that is open source?
I don't think of the "ecosystem" as "our project". I think of this collective space as "where and how does PhET plug into the open-source-ecosystem". There is an existing open source ecosystem that we participate in already in a variety of ways. So this ecosystem includes us, the libraries we use, those who uses our libraries, those who tests with our code, individuals and organizations who we are in conversation with, etc.
So the label encompasses issues that have overlap with the even broader open-source-ecosystem.
How does that feel to you
@Marla Schulz
? (edited)
Marla Schulz
9 days ago
Mmm. When it’s used as the broader ( beyond PhET ) ecosystem the “open-source-ecosystem” label makes more sense to me.
I will also add that I have full faith that whatever label we choose will serve us well.
👍
1
Brett Fiedler
9 days ago
Just to forward
@emilym
’s reasoning from the original thread in another channel:
"I have no problem with a new label. I would suggest not using “ecosystem”. Community sounds more accessible. “Ecosystem” is what funders want. It’s not clear if we want that. But we do have and generally want community.
So perhaps type:open-source-community."
My own additions: Ecosytem is very broad and has some additional connotations for NSF, other funders, and other folks promoting open source ecosystems. We're certainly discussing the possibility here, but even if we cease exploration under the current funding, we're likely to keep creating issues tied to our existing community.
Taliesin Smith
8 days ago
Most of our project is already open source, so I feel the purpose of the label is to help us identify issues that may directly related to the POSE-funded investigations, and more broadly helps identify issues that are related to us making our processes and code better for our team and our community, however broad the community grows.
From Dev meeting:
Based on conversations this week, including the presentation of Josh Gay, it seems the most suitable label would be "type:open-source-ecosystem".
I'm planning to create it soon. If there is a significant push for renaming, we can rename it.
Also, I want to clarify the connotation is about how PhET fits into a larger open-source ecosystem, not how PhET works "are" an open source ecosystem. Ecosystem includes community. @kathy-phet described it well above:
I don't think of the "ecosystem" as "our project". I think of this collective space as "where and how does PhET plug into the open-source-ecosystem". There is an existing open source ecosystem that we participate in already in a variety of ways. So this ecosystem includes us, the libraries we use, those who uses our libraries, those who tests with our code, individuals and organizations who we are in conversation with, etc.
So the label encompasses issues that have overlap with the even broader open-source-ecosystem.