comunes/tane
1
0
Fork 0
Code Issues Pull requests Projects Releases 7 Packages Wiki Activity Actions
Local-first, decentralized app for traditional seeds
4 commits 1 branch 17 tags 77 MiB
Find a file
vjrj 59beadc03c Add core/domain boundary doc; clarify lots (mixed year/unit per variety)
2026-07-07 01:49:35 +02:00
docs Add core/domain boundary doc; clarify lots (mixed year/unit per variety) 2026-07-07 01:49:35 +02:00
.gitignore Initial import: mockups, visual identity, stock photos, project plan, README 2026-07-06 23:58:31 +02:00
PLAN.md Rename to Tanemaki (Tane); domain tanemaki.app; package id org.comunes.tane 2026-07-07 00:40:39 +02:00
README.md Add design docs; update README/PLAN 2026-07-07 01:28:54 +02:00

README.md

Tanemaki 種まき

A local-first, decentralized app for managing and sharing traditional seeds and seedlings.

Tanemaki (種まき, "to sow / scatter seeds" in Japanese; short name Tane, 種 "seed") helps people and collectives keep a friendly inventory of their seed bank, decide what they offer, and share it locally — without a central intermediary that could control, censor, or be fined for it. The goal is both practical and political: to support traditional seed varieties and push back against the seed monopoly.

The name honors the old Japanese mutual-aid traditions around rice — yui (shared community labor) and tanomoshi (reciprocity funds) — that inspired the paper Plantare, the "community currency for seed exchange" (BAH-Semillero, 2009, CC-BY-SA). Tanemaki is the digital Plantare.

Status

Early design. See PLAN.md for the full analysis and roadmap (in Spanish). The valuable prior work lives in docs/mockups/.

Principles

  • Local-first. Works fully offline, no account, no central server. Stays useful even if no one maintains it.
  • Decentralized. Identity is a keypair you own; sharing rides on open protocols (Nostr / ActivityPub), never a central marketplace.
  • Free/libre. Copyleft software, open data formats, multilingual from day one.
  • Layered. Inventory -> Offer -> Local sharing -> Web of trust. Each layer is useful on its own.

Conventions

English is the project language for all code. Identifiers, class/field/column names, code comments, commit messages, branch names, and technical documents (data model, schemas) are written in English, without exception. This keeps the project contributable by anyone, anywhere.

  • User-facing strings are never hardcoded — they go through i18n (the app itself is multilingual by design).
  • Planning and discussion documents may be written in Spanish (e.g. PLAN.md, docs/design/data-notes.md); technical specs that feed code are in English (e.g. docs/design/data-model.md).
  • Database schema changes ship as versioned Drift migrations (drift_schemas/), one new version per change, never editing a released version. See docs/design/data-model.md §5.

License

Software: copyleft (AGPL/GPLv3, TBD). Docs & assets under CC-BY-SA where noted.