-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit statement on sub-project scoping #46
Comments
Do we need to have the following explicit statement for all repositories matching the pattern
I think it is redundant to have the explicit statement since the project name "ORAS |
All ORAS libraries should follow https://oras.land/client_libraries/.
Since libraries are language specific, references will be available on the language specific website. A link should be added to the |
Thanks @shizhMSFT for opening this. For other sub-projects may be a bit broader, or different. Having each sub-project define it's scope is goal. Not too much, not too little, juuuust right. |
Just a paragraph in the README with goals/non-goals maybe? |
The question about scope of each sub-project continues to come up. I'm suggesting the readme can define the scope:
"The oras-dotnet repo is scoped at implementing a dotnet version of ORAS functionality. "
The interesting thing that came up with the oras-py implementation is whether each library is following an implementation of a common spec? What's the reference for each library?
For now, It's probably ok to just say the above.
Originally posted by @SteveLasker in oras-project/oras-dotnet#2 (comment)
The text was updated successfully, but these errors were encountered: