Consistency of names across different spaces about toronto-community-network HOT 12 CLOSED

I feel ppl will type a short in chat anyways, and it's better to do that than TOMesh/TOMESH/Tomesh/TOMesh/TO Mesh...

from toronto-community-network.

Some terms we can add to a glossary or @tomeshnet/communications-and-community-engagement can use for website copy:

A supernode is an actively maintained relaying node that supports high bandwidth point-to-multipoint (PTMP) connectivity. Currently all supernodes are managed by the Network Planning, Design and Operations working group at Toronto Mesh, but other groups may also operate their own supernodes on the Toronto Community Network.

The supernode name is snXyY and where X is assigned by the Network Planning, Design and Operations working group, and yY is chosen by the node operator to identify network components within the node. For example a1 for antenna 1 and r1 for router 1.

The supernode domain is in the format nodename.operator.tcn.tomesh.net. For example sn1a1.core.tcn.tomesh.net for a device operated by the core team at Toronto Community Network.

from toronto-community-network.

Yea pls do and archive it

from toronto-community-network.

Could an abbreviation of Toronto Community Network as TCN/tcn be added? It is already in use in domain names.

from toronto-community-network.

In what instances is "tomesh" used? Code comments? Should we not just be using the standard "Toronto Mesh instead?

from toronto-community-network.

Only when in chat and comments like here, tomesh (6 char) without having to type the whole thing out

from toronto-community-network.

I almost don't want to make it an "official" short form but it's also our website domain... 🤔

from toronto-community-network.

Update this repository name to toronto-community-network (this name is confusing esp. since we have deployment repo)

Just wanted to point out that the reason we mane "mesh-deployment" was because we needed to make a private repo.
The plan was to REPLACE the deployment repo .

Is there any advantage of using "toronto-community-network" over simply "deployment"

Currently the deployment repo really does not have any valuable content.

Also

"The name of this particular initiative. It is the name we agreed on and put into all proposal material shared with collaborators."

As opposed to what initiative? How far does "this initiative" stretch?

from toronto-community-network.

Is there any advantage of using "toronto-community-network" over simply "deployment"

The project proposal involves many components that are not really related to "deployment". If the intention is to separate out things into many repos, that's a larger convo, and perhaps we should then move the deployment tickets (those tagged network) to the deployment repo. (There is a feature to do this easily.) This looks like a repo for planning the overall project, that's why it hosts tags like communications and governance, which I believe gets confusing when in a "deployment" repo. The content in the repo also is the overall plan that extends beyond network deployment.

As opposed to what initiative? How far does "this initiative" stretch?

The initiative described here https://github.com/tomeshnet/toronto-community-network/tree/master/published-documents

It excludes ipfs-live-streaming, p2p-internet-workshop, prototype, etc.

from toronto-community-network.

The rationale for renaming this repo makes sense to me but the deployment repo should probably also be removed. It has one document in it (which can be moved to the documents repo) and all the issues are pretty much made obsolete by this initiative. I am for moving that document and outright deleting or archiving the deployment repo.

EDIT: This has been done. The deployment repo is now archived.

from toronto-community-network.

Added definition of SUPERNODE to first post on this issue

Super Node naming standards added to issue #21

NOTE
NOSTNAME is snXyY
DOMAIN is operator.tcn.tomesh.net
FQDN (fully qualified domain name) would be a mix of the two - snXyY.operator.tcn.tomesh.net

from toronto-community-network.

This needs to be documented in our #54 eventually, but I'd say this task is done now since success criteria is met and I am unaware of incorrect references in any official place.

from toronto-community-network.