Gather Data for Tension in Constituencies
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 550
- Forks
- 31
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 1
Description
We need to gather data / create a process around what happens when constituencies are in conflict.
We should try to find examples of tensions (performance seems the easiest to gather data around) and see what kinds of compromises or solutions were made reactively and see if we can form some sort of historical record of patterns/processes/data that were important in making those decisions. Importantly, this is not just about implementation, but also around identifying experts in the affected systems and which systems were affected.
From that record, we could then start to create a list of important things to consider and/or even a checklist of things that have been considered.
Contributor 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.
Research direction
Start by collecting examples of constituency tensions, with performance-related cases suggested as the easiest entry point. Record the reactive compromises or solutions, affected systems, and relevant experts. Done means there is a historical record from which recurring patterns, decision factors, and a consideration checklist can be identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100