New Visualization: Contributor flow by activity
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- data-visualization
Research direction
Start with the linked Fedora cohort analysis notebook and the existing 8Knot visualization and query templates. First outline how contributor activity should be represented for 8Knot, then review the current queries and the CHAOSS Data Science issue linked in the acceptance criteria. Done means documenting the visualization concept and creating a notebook and 8Knot visualization pull request; a new query is optional.
Written by the indexing model from the issue text.
Description
Please describe the background and context for this new visualization
https://rwright.fedorapeople.org/reports/notebooks/CohortAnalysis.html
Describe the perspective you'd like the final visual to give
Take inspiration from the fedora graph but develop the concept to fit the 8knot usecase and data structure
Acceptance criteria for the issue and visualization to be complete
- Take the concept -> high level overview of what the visualization will be and detail it in the issue
- Review current set of queries to see if one already gathers the information needed or a small edit could get it there
- Create visualization notebook in the CHAOSS DS WG ISSUE
- Visualization notebook -> 8Knot PR for visualization following the visualization template
- Create 8Knot visualization PR from the notebook using the visualization template
- Optional - add new query using the query template
Additional context
Add any other context or screenshots about the feature request here.
- Dominant language
- Python
- Stars
- 80
- Forks
- 92
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from chaoss/8Knot
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
chaoss/8Knot#1188 · 1 comment ·
Maintainers usually reply within 1 day
-
add CONTRIBUTING.mdOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
chaoss/8Knot#1241 · 1 reaction ·
Maintainers usually reply within 1 day
-
update references from eightknot.osci.io to eightknot.ioPossibly taken @MoralCode claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Robin-IA/Congressional-Letters-Dev#1347 ·
Maintainers usually reply within 1 day