community dashboard

[parispittman]

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]

Hey @parispittman I wanna work on this issue can you help me out?

[parispittman]

@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

[halcyondude]

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) obtain Neo4j Enterprise License for OSS (clustering, bloom, metrics, ...) cncf/landscape-graph#40 (comment)

On prior art

• Augment existing data model w/ learnings from github.com/community-graph cncf/landscape-graph#5
  • https://github.com/community-graph
  • https://github.com/community-graph/dashboard (useful bits)

On design targeted to enable community engagement

• (in progress) --> design: Sub-Graph Modules (sgm)  cncf/landscape-graph#54
• (next) https://github.com/orgs/cncf/projects/7/views/2

[AvineshTripathi]

Hey @halcyondude i have tried looking for docs to try this locally unfortunately I couldn't find one can you help me with this

[halcyondude]

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
• design: Sub-Graph Modules (sgm)  cncf/landscape-graph#54
• Create GraphQL endpoint, leveraging neo4j graphql library v3 cncf/landscape-graph#4

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[halcyondude]

/remove-lifecycle stale

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

[imnmo]

@halcyondude is there any update?

[k8s-triage-robot]

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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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-ci-robot]

@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/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was 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

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.