Document operational and technical information about toronto-community-network HOT 13 OPEN

Done today, this issue will stay open. I've updated it to include any new issues I found previously.

from toronto-community-network.

I think it can be in this, and check off sections as they get merged.

from toronto-community-network.

Discussed in one of the meetings (ops or govnt dont remember)

Docs.tomesh.net will be a "manual" so facts an figures.

While the Journal/Blog/Event recap will be in some other location (blog maybe, or docs)

from toronto-community-network.

#54 might supersede this issue.

from toronto-community-network.

Discuss scope of issues

from toronto-community-network.

Overall network topology images: benhylau drawing and DD2k diagram

from toronto-community-network.

I think a quick way to get stuff transferred is to agree on the "chapters" index and then transfer content on there, then assign one person to go thru all of it, make everything consistent and pretty.

from toronto-community-network.

Yeah, starting to create a draft/template of all the sections sounds like the right idea. Can this be done in this issue, or should there be another?

from toronto-community-network.

Should the docs have sections explaining what the network is in depth, with an FAQ, etc? Or should that be on tomesh.net?

from toronto-community-network.

I would suggest putting the above comment as part of the first one.

that way we don't have to dig for it!

from toronto-community-network.

Done, thanks. I've left my question though.

from toronto-community-network.

#34 Supernode 1 field testing

This seems like more of a tomesh/documents write up about what we did (the event) and just the results in the docs.

from toronto-community-network.

I think it definitely depends on the nature of the write up. It'd be nice to have some info in the docs on how it was done, like with tips or important info. But any sort of narrative would be better for a blog post or document.

from toronto-community-network.