package naming convention

MobilityData / gtfs-validator

Canonical GTFS Validator project for schedule (static) files.

https://gtfs-validator.mobilitydata.org/

Apache License 2.0

288 stars 101 forks source link

package naming convention #46

Closed ghost closed 3 years ago

ghost commented 4 years ago

Is your feature request related to a problem? Please describe. @barbeau

Describe the solution you'd like @barbeau

Additional context https://github.com/MobilityData/gtfs-validator/pull/44#discussion_r386514156

barbeau commented 4 years ago

From discussion in https://github.com/MobilityData/gtfs-validator/pull/44#discussion_r387705551:

In the gtfs-realtime-bindings project, we decided to use the following namespace:

io.mobilitydata.transit

Note the io instead of org - that was a deliberate decision based on the MobilityData IO branding. The transit was mainly to be consistent with the prior google maven group ID of com.google.transit.

So, if we want to be consistent, we should change the org to io.

barbeau commented 3 years ago

Closing as outdated