vbatts
/
cncf-toc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

unify steps to become a TOC Contributor 

This file used to say that "we would encourage you to make a public commitment on the TOC mailing list that you will become a TOC Contributor." while CONTRIBUTORS.md said "we would encourage you to issue a pull request here that you desire to become a TOC Contributor".

Updating this file to match CONTRIBUTORS.md
This commit is contained in:
Dave Zolotusky 2018-03-20 16:28:13 +01:00 committed by GitHub
parent da5f7af5d0
commit 3f808d7be2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -18,7 +18,7 @@ Possible ways to contribute:
* Working groups (various tasks)
* Technical content for website
If you are interested in engaging in this way, we would encourage you to make a public commitment on the TOC mailing list that you will become a TOC Contributor. Although there is not an actual limit of having one Contributor per company, we would encourage CNCF member companies to designate an official TOC Contributor who is tasked with consulting internal experts and expressing a semi-official view on a given project. We will list current TOC Contributors on a page similar to https://www.cncf.io/people/ambassadors/.
If you are interested in engaging in this way, we would encourage you to issue a pull request to [TOC Contributors](https://github.com/cncf/toc/blob/master/CONTRIBUTORS.md) that you desire to become a TOC Contributor. Although there is not an actual limit of having one Contributor per company, we would encourage CNCF member companies to designate an official TOC Contributor who is tasked with consulting internal experts and expressing a semi-official view on a given project. We will list current TOC Contributors on a page similar to https://www.cncf.io/people/ambassadors/.
This is not only about individual contribution. It is also about rallying help from your employer, e.g., if you work for a CNCF Member company. Given the [breadth](https://raw.githubusercontent.com/cncf/landscape/master/landscape/CloudNativeLandscape_v0.9.5_cncf.jpg) of projects represented by cloud native, it is impossible for anyone to be an expert in all technologies that we’re evaluating. We’re particularly interested in Contributors that can act as a focal point for tapping relevant expertise from their organizations and colleagues in order to engage with CNCF discussions in a timely manner.