Skip to content

Latest commit

 

History

15 Commits

Folders and files

Repository files navigation

Contributing to StrataMesh Laboratory

Open contribution is welcome. Canonical code lives under StrataMesh-Laboratory.

@amcmorais is one contributor (and org admin / reference-node operator via AMCM ENI). Reviews and merges are organisation work, not a personal mainline.

Discussion

Use the lab forum for design talk (code review stays on GitHub): https://stratamesh.discourse.group

Where to contribute

Repository Focus
stratamesh-core Protocol core, workers, DAG, tip selection, docs
stratamesh-laboratory Charter, posture, research ladder
calhegas-morais-node Reference Fog node registry
stratamesh-impact-fund Impact Fund app · challenges · Sponsors rails

Do not use amcmorais/stratamesh-core — it is archived (outdated personal path).

How (fork → PR)

  1. Fork the target repo under your account.
  2. Branch from main (feat/…, fix/…, docs/…).
  3. Open a Pull Request against StrataMesh-Laboratory/<repo>:main.
  4. Fill the PR template; link issues / impact challenges when relevant.
  5. Keep changes reviewable; add tests for behavioural core changes.

Issues and Impact challenges (impact-challenge label) are first-class entry points. Funded work uses the same PR path with metrics on the issue.

Lab honesty

This is lab / not mainnet. Do not claim production finality, aBFT, or live PQ. See the public roadmap in stratamesh-core.

Licence

Unless noted otherwise, contributions are under the repository’s licence (MIT on core).

Conduct

Be precise, technical, and respectful. No harassment. Security-sensitive reports: prefer private contact to the operator (geral@eni.calhegasmorais.pt) before public issues when disclosure could harm the node.

About

Organization profile, security policy, contributing, CODEOWNERS

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors