Files
zjs81 aa00a863c3 Refresh documentation and update Dutch translation
Documentation:
- Correct web transport support: USB via Web Serial in Chrome only; no
  BLE or TCP in the browser.
- Fix region scope semantics, routing modes (Auto/Flood/Manual), the
  156-byte DM limit, repeater CLI framing, the guessed-location algorithm,
  radio stats contents and settings labels.
- Add regions, image messages, radio statistics and troubleshooting guides.
- Restore coding conventions, localization workflow, storage scoping and
  transport entry points to CLAUDE.md/AGENTS.md; align build/CI commands.
- Replace the obsolete docs/BLE_PROTOCOL.md with a pointer to the
  maintained protocol reference.

Dutch (nl):
- Translate the 79 missing strings and correct existing mistranslations,
  typos and grammar (e.g. "Uitzoomen", "Handmatig", "Slowaaks", frequency
  range 150-2500 MHz).
- Use consistent terminology and informal "je" throughout; keep mesh terms
  such as repeater, node, flood, hop and advert in English.

Fixes #538
2026-09-27 13:12:23 -07:00

3.8 KiB

How to contribute to Meshcore Open

Before submitting any pull requests (PR), please review the following information.

Unsolicited PRs without previous discussion or open issues may be rejected. As may changes that are too broad (i.e. 100 files changed) or that cover too many separate changes. If the changes are clearly AI generated they may also be rejected. See more

First Step Checklist

Did you find a bug?

  • Ensure the bug was not already reported by searching on GitHub under Issues.

  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. You can also include screenshots or video.

  • DO NOT start work and submit a PR at this time, please discuss the issue and your implementation plan first.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the application will generally not be accepted.

Do you intend to add a new feature or change an existing one?

  • Suggest your change in a new issue as a feature request.

  • DO NOT start work and submit a PR at this time, please discuss the change and your implementation plan first.

  • After it is generally decided that the feature or change fits the goals of the project you can start work or open a PR if you have already started.

Submitting your patch

  • All changes should be based on the dev branch. When creating your PR please be sure to change the target to merge into dev, and when starting work on a new branch be sure to start on latest dev.

  • Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

  • Prefer one final commit per PR. The commit message should have a clear title followed by a new line and then brief description if needed. If review requires follow-up commits, maintainers may squash them before merging. See Git Mastery for more information on good commit messages.

  • Before committing changes on your branch, be sure to run dart format ., flutter analyze --fatal-infos --fatal-warnings, and flutter test. CI also checks formatting with dart format --output=none --set-exit-if-changed .. The continuous development checks will fail if issues here are not addressed before hand.

AI-use

Everyone loves some help, AI agents are a tool in many of our belts. The project is not anti-AI.

There are some limits to acceptable use however. Generally:

  • All code generated by AI should be thoroughly reviewed by the contributor.
  • The changes should be tightly controlled to not change anything out of scope for the patch, bug fix, etc.
  • The contributor should have a good understanding of what the code does and how the application works in order to effectively be able to manage the agent.

Documentation and validation

Update the relevant user guides when changing features, defaults, navigation, firmware requirements, or platform limitations. Add screenshots for visible UI changes and keep localization keys consistent across supported locales. Include protocol changes explicitly in the PR description.

Test on the platforms and hardware affected by the change. State what you tested and any untested platforms in the PR; automated builds do not prove BLE/USB/radio interoperability. Documentation-only changes need link and content checks, not a Flutter build.