Transit Software Cooperative Funding #15
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
gtfs.zone/hatchery#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Transit agencies all do almost the same thing, yet they seem to all build different software for no particular reason.
Make a place where people and agencies can propose transit software, with a fairly detailed specification, and different agencies can bid on how much they would pay for the building of it. Sort of like Kickstarter, they might get some control of the software, depending on the policy. The important thing is that multiple agencies could pool money to build the same software.
This would require careful planning from a legal perspective to make sure that the developers are paid, etc. Somehow, you would have to verify that the software was built to the required specification to be paid.
Potentially a minimal version of this would be best, simply connecting developers with a group of agencies who are all interested in building the same software.
This allows multiple agencies to share software, likely encouraging open sourcing it, or at least making the software not agency specific.