contributor-site
contributor-site copied to clipboard
kubernetes
community dashboard
https://github.com/cncf/devstats/issues/229
moving from devstats as this might be the better place for it anyway.
Display community facts and quantitative information.
-twitter stats for https://github.com/kubernetesio (impressions, shares, etc) -slack stats (messages sent, # of channels, etc) -meetup stats (# of meetups, # of members, etc - this is on the website too) -YouTube playlists - how many, link to last meeting on the list -current release and other release stats -chairs and tech leads stats (changes to sigs.yaml in the community repo: how many new chairs/tls this year, avg tenure, etc) -github - number of repos in the org
TODO where on the site? break down the needs of each one / if it has an api / how we get keys to it
@SuperAayush - for sure, come to #sig-contribex on slack
we might be able to use this https://github.com/cncf/landscape-graph#how-can-a-graph-help-us
Yes! How can I engage? I've created this so that it could be (specifically) a community dashboard. Here's a few things of note happening in the project in the last week :)
On hosting logistics:
- (in progress) https://github.com/cncf/landscape-graph/issues/40#issuecomment-1111662444
On prior art
- https://github.com/cncf/landscape-graph/issues/5
- https://github.com/community-graph
- https://github.com/community-graph/dashboard (useful bits)
On design targeted to enable community engagement
- (in progress) --> https://github.com/cncf/landscape-graph/issues/54
- (next) https://github.com/orgs/cncf/projects/7/views/2
Hey @halcyondude i have tried looking for docs to try this locally unfortunately I couldn't find one can you help me with this
Yes certainly, this is still very early days :)
If you want to experiment today, start here --> https://github.com/cncf/landscape-graph/blob/main/apps/local-docker/local-docker-neo.sh
This will yield a local neo4j database running in docker, populated with the latest landscape data, however this is a very basic data model. Active development happening now to move to GraphQL as the source of truth (w.r.t. schema), with the Neo4j Database generated and in many cases populated via GraphQL Mutations.
That work is in flight here:
- Kanban: https://github.com/orgs/cncf/projects/7/views/2
- https://github.com/cncf/landscape-graph/issues/54
- https://github.com/cncf/landscape-graph/issues/4
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
