search

ewasm / testnet

Testnet planning & documentation
64 stars 19 forks source link

User documentation #19

Closed jakelang closed 5 years ago

jakelang commented 6 years ago

When the eWASM testnet goes public it will be important to have a compendium of documentation for working with eWASM and writing contracts. A decent option for this would be readthedocs.io, which is already used for the Solidity docs.

jakelang commented 6 years ago

note: The ethereum magicians fellowship is also talking about moving documentation to another site. Perhaps it could make sense to have ewasm documentation in the same spot as other ethereum docs. https://ethereum-magicians.org/t/eip-1053-a-proposal-to-move-the-content-in-ethereum-wiki-to-a-wikipedia-style-wiki-site/265

lrettig commented 5 years ago

There is no specific task here. I propose removing this from the Public testnet (initial release) project, and instead putting concrete tasks there (like #25). Alternatively, a list of subtasks could be added in the description here.

jakelang commented 5 years ago

yeah getting rid of this is fine.

On Tue, Nov 13, 2018, 11:21 Lane Rettig <notifications@github.com wrote:

There is no specific task here. I propose removing this from the Public testnet (initial release) project, and instead putting concrete tasks there (like #25 https://github.com/ewasm/testnet/issues/25).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ewasm/testnet/issues/19#issuecomment-438330930, or mute the thread https://github.com/notifications/unsubscribe-auth/AHEQhxRKCgUSnjXxRg48EiPqJEW6ykGOks5uuvGFgaJpZM4Triia .

axic commented 5 years ago

I prefer individual tasks so that the project board can track it.