Process: How GTFS extensions are added to the main spec

100 views

Skip to first unread message

Joe Hughes

unread,

Feb 20, 2008, 4:13:46 PM2/20/08

to Google Transit Feed Spec Changes

Hi all,

I just wanted to go over the process for extending the GTFS format as
it stands now:

1) Someone posts a proposal to this group. Either the poster or I
edit the "Open Proposals" summary page with a link to the new
proposal:
http://groups.google.com/group/gtfs-changes/web/open-proposals

2) Members comment on the proposal, and if it's compelling, people
create test implementations.

3) Once the proposal has been tried end-to-end with real data and a
client app that uses the new information (could be Google Maps or an
independent application like TimeTablePublisher), and it seems to work
well, I post a notice that it's ready for inclusion in the discussion
and the proposals page.

4) The proposed changes are added to the format spec document.

The goal of this process is to ensure that the spec is extended in
ways that are useful, and that anyone who's interested can follow the
progress of development. (Anyone can read this group on the Google
Groups website or via a read-only email subscription, though only
existing users of the spec are allowed to post.)

Let me know if you have additional questions or comments. I expect
that this process will change over time, as the number of spec
stakeholders expands.