.github's People
.github's Issues
Create a shared `GOVERNANCE.md`
Write down governance rules for this community. Cover following topics:
This is a brain dump, feel free to extend.
- How to become a member:
- Create and commit to maintaining a plugin - becomes code owner of that plugin
- Asks for it and it's approved by project area maintainer to join a wider project area group
- Is nominated by a maintainer
- Who is a maintainer
- Define project areas
- Contributor roles are managed through github groups
- Repositories have github groups serving as code owners per area
- Access is reviewed annually
- Member who is not active will lose merge/review permissions and will be recognized as a honorable/emerit member of the team (remove from group but left in org and added to a running doc of recognized members/authors)
Add generic github issue templates for .github
What needs to be done?
Add generic github issue templates to the .github repository to serve as default templates for the organization.
Dependency Dashboard
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
Open
These updates have all been created already. Click a checkbox below to force a retry/rebase of any.
- chore(deps): update docker/build-push-action digest to 5cd11c3
- chore(deps): update docker/setup-buildx-action digest to 988b5a0
- chore(deps): update docker/setup-qemu-action digest to 49b3bc8
- chore(deps): update redhat-actions/podman-login digest to 4934294
- chore(deps): update actions/create-github-app-token action to v1.10.3
- Click on this checkbox to rebase all open PRs at once
Detected dependencies
github-actions
.github/actions/build-and-push/action.yaml
docker/setup-qemu-action 5306bad0baa6b616b9934712d4eba8da2112606d
docker/setup-buildx-action edfb0fe6204400c56fbfd3feba3fe9ad1adfa345
redhat-actions/podman-login a7d8d3e6447c1d7ea679172c7d10c7723d49dbf4
docker/build-push-action 9f6f8c940b91232557f8699b21341a08624a8dce
.github/actions/mirror-images-and-create-manifests/action.yaml
redhat-actions/podman-login a7d8d3e6447c1d7ea679172c7d10c7723d49dbf4
redhat-actions/podman-login a7d8d3e6447c1d7ea679172c7d10c7723d49dbf4
.github/workflows/add-to-project.yaml
actions/create-github-app-token v1.6.3@f04aa94d10cf56334d1c580e077ce2e3569e805d
.github/workflows/setup.yaml
- Check this box to trigger a request for Renovate to run again on this repository
add blank issue template to .github
What needs to be done
Disable blank issues in favor of a blank issue template to help ensure all new issues have the status/triage
label
Automatically add every new issue to "janus-idp planning" project
To make planning easier, we want to ensure every issue is in the "janus-idp planning" project.
Right now, I can see two options for how this can be done.
- create a GitHub action (in .github repo) that will be triggered periodically (nightly should be ok) that scans through all issues in all repos in this org that are not in the project (or that were created since the last run) and adds them to the project
- github action that will be triggered on issue creation on each repo
benefit of 2) is that it will be quicker, but downside is that will be a separate action for each repo (workflows can be reused, so this will be defined in one place
benefit of 1) is that everything will be in one place but a bit slower (nightly)
Acceptance criteria:
- every new issue created in any repo in this org is automatically added to "janus-idp planning"
Comply with new GOVERNANCE.md model
Governance #20 is merged now, so we should go and apply the changes in order to make us compliant.
Can you please help me fill in the teams with appropriate members? https://github.com/orgs/janus-idp/teams
Please remember: Maintainer teams have write access to their assigned repositories. If we need somebody to just triage/look through issues we don't need them to be maintainers.
Teams starting with [DEPRECATED]
are the teams we had before, and should eventually go away. So we should make sure everybody who should own/maintain anything is captured by the "new" teams. I'll be also creating a bunch of Draft PRs creating/updating the CODEOWNERS
to match the governance model. These should go in once we're sure the teams are staffed properly.
- New github teams populated and reviewed
- Old teams removed
-
CODEOWNERS
created in individual repositories.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.