-
Notifications
You must be signed in to change notification settings - Fork 590
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
New repo for language guidelines #91
Comments
|
let’s chat next week, if we are codifying guidelines they be in this repo
I have some ideas to share on this too
On Fri, Jun 19, 2020 at 6:41 PM Celeste Horgan ***@***.***> wrote:
Create a new repo, cncf/language, to host a list of language and naming
requirements for CNCF projects.
Note: I was privately circulating a google doc
<https://docs.google.com/document/d/1bnPvb6oE07Wg9rb7kBXcpHe6j85bbyltdc0h0_gil88/edit?usp=sharing>
to Kubernetes collaborators for this work, it's taken on a life of its own
and started circulating independently of any Kubernetes- or CNCF- work to
some of our member organizations. At this point I think it's best to make
any WIP publicly attached with the CNCF :)
Note #2 <#2>: I'm open to
alternate repo names.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#91>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAPSIIKJH2MWVQOZEUZTGTRXPZQ7ANCNFSM4ODDSJ7A>
.
--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719
|
xref ContribStrat issue: cncf/tag-contributor-strategy#34 |
@justaugustus can you just PR a new .md to this repo which is meant for all foundation wide guidelines? |
Yup, will do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Create a new repo,
cncf/language
, to host a list of language and naming requirements for CNCF projects.Note: I was privately circulating a google doc to Kubernetes collaborators for this work, it's taken on a life of its own and started circulating independently of any Kubernetes- or CNCF- work to some of our member organizations. At this point I think it's best to make any WIP publicly attached with the CNCF :)
Note #2: I'm open to alternate repo names.
The text was updated successfully, but these errors were encountered: