Skip to content

Translation

Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.

Participate in the methodologies

You can improve ASILO, MILPA and SCAFFOLD without belonging to Kasai Labs. Contributions can cover writing, fictional examples or sanitised real cases, translation, accessibility, sources and requirement evaluation. You can also identify a contradiction or propose a methodological change without writing code.

These pages are the shared source for contribution, governance and participation policies. They are maintained in Git and displayed in MkDocs. The repository's entry files link to these policies; a proposed change to them follows the same review process as the rest of the documentation.

Take part in any language

You can open Issues, comment and propose changes in the language you prefer. You do not need to write in Spanish or English to take part. Maintainers may use machine translation to understand your contribution and will tell you when they do; if a sentence can be read two ways, they will ask before deciding. The normative text is kept in Spanish, so an accepted proposal is then written in Spanish and reviewed with you when possible.

Choose a contribution

You want to… First step
Correct a typo or link Submit a PR (pull request) with the correction and its check.
Clarify an explanation or translation Identify the Spanish reference text and explain the difference.
Add a source or example Explain which claim it supports; use fictional data and verifiable references.
Contribute a sanitised real case Obtain written consent from the people or organisation involved and anonymise the case; a maintainer reviews the anonymisation before it is merged. Do not attach the consent to the Issue or the PR.
Change a requirement or its scope Open an Issue with the ID, edition, problem and expected impact.
Review a proposal Comment on its Issue or PR with reasoning and sources.
Report a sensitive problem Follow the reporting procedure.

A fork is a copy of the repository where you can work without write permissions on the original. A branch groups the changes for a contribution. A pull request (PR) proposes integrating that branch and retains its discussion and review. Codeberg documents this workflow in its fork and PR guide.

From an idea to a PR

  1. Consult the repository and locate the affected page or requirement. For a substantive change, open an Issue with the problem, scope and evidence. A minor correction can start directly as a PR.
  2. Create a fork in your Codeberg account and a descriptive branch, such as docs/milpa-provenance-example. Keep one focused contribution per branch.
  3. Edit the necessary files. You can review Markdown without installing tools; to build the site, use this repository's instructions and dependencies. Participation requires no access to other repositories or ecosystem services.
  4. Write and review Spanish first. A translation identifies the source page and revision, preserves IDs, conditions, figures and normative force, and records unresolved differences. English is informative; follow the editorial axioms.
  5. Run the documented checks relevant to the change. If you cannot run them, state this in the PR with the reason; do not present a pending check as passed.
  6. Submit the PR from your branch. Describe the problem, affected files and IDs, outcome, evidence, version impact and checks. Link the Issue when one exists and disclose relevant artificial intelligence (AI) assistance.
  7. Respond to review. The maintainer integrates once observations are resolved and the decision required for that change type is recorded. Governance explains who reviews, who decides and how to request reconsideration.

Check a contribution

With Python 3.11 or later, create a virtual environment and install requirements-docs.txt from the clone root. With that environment activated, run the common review:

python scripts/check-all-docs.py

The command checks links, terms, normative integrity, diagram sources and translations; it then builds MkDocs with --strict in an owned temporary directory and scans source and site for sensitive patterns. Matching hashes detect changes; they do not demonstrate linguistic equivalence. A scanner without findings does not prove sensitive data is absent.

For a visual change, also review the site on desktop and mobile, textual explanations, labels and SVG (Scalable Vector Graphics). Record environment, result and pending work. This is neither an audit of implementation software nor an accessibility or security certification.

Sources, authorship and AI assistance

The contributor is responsible for the submitted text, including when using AI to draft, translate or research. State which task the tool assisted and what you verified: for example, “AI assisted the first draft; the contributor reviewed sources and equivalence.” Disclosure replaces neither source review nor human authority. Use synthetic examples or sanitised real cases with written consent, and avoid sending sensitive data to external tools. Check that the AI provider's terms allow you to contribute the output, and do not upload third-party material you cannot share. If a commercial, work or personal interest relates to your proposal, declare it in the PR; declaring it does not prevent you from contributing.

Preserve each resource's attribution, license and provenance. Contribute only material you can distribute under the applicable license. Original text is under CC BY-SA 4.0, unless otherwise indicated; the official summary explains attribution, changes and sharing adaptations under its terms. Consult LICENSE and ASSETS.md in the repository for the full text and resource exceptions. PR review governs integration into this repository; it does not restrict the copying, adaptation or fork rights the license grants.

Brand assets and fonts retain their specific conditions. Scripts, tests, templates, CSS and JavaScript are under Apache-2.0, because Creative Commons recommends specific software licenses. REUSE.toml sets the license for each path and NOTICE summarises it. A contribution enters under the license of the file it changes; no assignment of rights is requested.

Start without a prepared change

Open a short Issue with the relative path, paragraph or ID and the question you cannot resolve. Include no credentials, personal paths, or unsanitised real case files or screenshots. A focused observation already helps improve the documentation. Public discussion records participation; it alone establishes neither community approval nor methodology adoption.