Skip to content
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

Clarify the KEDA website and documentation maintainers #1372

Open
Tracked by #1361 ...
dwelsch-esi opened this issue Apr 15, 2024 · 5 comments
Open
Tracked by #1361 ...

Clarify the KEDA website and documentation maintainers #1372

dwelsch-esi opened this issue Apr 15, 2024 · 5 comments
Labels
cant-touch-this All issues that should not be automatically closed by our stale bot

Comments

@dwelsch-esi
Copy link
Contributor

Document the website maintainers.

Use-Case

Documentation and website maintainers should be listed in the doc repository.

Specification

Create an OWNERS.md file to document (on the kedacore/keda-docs repo) the current custodian(s) of the following accounts: analytics (GA4), site-search (Algolia).

Explicitly document in the repo (keda-docs, keda, or both) who the website/documentation maintainers are. Solicit maintainers and contributors for documentation, either in the new OWNERS file or the governance MAINTAINERS file.

Copy link

stale bot commented Jun 15, 2024

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

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Jun 15, 2024
@nate-double-u
Copy link
Contributor

It's best not to auto-delete this issue; it is still relevant.

@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Jun 18, 2024
@tomkerkhove tomkerkhove added the cant-touch-this All issues that should not be automatically closed by our stale bot label Jun 19, 2024
@tomkerkhove
Copy link
Member

Hi, what would be the recommendation? We already have https://github.com/kedacore/keda-docs/blob/main/.github/CODEOWNERS.

Is the suggestion to reference this in the README or?

@nate-double-u
Copy link
Contributor

I think including the info in the README could work, but I think the point of this suggestion is to ensure access to these services when project personnel changes (or when someone needs access years in the future after things have been setup). Since it's potentially private or secure data, maybe create a private document (shared with the CNCF) with instructions on how to access it when needed.

@tomkerkhove
Copy link
Member

Oh I missed the part for site-search & analytics. I honestly don't know that, this was set up by CNCF so I'd presume that is on your team then or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cant-touch-this All issues that should not be automatically closed by our stale bot
Projects
Status: No status
Development

No branches or pull requests

3 participants