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

Add links to other OSS communities using Discourse

This commit is contained in:
Jorge O. Castro 2018-04-17 09:51:40 -04:00
parent 9d2f5a8473
commit 2ab4dc2398
No known key found for this signature in database
GPG Key ID: 946EF973E2E37641
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
keps/sig-contributor-experience/0007-20180403-community-forum.md
View File

@ -15,14 +15,12 @@ approvers:
editor: TBD editor: TBD
creation-date: 2018-04-03 creation-date: 2018-04-03
last-updated: 2018-04-03 last-updated: 2018-04-17
status: provisional status: provisional
--- ---
# A community forum for Kubernetes # A community forum for Kubernetes
(This is a draft and not PRed or proposed yet)
## Table of Contents ## Table of Contents
* [Table of Contents](#table-of-contents) * [Table of Contents](#table-of-contents)
@ -97,8 +95,6 @@ The site would be forum.k8s.io, and would be linked to from the homepage and maj
### User Stories ### User Stories
(This is a bullet list right now, needs to be fleshed out)
- A place for open ended discussion. For example "What CI/CD tools is everyone using?" - A place for open ended discussion. For example "What CI/CD tools is everyone using?"
- This would be closed as offtopic on StackOverflow, but would be perfect for a forum. - This would be closed as offtopic on StackOverflow, but would be perfect for a forum.
- Post announcements about kubernetes core that are important for end users - Post announcements about kubernetes core that are important for end users
@ -162,6 +158,16 @@ The site would be forum.k8s.io, and would be linked to from the homepage and maj
- Lots of data retention options in Discourse. - Lots of data retention options in Discourse.
- We'd need to engage with upstream on their plans for this, we would want to avoid having to manage this ourselves. - We'd need to engage with upstream on their plans for this, we would want to avoid having to manage this ourselves.
#### References from other projects
- [Chef RFC](https://github.com/chef/chef-rfc/blob/master/rfc028-mailing-list-migration.md)
- [Blog post](https://coderanger.net/chef-mailing-list/) from a community member - good mailing list and community feedback here.
- [Swift's Plan](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170206/031657.html) - Long discussion, worth reading
- [HTM Forum](https://discourse.numenta.org/t/guidelines-for-using-discourse-via-email/314)
- [Julia](https://discourse.julialang.org/t/discourse-as-a-mailing-list/57) - It might be useful for us to investigate pregenerating the mail addresses?
- [How's Discourse working out for Ghost](https://forum.ghost.org/t/hows-discourse-working-out-for-ghost/947) - We asked them for some direct feedback on their progress so far
## Graduation Criteria ## Graduation Criteria
There will be a feedback subforum where users can directly give us feedback on what they'd like to see. Metrics and site usage should determine if this will be viable in the long term. There will be a feedback subforum where users can directly give us feedback on what they'd like to see. Metrics and site usage should determine if this will be viable in the long term.