Website: Need OWNERs file in subdirectories of docs

Created on 11 Aug 2020  路  7Comments  路  Source: kubeflow/website

Most of the subdirectories in docs lack owners files
https://github.com/kubeflow/website/tree/master/content/en/docs

Each of these directories should probably have an OWNERs file indicating who is responsible for the docs.

@8bitmp3 and @RFMVasconcelos could you help drive this?

arecommunity aredocs kinfeature lifecyclstale prioritp1

Most helpful comment

fyi I'm making a comprehensive list of:

  • docs directories and subdirectories with OWNERS files + corresponding (open/closed) PRs
  • docs directories and subdirectories that should be updated (and a list of potential approvers based on the commit history)

cc @jlewi

All 7 comments

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| area/docs | 0.96 |
| kind/feature | 0.53 |

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

Issue-Label Bot is automatically applying the labels:

| Label | Probability |
| ------------- | ------------- |
| kind/feature | 0.53 |
| area/docs | 0.96 |

Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@jlewi 馃挴

Just to be clear: we should create an OWNERS file in each sub-directory (without a suffix/extension). This will be similar to what we've got in /kubeflow/kubeflow/blobl/master/OWNERS, such as:

# We want to rely on fine grained OWNERs files.
  - jlewi
  - [github_handle2]
  - [github_handle3]
  • To implement this, we can have one draft PR that encapsulates all OWNERS file additions to /kubeflow/website/docs
  • In it, we can tag each of the docs original creators and contributors per org (independent, SaaS, or cloud provider, for example)
  • If they confirm they or someone else is in charge of the docs - that'll be 馃憤 and we push/change the commit(s)

WDYT?

Hi @jlewi, @8bitmp3 this looks cool, happy to help drive!

@8bitmp3 However, you want to do it sounds good to me. Breaking it up into many PRs might help so you don't get blocked waiting on the tail end of approvers.

fyi I'm making a comprehensive list of:

  • docs directories and subdirectories with OWNERS files + corresponding (open/closed) PRs
  • docs directories and subdirectories that should be updated (and a list of potential approvers based on the commit history)

cc @jlewi

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings