knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add knative-users as as access option for Team Drive (#313) 

* Add knative-users as as access option for Team Drive

* Un-prettify to make diff reading easier.

* Even less pretty.
This commit is contained in:
Evan Anderson 2018-08-03 11:23:31 -07:00 committed by Google Prow Robot
parent 765589015c
commit 90b273c7e4
3 changed files with 17 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
community/CONTRIBUTING.md
View File

@ -58,12 +58,16 @@ to be a [member](ROLES.md#member) of the Knative organization.
We do not yet have a common design document template(TODO).
The team drive is shared with the
[knative-users@](https://groups.google.com/forum/#!forum/knative-users) and
[knative-dev@](https://groups.google.com/forum/#!forum/knative-dev) Google
group for editing and commenting. If you're not part of that group, the
first time you try to access the team drive or a specific doc, you'll be
asked to request permission. This permission will always be granted and we
do our best to grant access as fast as we can, but there is a human involved
there, so please forgive any delays.
groups for reading and editing, respectively. Access to
[knative-users@](https://groups.google.com/forum/#!forum/knative-users) is
unlimited, while
[knative-dev@](https://groups.google.com/forum/#!forum/knative-dev) requires
human review. If you're not part of one of those groups, the first time you try
to access the team drive or a specific doc, you'll be asked to request
permission. Please join one of the above groups (you can join knative-users and
later join knative-dev if you want immediate access).
## Contributing a feature
@ -100,7 +104,6 @@ following steps:
* Submit PRs to knative/serving with user documentation for your feature,
including usage examples when possible. Add documentation to
[knative/docs/serving](https://github.com/knative/docs/tree/master/serving).
<!-- TODO: switch to knative/serving.dev) -->
*Note that we prefer bite-sized PRs instead of giant monster PRs. It's therefore
preferable if you can introduce large features in small, individually-reviewable

6
community/ROLES.md
View File

@ -34,7 +34,7 @@ table describes:
<tr>
<td>Collaborator</td>
<td>Casual contributor to the project</td>
<td>n/a</td>
<td>Join [knative-users@](https://groups.google.com/forum/#!forum/knative-users) to get access to the team drive.</td>
<td>
<p>Can submit PRs</p>
<p>Commenting permission on the Knative Team drive</p>
@ -115,7 +115,9 @@ the PR bot.
* Working on some contribution to the project that would benefit from the
ability to have PRs or Issues to be assigned to the contributor
* Sponsored by 1 member
* Join [knative-users@](https://groups.google.com/forum/#!forum/knative-users)
unrestricted join permissions; this grants read access to documents in the
Team Drive
## Member

7
community/WORKING-GROUPS.md
View File

@ -13,9 +13,10 @@ procedures.
The working groups generate design docs which are kept in a
[shared drive](https://drive.google.com/corp/drive/folders/0APnJ_hRs30R2Uk9PVA)
and are available for anyone to read and comment on. The shared drive
currently grants edit and comment access to the
[knative-dev@](https://groups.google.com/forum/#!forum/knative-dev)
Google group.
currently grants read access to
[knative-users@](https://groups.google.com/forum/#!forum/knative-users) and edit
and comment access to the
[knative-dev@](https://groups.google.com/forum/#!forum/knative-dev) Google group.
The current working groups are: