Closed raprasad closed 1 month ago
Q: Where should a descriptions of the commons live? A: https://docs.opendp.org/en/stable/opendp-commons/index.html
Are repositories within the opendp org, other than the library, considered as part of the commons?
It surprised me, but no: Salil writes:
However, the OpenDP Commons should include the OpenDP Library, but not SmartNoise. It is more about community ownership and governance rather than the nature of the software itself.
How can we "mark/label" these repositories--perhaps a badge?
Using a github "topic" would be good: We could link to a complete list. My previous lab, for example.
Where should a description of the commons live? In this repository?
I'd prefer to leave the description of the opendp commons to the project site. Better to do it in just one place, and do it clearly. The current description of commons on the project site could
People can use that link, but as discussed, github repo topics are not something we can control: Anyone can add opendp-commons
to their repo. If this is a concern, then you'll need to make use of the organization. One possible way to explain the relationship between projects would be create an organization README, but I think the status quo is fine.
from the github docs:
Create a public repository called .github. Once created, add a /profile/README.md. The README will appear on your organization's profile, visible to anyone.
Closing!
To discuss