🧹 Move ODS repo outside Cal-ITP

[e-lo]

In order to move ODS outside of Cal-ITP, we must create a separate organizational home for it on GitHub which is managed by ODS' own governance processes.

Suggestion:

• I created https://github.com/transit-operations which could work - or open to other suggestions

To do:

• @safrazier17 identify home location
• @thekaveman transfer repository

[skyqrose]

👍 I like the idea of moving it to a separate organization. It originated from Cal-ITP, but it's supposed to be a standard not tied to any one agency.

Feedback on the name:
transit-operations has an almost-conflicting name with https://transitops.co/ , because both have pretty generic names. Maybe the name of the org should have something more specific to what it's doing in the name, like "standards" or "data". Maybe something like "operational-data-standard"? Is it okay if both the org and the main standard are named ODS? Are there other projects planned for this organization such that the name shouldn't be tied to ODS?

[thekaveman]

Maybe something like "operational-data-standard"? Is it okay if both the org and the main standard are named ODS?

I like this idea. The org could be operational-data-standard and the repo spec or similar, then we have:

https://github.com/operational-data-standard/spec as the main GitHub URL.

And the GH Pages URL would default to:

https://operational-data-standard.github.io/spec

Which isn't so bad?? (We can always redirect with a vanity URL too)

[e-lo]

Two hesitancies on operational-data-standard:

1. there is no mention of transit
2. it is very long

[thekaveman]

there is no mention of transit

Good point