We need to get a docs site up and running. Things we'll want:

• landing page
• styling/branding consistent with OpenFeature
• basic structure
• multi-language code snippet component of some sort

We need regular project meetings. Until we have a charter on https://community.cncf.io/, we can use individual zoom accounts

• - Agree on the timeslot: https://doodle.com/poll/tvncfguy3wxyhqma?utm_source=poll&utm_medium=link
• - Update contributing guidelines with the meeting info
• - Created a Google Doc for meeting notes
• - Announce the first meeting

GitHub Username

@aepfli

Requirements

• I have reviewed the community membership guidelines https://github.com/open-feature/community/CONTRIBUTOR_LADDER.md
• I have enabled 2FA on my GitHub account. See https://github.com/settings/security
• I have subscribed to the Slack channel (use http://slack.cncf.io/ to get an invite)
• I am actively contributing to 1 or more OpenFeature subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
• #179

Sponsors

• @beeme1mr
• @toddbaert

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.

List of contributions to the OpenFeature project

• PRs reviewed / authored:
  • https://github.com/open-feature/community/pulls?q=+is%3Apr+author%3Aaepfli+
• Issues responded to
• Subprojects I am involved with

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

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.

Please use this template.

Title

• Description: (2-5+ sentences)
• Expected outcome:
• Recommended Skills:
• Mentor(s): (Name, github, email)
• Expected project size: (175 or 350 Hours)
• Difficulty: (Easy, Medium, or Hard)
• Upstream Issue (URL):

#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

• Technical steering committee
• Governance board (if not merged in the steering committee)
• Official Maintainer roles for the specification, core service and integrations
• Official Project Member role
• Contributor ladder, including qualifications and the approval process
• TBD: Advisory board
• TBD: Outreach/Events committee

Description

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

Proposal

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.

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.

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 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.

Proposal

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.

What do we want?

1. We want to have an easy and trackable way of assigning different permissions to members of our organization.
2. We want to have a straightforward approach with little to no duplication or too many points to edit alignment
3. We want to organize our members in teams with certain aspects.
4. We don't want to assign permissions per individual but on a team basis, so if you want specific permissions, you're part of a certain team.
5. We want to group repositories for teams, aka one team is responsible for multiple repositories - to reduce maintenance efforts
6. We also want to have overlapping teams for repositories, as there might be the need to separate some access

Permission structure

Organization Level

First, we do have roles on organizational level like:

Owners
Members

With respective permissions

Repository Level

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

Proposal

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.

References

• https://github.com/kubernetes/org

Overview

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

Assets

• Figma files

Objective

Configure the first interaction GitHub action to welcome new users to the project.

The proposal process can be found here:
https://github.com/cncf/toc/blob/main/process/project_proposals.adoc

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.

Detected dependencies

None detected

• Check this box to trigger a request for Renovate to run again on this repository

The license section references a blog post but doesn't include a link.

https://github.com/open-feature/community#license

I’d like to propose that OpenFeature participates in the Google Summer of Docs project.

I’m happy to mentor a project.

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:

Key:

GitHub Username

@Arhell

List of contributions to the open-feature project

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

I would like to nominate myself as a candidate to join the bootstrap governance board.
(Thanks @AloisReitbauer for the reminder to apply here! )

Relevant prior-art

• I bring commercial & technical experience to the Open Feature project to achieve wider adoption and success.
• I am the author of flagD and Open feature operator and now actively maintain these with the community.
• I am actively participating in the wider cloud ecosystem and am looking for collaborative opportunities for us to enable solutions for real-world problems.

Goals

• Establish and run regular governance meetings
• Establish an enhancement process.
• Help to define the charter for the coming year
• Support GB, TC and maintainers on establishing the roadmap for the next 12 months
• Help to build an end-user outreach group.

If you would like to support my nomination, please add your +1 below. Thank you!

GitHub Username

@Sindhuinti

Requirements

• [✅ ] I have reviewed the community membership guidelines https://github.com/open-feature/community/CONTRIBUTOR_LADDER.md
• [✅ ] I have enabled 2FA on my GitHub account. See https://github.com/settings/security
• [ ✅ ] I have subscribed to the Slack channel (use http://slack.cncf.io/ to get an invite)
• [✅ ] I am actively contributing to 1 or more OpenFeature subprojects
• [✅ ] I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
• [ ✅ ] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
• [✅ ] I have created a pull request, adding myself to the members of the organization within the community configuration

Sponsors

• @beeme1mr
• @staceypotter

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.

List of contributions to the OpenFeature project

• PRs reviewed / authored
• Issues responded to
• Subprojects I am involved with

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.

Issue to track the public announcement of OpenFeature.
Working doc is here

Please indicate your involvement

http=>https

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!

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

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.

It is kind of hard to get people notified and involved in communication - especially those requiring real-time answers.

• GitHub - We all drown in issues and notifications
• Slack - We have the CNCF Slack channel but cannot use @here or @channel to notify people.

What should we use going forward?

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 Bootstrap Governing Board as defined in the governance charter.

The proposal for voting:

• Appoint Five bootstrap governing board members
  • Michael Beemer, Dynatrace
  • Ben Rometsch, Flagsmith
  • Justin Abrahms, eBay
  • Kevin Chu, GitLab
  • Pete Hodgson, Independent
• Reserve two more seats for now until more parties join

Please vote 👍/👎 in this issue or comment below. Any community member can vote.

Objective

Configure the close stale issues and PRs GitHub action to automatically close issues that have become stale.

The project needs a logo. Temporary logo for bootstrap:

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.

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:

• Approve the Technical Steering Proposal #46. As agreed at the meeting, we can extend the committee later as needed
• Appoint the bootstrap technical steering committee
  • Todd Baert, Dynatrace
  • Steve Arch, CloudBees
  • Dan O’Brien, LaunchDarkly

Please vote 👍/👎 in this issue or comment below. Any community member can vote.

Hacktoberfest prep

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.

Proposal

In order for a repo to participate the hacktoberfest topic must be set. This should be done in the following repos:

• js-contrib
• java-contrib
• go-contrib

For SDKs without associated contribs repos, we could create issue to have the community help bootstrap them. Eligible SDKs include:

• PHP
• Python
• .NET

As per the Hacktoberfest maintainers guidelines, the following requirements must be met per participating repository:

• Apply the “hacktoberfest” label to issues you want contributors to help with in your GitHub or GitLab project.
• Add a CONTRIBUTING.md file with contribution guidelines to your 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.

1. Go to repo
2. Open pinned Hacktoberfest issue
3. Create issue using Hacktoberfest issue templates (hooks, providers)
4. New issue is created with "pending-acceptance"
5. Repo maintainer reviews issue. If approved, "pending-acceptance" label is removed, "hacktoberfest" label is added, reporter is assigned.
6. PR is reviewed. If approved, the PR is merged or hacktoberfest-accepted is added. In case of spam, the PR is closed and the label spam is added.

How OpenFeature maintainers can help

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!

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!

The CNCF requires CLA or DCO. Currently CDO is being used. Update the readme to reflect that.

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.

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

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!

Update the governance section to reflect the current CNCF status.

The current tagline Cloud Native Feature Flag Management puts too much focus on cloud native and doesn't mention anything about standardization.

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:

• SDK (SDK repos)
• K8s ("cloud native" components such as flagd and the OpenFeature Operator)
• spec (spec and schemas, etc)
• doc (docsite, obviously... should this also include the website? openfeature.dev, if so, what's a better name)?
• community (no sure about this one, but possibly it would be about governance docs, etc)

We have a new domain, and it is time to migrate

GitHub Username: @staceypotter

Requirements

• I have reviewed the community membership guidelines https://github.com/open-feature/community/CONTRIBUTOR_LADDER.md
• I have enabled 2FA on my GitHub account. See https://github.com/settings/security
• I have subscribed to the Slack channel (use http://slack.cncf.io/ to get an invite)
• I am actively contributing to 1 or more OpenFeature subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines. Among other requirements, sponsors must be approvers or maintainers of at least one repository in the organization and not both affiliated with the same company
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
• I have created a pull request, adding myself to the members of the organization within the community configuration

Sponsors

• @beeme1mr
• @toddbaert

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.

List of contributions to the OpenFeature project:

• PRs reviewed / authored: #187
• Issues responded to
• Subprojects I am involved with

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:

• Establish and run regular governance meetings
• Establish an enhancement process.
• Help to define the charter for the coming year
• Support GB, TC and maintainers on establishing the roadmap for the next 12 months
• Help to build an end-user outreach group.

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!