Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

docs: fix broken install path, wrong commands and stale status in participant guides

Offen
  • Stimmt etwas nicht?
#290 2 Kommentare 0 Reaktionen 5 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@robertocarlous arbeitet bereits daran.

Seit 27.10.2026.

  • #294 von @Abidoyesimze — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Note: this review was produced by an AI agent (Claude), checking the docs against the code on develop on 27 October 2026. It may be missing context: some items may already be resolved, in progress elsewhere, or deliberately left as they are. If so, please comment and we'll tick them off or drop them.

Most of these block a newcomer from getting started.

Blocks newcomers

  • Documentation/public/setup.md:34-42: both install options fail. Option A downloads dincli-0.1.0 from main, which only has 0.2.0. Option B installs from dist/, which has no pyproject.toml (pip: "neither 'setup.py' nor 'pyproject.toml' found"). Coordinate with the install-guide issue.
  • Documentation/public/getting-started.md: says "Global Iteration 2 in progress" (line 62), but GI 2 stopped at registration. It teaches DevNet 2.0 commit/reveal steps (lines 360-384), and the live DevNet 1.0 contracts have no commit/reveal functions. Add a clear note on which network the guide is for.
  • Commands that don't exist, with the real ones:
    • model-owner registry request-registration → task model-owner register-request (roles/model-owner.md:87, # TODO)
    • model-owner registry show-request → task model-owner show-registration-request (roles/model-owner.md:103, # TODO)
    • model-owner registry request-manifest-update → task model-owner update-manifest-request (roles/model-owner.md:115, # TODO)
    • task model-owner update-manifest → task model-owner update-manifest-request (manifest.md:124)
    • task model-owner register → task model-owner register-request (workflows/model-workflow.md:200)
    • model-owner model create-genesis and task model-owner create-genesis → model-owner model create-genesis-model (manifest.md:22, 42)
    • model-owner model submit-genesis → model-owner model submit-genesis-model (roles/model-owner.md:146)
    • system get-fees → system get-registry-fee (roles/model-owner.md:60)
  • sepolia_devnet and mainnet are listed as network options (setup.md:73, cli-reference.md:13 and 38, roles/clients.md:19). din_info.json has no sepolia_devnet entry and mainnet only has placeholder addresses, so both fail. List only local and sepolia_op_devnet until they exist.

Stale or misleading

  • Developer/GOOD_FIRST_ISSUES.md (linked from the README) lists the DP review starter task as open; its own task file marks it completed in PR #89. Replace the list with a link to the good first issue label, or update it.
  • getting-started.md contradicts itself: line 98 says trust rests on "cryptographic and economic enforcement" and line 92 says the system is "fully verifiable end-to-end", while line 178 says economic and reward mechanisms are still under development.
  • README.md:24 says "Only anonymised, encrypted patterns join the network". Client model updates are uploaded unencrypted (with optional DP); only the auditors' test data is encrypted. PR #280 fixes this wording.
  • "DAO" approval: roles/model-owner.md:96, 108 and 119; "later DIN-DAO": workflows/din-workflow.md:5 and workflows/model-workflow.md:8. Approvals are by the DIN-Representative, and the DAO is deferred to post-mainnet.
  • Naming: "Infinite Zero" (14 times) vs "InfiniteZero" (9 times) across public docs; sepolia-op-devnet (getting-started.md:11, 39, 43, 134) vs the real value sepolia_op_devnet.
  • Old Telegram invite link in getting-started.md:190 (t.me/+I4Tl7foCVwwwM2Vk). Replace it with the current link, t.me/+h46VS3AnO384ZGI8.

Thin or unclear

  • Developer/DEVELOPMENT_SETUP.md: add the Python version (3.12+), Foundry install, how to run the Solidity and Python tests, and links to Documentation/technical/testing/.
  • Developer/CODE_STANDARDS.md is empty but linked from Developer/README.md.
  • Developer/CONTRIBUTING.md:15: a file path sits inside a bash block as if it were a command.
  • setup.md:76-77: a [!NOTE] callout sits inside a code block and renders as raw text.
  • Typos in workflows/model-workflow.md:195 ("manisfest") and 197 ("Protocolat", "Model Owner then register").
Vorherrschende Sprache
Python
Sterne
4
Forks
7
Ø Merge
3 T. 4 Std.
Gemergte PRs (30 T.)
34

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus InfiniteZeroFoundation/DevNet

Alle Issues in InfiniteZeroFoundation/DevNet

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.