[FEATURE] Add "Support" page
Requirements
The OpenFeature project is large enough that it should have a page that features training/support like other CNCF projects: e.g., https://prometheus.io/support-training/ or https://www.envoyproxy.io/community
CNCF guidelines: https://github.com/cncf/foundation/blob/main/website-guidelines.md
I'll bring this up at the next GC meeting.
Hi @beeme1mr, I work with Chris here at the foundation. I have already started taking a look at this issue. I'm very much happy to collaborate together with you and the rest of maintainers.
Will let you know once I have a PR ready!
Thanks @thisisobate! I added you as a co-assignee then. Let's work through this issue (or ping me on Slack) to discuss the details.
I talked to the GC today and we would like to define the requirements for someone to be listed on the support page. We already have an ecosystem page that lists vendor integrations, and we feel that the support page should have a higher entry barrier.
I'd advise all y'all keep it as simple as possible.
If the organization has a page on their website mentioning openfeature support and they have contributed to the project would be good enough for me. The idea here is to actually start building an ecosystem without making it too hard.
You should have a higher bar for folks to join as maintainers etc
On Fri, Mar 1, 2024 at 11:01 AM Michael Beemer @.***> wrote:
I talked to the GC today and we would like to define the requirements for someone to be listed on the support page. We already have an ecosystem page that lists vendor integrations, and we feel that the support page should have a higher entry barrier.
— Reply to this email directly, view it on GitHub https://github.com/open-feature/openfeature.dev/issues/390#issuecomment-1973549975, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSINJDXGQFXDWSEDKSTTYWCX77AVCNFSM6AAAAABCPWWHX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGU2DSOJXGU . You are receiving this because you authored the thread.Message ID: @.***>
-- Cheers,
Chris Aniszczyk https://aniszczyk.org
Hey @caniszczyk, we already have an ecosystem page that essentially does what you're describing.
https://openfeature.dev/ecosystem
I could see this support page as an opportunity for vendors to explain to users what kind of support and commitment they can expect.
FYI @open-feature/governance-board
SGTM, just try to keep it simple like Envoy etc https://www.envoyproxy.io/community or https://prometheus.io/support-training/
On Fri, Mar 1, 2024 at 12:44 PM Michael Beemer @.***> wrote:
Hey @caniszczyk https://github.com/caniszczyk, we already have an ecosystem page that essentially does what you're describing.
https://openfeature.dev/ecosystem
I could see this support page as an opportunity for vendors to explain to users what kind of support and commitment they can expect.
FYI @open-feature/governance-board https://github.com/orgs/open-feature/teams/governance-board
— Reply to this email directly, view it on GitHub https://github.com/open-feature/openfeature.dev/issues/390#issuecomment-1973737702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIORLZMB45WGGMIII3TYWDECTAVCNFSM6AAAAABCPWWHX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTG4ZTONZQGI . You are receiving this because you were mentioned.Message ID: @.***>
-- Cheers,
Chris Aniszczyk https://aniszczyk.org
@beeme1mr Do you have a list of orgs that you want me to list on the support page?
Hey @thisisobate, sorry for the delay. I was out sick for most of last week.
This will have to be something we pick back up after KubeCon. I think this is a great initiative but I won't have time to work on it this week.
Alright. Thanks for the response @beeme1mr
Hi @beeme1mr, just following up. Are there any next steps we can take here, we've had a PR (https://github.com/open-feature/openfeature.dev/pull/416) open for a while.
https://openfeature.dev/support-training