open-feature / community Goto Github PK
View Code? Open in Web Editor NEWOpenFeature project community and governance
Home Page: https://openfeature.dev
License: Apache License 2.0
OpenFeature project community and governance
Home Page: https://openfeature.dev
License: Apache License 2.0
I would like to nominate myself as a candidate to join the bootstrap governance board.
(Thanks @AloisReitbauer for the reminder to apply here! )
If you would like to support my nomination, please add your +1 below. Thank you!
Please use this template.
I am offering to join the bootstrap governance board for one of the open seats and help establishing a governance process based on experience in other projects.
My key goals:
I have been working intensely on OpenFeature and helped assemble the project team. I would like to make my contribution more official also representing one of the major contributing organisations.
If you support please add your +1 below. Thank you!
The license section references a blog post but doesn't include a link.
Update the governance section to reflect the current CNCF status.
Community, Membership, and Repository management is complex on its own.
With a growing community, keeping an overview gets harder and harder.
Instead of relying on manual actions, I recommend switching to a GitOps approach, utilizing Peribolos.
Peribolos offers a great variety of settings and can be used to manage organization management, team assignments, and repository permissions.
Peribolos is developed and used by Kubernetes and is a good fit for OpenFeature.
First, we do have roles on organizational level like:
Owners
Members
With respective permissions
Additionally, if you are part of the organizational level, you can also be one of those roles just for the repository or repository group:
Repo-Admin
Repo-Maintainer
Repo-Approver
Ultimately, we can setup the repo permissions for each repository, which means a lot of duplicated configuration effort, but grouping would be easier and way better to handle.
Furthermore, it would represent the community structure in a better manner.
As the configuration file for this structure would be already quite big and cover a lot of duplication
I propose consolidating this into a leaner structure with an automatic merge (like Kubernetes is doing https://github.com/kubernetes/org) tailored to our needs. We will have our Directory per organization we manage and a subdirectory per group containing the necessary information.
The org.yaml
will contain basic information about the organization, such as general membership, description, etc.
Also it will contain a group for Community maintainers
The group configuration will contain the following structure, eg. for java
repos: # the repositories belonging to this team
- java-sdk
- java-sdk-contrib
approvers: # list of users who are approvers for this group and its repos (GitHub Permission: triage)
maintainers: # list of users who are maintainers for this group and its repos (GitHub Permission: maintain)
admins: # list of users who are admsin for this group and its repos (GitHub Permission: admin)
Our merger will then take all this information to generate the configuration and apply it via GitHub Action to the defined organizations.
members
of the organization within the community configurationEach sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors confirmation before submitting the request.
We need to setup intermediate governance process while we are setting up the project. Most likely it is to be replaced once the project onboards more contributors
Hacktoberfest is an annual event that promotes open source participation. OpenFeature would like to support this initiative by offering guidance for contributing to the project. One of the best ways to get involved would be to develop hooks and providers in various contributing repos.
In order for a repo to participate the hacktoberfest
topic must be set. This should be done in the following repos:
For SDKs without associated contribs repos, we could create issue to have the community help bootstrap them. Eligible SDKs include:
As per the Hacktoberfest maintainers guidelines, the following requirements must be met per participating repository:
Taking into account the requirements, the following user journey could be implemented in contrib repos. This would allow participants to submit proposals for adding new hooks and providers.
hacktoberfest-accepted
is added. In case of spam, the PR is closed and the label spam
is added.Volunteer to review Hacktoberfest issues and PRs. Please reply with a comment below with the language(s) you're willing to support in reviewing. Together we can take this great opportunity to expand our community and the feature flagging ecosystem overall!
We have a new domain, and it is time to migrate
We need regular project meetings. Until we have a charter on https://community.cncf.io/, we can use individual zoom accounts
http=>https
We have merged our peribolos-based configuration recently, and it is doing great work. But unfortunately, as this tooling resides within this repository, we're also getting updates via renovate for our tooling.
This repository should handle community-specific agendas, and managing software updates is more bloat than benefiting the purpose.
So we'd like to extract the tooling into a separate repository, but create deliverable artifacts to be used within the community repository
Migrate the go files into an own repository, and build a docker image within this repository.
This docker image should be ready for GitHub Action so that we can replace the logic of the tooling within this repository within the docker image.
members
of the organization within the community configurationEach sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors confirmation before submitting the request.
The current tagline Cloud Native Feature Flag Management
puts too much focus on cloud native and doesn't mention anything about standardization.
Please add below any links to information you'd like to share on the OpenFeature social media profiles (Twitter & Linkedin).
Don't forget to add your social media handles for tagging.
Hi Everyone,
as we will have a Kiosk for Open Feature at kubecon it would be useful to know who all will be there so we can have it covered fro the whole conference. If you could add the dates you will be there and your availability we can coordinate.
Also it would be nice to have some SWAG to give away, would anyone be interested in participating here? @beeme1mr had already found a good supplier for Kubecon EU.
Configure the close stale issues and PRs GitHub action to automatically close issues that have become stale.
Please add below any items you'd like to share on the OpenFeature social media channels (Linkedin, Twitter, YouTube) so I can schedule them for publishing this week.
Examples: project updates, new releases, blog posts, videos, future events, speaking engagements, etc.
Don't forget to add your social media handles if you want to be tagged!
Currently I keep my OpenFeature artwork here: https://docs.google.com/presentation/d/1NWpAXdpDiMR8MDMm15SGV7qiu7fNrWc2zMO7-NLcIeY/edit?usp=sharing
It would be nice to make this repository reusable by others
This issue has been created to collect all the information about what is happening at KubeCon related to OpenFeature, in order to plan a campaign for the month of October.
Issue to track the public announcement of OpenFeature.
Working doc is here
Please indicate your involvement
Name | Company | PR | Blog | Quote |
---|---|---|---|---|
Alois Reitbauer | Dynatrace |
I would like to restructure the current community site be similar to OpenTelemetry. They have quite a good practice and structure that will serve as well, too.
Reference: https://github.com/open-telemetry/community
As agreed at the project meeting on April 14 and discussed before on Slack, we want to proceed with the Bootstrap Governing Board as defined in the governance charter.
The proposal for voting:
Please vote 👍/👎 in this issue or comment below. Any community member can vote.
Hi Everyone ,
let's use this issue to track all the CFPs that have been submitted for Kubecon EU.
It would be great if you could share the title.
Please let know if you have any questions.
The O in the OpenFeature logo resembles a toggle. A fun way to use this design is to "toggle" the logo causing it to switch between dark and light mode. This could be used across various touchpoints to increase brand awareness.
Here's an example of how it could potentially look
Note: This is a recording captured original openfeature.dev website
Please add below any items you'd like to share on the OpenFeature social media channels (Linkedin, Twitter, YouTube) so I can schedule them for publishing this week.
Examples: project updates, new releases, blog posts, videos, future events, speaking engagements, etc.
Don't forget to add your social media handles if you want to be tagged!
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
This repository currently has no open or pending branches.
None detected
We need to get a docs site up and running. Things we'll want:
With increased participation in the project it's become apparent that we need to efficiently and effectively manage access to repositories. We can use Github's teams OR OWNERS_ALIASES
, combined with specific users in OWNERS
files. There's precedent here: https://www.kubernetes.dev/docs/guide/owners/
Github teams are not publicly viewable, so some projects (for example K8s) choose to use OWNERS_ALIASES
in the OWNERS
file for representing team memberships as well. I'm not sure if that's the route we want to go, but it's an option. It would require more maintenance in OWNERS
files.
My proposal is to use Github teams + OWNERS files with user references to control access. Some example teams could be:
We need Slack channels (on Kubernetes or CNCF?) and maybe other entries for the project. Not sure about creating a new Slack workspace at the moment.
It looks like we use both in different places. Which is the official one?
As agreed at the project meeting on April 14 and discussed before on Slack, we want to proceed with the Technical Steering Committee entity and with appointing the bootstrap members.
Proposal for voting:
Please vote 👍/👎 in this issue or comment below. Any community member can vote.
Each sponsor should reply to this issue with the comment "I support".
Please remember, it is an applicant's responsibility to get their sponsors confirmation before submitting the request.
https://github.com/open-feature/openfeature.dev/issues/created_by/Arhell
https://github.com/open-feature/openfeature.dev/issues?q=is%3Aissue+author%3AArhell
https://github.com/open-feature/openfeature.dev/commits?author=Arhell
I want to support the project and help fix bugs and other problems that I find.
https://github.com/open-feature/openfeature.dev
https://github.com/open-feature/docs.openfeature.dev
Thank you for your attention
The proposal process can be found here:
https://github.com/cncf/toc/blob/main/process/project_proposals.adoc
Please add below any items you'd like to share on the OpenFeature social media channels (Linkedin, Twitter, YouTube) so I can schedule them for publishing this week.
Examples: project updates, new releases, blog posts, videos, future events, speaking engagements, etc.
Don't forget to add your social media handles if you want to be tagged!
Please add below any items you'd like to share on the OpenFeature social media channels (Linkedin, Twitter, YouTube) so I can schedule them for publishing this week.
Examples: project updates, new releases, blog posts, videos, future events, speaking engagements, etc.
Don't forget to add your social media handles if you want to be tagged!
Please add below any items you'd like to share on the OpenFeature social media channels (Linkedin, Twitter, YouTube) so I can schedule them for publishing this week.
Examples: project updates, new releases, blog posts, videos, future events, speaking engagements, etc.
Don't forget to add your social media handles if you want to be tagged!
We should reach out to all of the vendors (and open source projects) in the flagging space. We'd like to let them know what we're doing, see if they want to get involved, etc.
The list:
Status | Company | Company Representative | Outreach Lead | Comment |
---|---|---|---|---|
🟩 | cloudbees | @agentgonzo | @beeme1mr | |
🟩 | flagsmith | @dabeeeenster | @beeme1mr | |
🟩 | launch darkly | @InTheCloudDan | @AloisReitbauer | |
🟨 | optimizely | |||
🟩 | split.io | @patricioe | @beeme1mr | |
🟩 | harness | @davejohnston | @beeme1mr | |
🟨 | apptimize | |||
🟩 | configcat | @sigewuzhere | ||
🟩 | unleash | @ivarconr | @beeme1mr |
Key:
Status | Meaning |
---|---|
🟩 | Interested party |
🟦 | Communication has been established |
🟨 | No contact yet |
Please add links below to the information you'd like to share on the OpenFeature social media profiles (Twitter & Linkedin).
Remember to add your social media handles for tagging.
The CNCF requires CLA or DCO. Currently CDO is being used. Update the readme to reflect that.
#1 defines only the bootstrap governance document. We will still need to create a full fledged governance model once the project is fully initialized and founding members are identified,
What is needed
Configure the first interaction GitHub action to welcome new users to the project.
I needed to put an email in the gpg key we're using to sign maven central artifacts. I used the dynatrace opensource one, but that feels weird. We should get an email address for governance things.
I’d like to propose that OpenFeature participates in the Google Summer of Docs project.
I’m happy to mentor a project.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.