Project and maintainers¶
Legible Protocol brings together an open specification, reference code and writing on the economics of legibility, in draft form for tests and contributions. Its current maintainer is Diogo Carlotto, author of Open Legibility and The Economics of Legibility.
Maintenance and participation¶
At this stage, the maintainer reviews and incorporates changes. Other people can contribute and take on component maintenance, agreeing on responsibilities and access. The maintainer list will be updated as this happens.
The proposed GitHub organization will group repositories and collaboration permissions. Each component identifies its maintainers. Participants remain responsible for the environments where they run it; the project does not operate their Legible spaces.
Contributions offered for incorporation follow DCO 1.1 and each repository's review and Git-signing policies. These procedures do not condition the creation or validity of Legible records in independent spaces.
Editions, records and independent proposals¶
The publication identifies the specification edition it presents. Its maintainers choose the records accompanying the materials. The collection contains only selected records and may remain empty.
A contribution not incorporated here may continue circulating elsewhere. The fork conventions explain how to identify independent proposals with their own names, versions and maintenance.
Repositories and reading site¶
Sources are organized in three repositories in the LegibleProtocol organization.
protocol contains the specification, formats, reference code and tests.
website contains the site pages, their translations and the generator.
publications contains the book, papers and their translations, with its own
Issues for discussing arguments, suggesting references and proposing corrections.
Proposed changes and contributions are tracked in the relevant repository.
The site presents these materials for people and AI tools to read. The displayed specification corresponds to the edition identified in the publication, and the generator checks the technical files used for that preparation. Complete sources remain in the repositories; first-use attachments and examples remain available here.
Project addresses¶
GitHub organization · Protocol repository — invitation required · Website repository — invitation required · Books and papers on GitHub — invitation required · Contact