Closed danry25 closed 11 years ago
It should provide all the information needed to set up a tower from scratch, including POE and such, but I'm counting at least one (and in special cases, two) link hop(s) as the boundary for that scope. It makes sense to break POE stuff out into its own thing, and have RITower.md link to it.
This would probably be a good time to think about organizing the content into subdirectories, so that different types of "products" are all in one dir, stuff like POE.md is in another. I don't know how I'd like those dirs named though, and the repo is still small enough that we don't have to care about it yet, so let's let it all stew in the git root for now, and move it/fix links later.
On Mar 2, 2013 10:21 PM, "danry25" notifications@github.com wrote:
Hey, I was wondering what you were thinking as to how extensive RITower.md should be? We can do separate documents like POE.md, etc., but what are you looking to include in this repository, and how would you like it organized?
— Reply to this email directly or view it on GitHubhttps://github.com/Roaming-Initiative/roaming-initiative-hardware/issues/12 .
That sounds like a good plan, although beyond RITower.md I'd like to do Omnitik.md, Linkcalc.md, etc that are all linked to from RITower.md, or in edge cases two links from RITower.md.
I'll probably end up creating a radio folder eventually, and inside that I'll probably have a few subfolders, but for now there isn't a need for that level of organization, at least not until I write up 10+ .md files on radios.
Hey, I was wondering what you were thinking as to how extensive RITower.md should be? We can do separate documents like POE.md, etc., but what are you looking to include in this repository, and how would you like it organized?