meta: parallel contributions are outpacing a shared development line
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
This is a governance proposal, not a code task: read the existing CONTRIBUTING.md, then skim docs/experiments.md, CMakeLists.txt and the two competing shim PRs (#183, #189) to see the overlap the issue describes. The concrete deliverable is one paragraph in CONTRIBUTING.md stating the three milestones and the merge rule, and it is done when the maintainer agrees in this thread. The four comments so far are discussion, so a newcomer should not act until a decision lands.
Written by the indexing model from the issue text.
Description
Problem
The repository is receiving more parallel changes than it has capacity to review, verify or integrate into a coherent direction. Each change is individually defensible under the current rule ("one pull request, one reviewable behavior"), but the rule says nothing about order. The result is breadth-first growth: many correct pieces, no vertical slice.
This is not a criticism of any contributor. It is a structural observation about the current throughput.
Evidence
Snapshot of main when this was written:
- 25 open pull requests.
docs/experiments.mdis edited by 17 of them.CMakeLists.txtis edited by 11 of them.tools/pe_map.cppby 5,tests/offscreen_check.cppby 4,tests/cpu/native_map_check.pyby 4.
Recent examples of the resulting friction:
| Observation | Consequence |
|---|---|
#183 (build a desktop xmem.dll) and #189 (serve the Bink shim from era_heap) pursue the same shim contract in different directions |
One of them has to be reframed after the other lands; effort is duplicated |
A CI failure on #212 came from tests/intake/paths_check.py:118, which encoded "an unknown loader hash produces no findings" |
The contract lived only inside a test; a parallel change to the same behavior broke it |
| The three most recent merged PRs had no review comments before merge | Review capacity is not keeping pace with submission |
src/ contains one 32-line runtime file |
Every experiment re-implements its own shim, because there is no shared layer to extend |
Risks
- Hidden contracts. When a behavior is only expressed by a test assertion, another contributor cannot see it. Changing the behavior then looks like a regression.
- Duplicate directions. Two PRs can implement the same missing piece in incompatible ways, and neither author knows until both are reviewed.
- Review depth. With 25 open PRs, the default becomes "does CI pass" rather than "is this the right change". CI does not run the hardware tests.
- Rebase churn.
docs/experiments.mdandCMakeLists.txtare edited by almost every PR, so every merge invalidates several branches. - Breadth without a vertical slice. The README's central unverified claims (title CPU execution, startup, frame rate) are not moved by any single new experiment, and no experiment is required to connect to another.
- Evidence drift.
docs/experiments.mdgrows faster than anyone can audit. Platform differences appear late, for example the Windows 10 in-box WARP failingpixel_aot_warpon the NLG NaN case. - Incentive mismatch. Fast merges reward volume. Contributors optimise for what is rewarded.
Proposed change
A lightweight development line plus a merge rule. No code changes, no new process tooling.
Three milestones, in order:
- Loader usable.
pe_mapplus a shared shim contract, TLS data, forwarded exports. Completion: a source-built DLL maps with every import and export resolved through one documented interface. - Measured startup. EXE entry point, a TLS value read on two threads, and an initialisation log compared with a normal Windows launch (#165).
- One real caller. Trace a higher-level caller into the Bink allocation path, as the README's CPU row asks.
Merge rule: every new pull request states which milestone it unblocks. If it unblocks none, it is welcome but goes to a visible later list rather than competing with the current milestone. The maintainer still decides what merges; the rule only makes the cost visible.
Two supporting practices:
- A consolidation lane: the shared lowerer, the shim contract and the capability table (#166) are first-class work, not refactors to squeeze between features.
- Review exchange: a contributor who opens a pull request reviews one outside their own area. This is a norm, not a gate.
Alternatives
- Status quo. Keeps momentum, but the drift persists and the vertical slice stays absent.
- Hard freeze on new experiments. Effective, but it risks losing the contributors who are currently active.
- Area ownership. Clearer responsibility, but heavy for a project this size and it would slow down the people already doing the work.
Verification
The proposal works if, after two weeks:
- the open pull request count stops growing;
- most new pull requests name a milestone;
- at least one milestone completion condition is met;
- duplicate directions are caught before both are implemented.
None of this needs a bot or a new label. It can be written into CONTRIBUTING.md in one paragraph if the maintainer agrees.
Scope
- No code changes, no test changes, no new dependency.
- No retroactive closing of open pull requests.
- No criticism of individual contributors; the examples include the author's own work.
- No game files, dumps, distribution links or credentials.
AI-assisted.
- Dominant language
- Python
- Stars
- 696
- Forks
- 61
- Avg merge
- 25m
- Merged PRs (30d)
- 171
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 R0Y00/Xbox2Windows
-
Difficulty 2/5 Half a day Newbie friendliness 80/100
R0Y00/Xbox2Windows#254 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 20/100
R0Y00/Xbox2Windows#207 · 2 comments ·
Maintainers usually reply within 1 day
-
pe_map cannot resolve a forwarded exportPossibly taken @raulmoracode claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
R0Y00/Xbox2Windows#206 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
R0Y00/Xbox2Windows#179 · 6 comments ·
Maintainers usually reply within 1 day
-
Replace the hardcoded operation chain in offscreen_check with a capability tablePossibly taken @lambirou claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
R0Y00/Xbox2Windows#166 · 3 comments ·
Maintainers usually reply within 1 day
All issues in R0Y00/Xbox2Windows
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
py-econometrics/pyfixest#2072 ·
Maintainers usually reply within 1 day
-
~planning docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Kromatic-Innovation/athenaeum#3084 ·
Maintainers usually reply within 1 day
-
Bosch Room Thermostat II number entities offer -500 to 3000 °C setpoint limits and a -32768 to 32767 °C outdoor temperaturePossibly taken @zigpy-review-bot claimed this today. Openbot: code audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zigpy/zha-device-handlers#5769 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day
-
[BUG]: list_tables skips tables when an include pattern has a wildcard inside the catalog or schema partPossibly taken @0z5a claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
databrickslabs/dqx#1724 ·
Maintainers usually reply within 1 day