Add new optional fields for Text-to-Speech functionality in Service Alerts feed

[ibi-group-team]

This is a proposal to add two new optional fields for text-to-speech functionality to the ServiceAlerts feed, called tts_header_text and tts_description_text of type TranslatedString.

See discussion here: #132

Announced on the GTFS-realtime Google Groups here: https://groups.google.com/forum/#!topic/gtfs-realtime/aI7OfMycsHw

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[ibi-group-team]

i signed it!

…

--- Ritesh Warade Director, IBI Group 617.699.9544

________________________________ From: googlebot <notifications@github.com> Sent: Thursday, January 10, 2019 5:47:34 PM To: google/transit Cc: TransitRealtime; Author Subject: Re: [google/transit] Add new optional field for Text-to-Speech functionality in Service Alerts feed: tts_ivr (#135) Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

________________________________ What to do if you already signed the CLA Individual signers * It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>. Corporate signers * Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot<http://go/cla#troubleshoot> (Public version<https://opensource.google.com/docs/cla/#troubleshoot>). * The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data<https://cla.developers.google.com/clas> and verify that your email is set on your git commits<https://help.github.com/articles/setting-your-email-in-git/>. * The email used to register you as an authorized contributor must also be attached to your GitHub account<https://github.com/settings/emails>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#135 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ARwac-M1MZnfywg2IaHwCSVUyuof1wmSks5vB8MGgaJpZM4Z6d7z>.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[farah-machlab-ibigroup]

I'm a commit author and I'm ok with my commits being contributed to this project.

[LeoFrachet]

I agree with the fields, their names and their definitions.

Two small suggestions:

1. Add the space missing in second definition: //Text => // Text
2. Maybe something (an example or a guideline) could be added to describe what they'll contain. For information in my tts_stop_name proposal (Add fields for text-to-speech #49), I was offering this kind of definition for text-to-speech field, to help the reader understand what would be the difference of content:

• Text-to-speech field - The field should contain the same information than its parent field (on which it falls back if it is empty). It is aimed to be read as text-to-speech, therefore, abbreviation should be either removed ("St" should be either read as "Street" or "Saint"; "Elizabeth I" should be "Elizabeth the first") or kept to be read as it ("JFK Airport" is said abbreviated).

[ibi-group-team]

This pull request has been open for more than one week, so we are calling for a vote.

Voting will be closed on Tuesday January 29 at 23:59:59 UTC.

[abyrd]

+1

[LeoFrachet]

+1

Pinging:

• MBTA: Dave (@DaveBarker) or Paul (@paulswartz)
• Transit app: Guillaume (@gcamp) or Juan (@juanborre)
• TriMet: Frank (@fpurcell) or Mike (@mgilligan)

[gcamp]

(That was a +1)

[paulswartz]

+0. We don't have a problem with this field, but aren't likely to incorporate it into how we use Text-to-speech for alerts.

[barbeau]

@ibi-group-team One point of clarity - I believe this vote is for adopting the tts fields as "experimental", right? In that case you'll need to mark it as experimental (for an example, see OccupancyStatus - https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/reference.md#enum-occupancystatus)

I'm +1 for adopting as experimental field.

[ibi-group-team]

Voting for this proposal is closed and the results are:
Yes: 4
No: 0

So the proposal passes! We'll get this merged.

Thank you all!

[ibi-group-team]

@google-admin @googlebot the CLA check is currently failing so this cannot be merged. @farah-machlab-ibigroup's contributions are covered under the corporate CLA for IBI Group. Can you please confirm and update the check?

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

[barbeau]

Thanks @ibi-group-team and all for coming to a consensus on this!