Publishers should be maintainable

[bigfleet]

Introduce the concept of a contact person for a publisher. If the endpoint is unreachable, notify the publisher.

[bigfleet]

I am thinking about adding into the app a notion of an Outage, which might have many occurrences, a start time and an end time. Does that extend to the services/middleware layer? Maybe? The notification should happen once, and should be clearable. This is an aid for the operators on behalf of providing good service to those cities on the platform.

[masonpackard]

Regarding contact information for the publishers:

• Is the app responsible for maintaining the information for contacts?
  • How much information should the app hold, ie. email, phone, human info?
• If our app holds the contact information:
  • managed by the development team on the back end?
  • self managed by the endpoint publisher?

If the endpoint's are mainly coming from the citygram-services app, should the contact information reside and be maintaned there?

[bcipolli]

Seems to me that this should be not only managed by the endpoint publisher, but you may want to have different levels of granularity:

• Endpoint-level ('your endpoint is out')
• Notification-level ('your notification has XXX problem')

This would allow endpoints to specify contact info dynamically. Having contact info could also be a criterion for turning on service.

[bigfleet]

@bcipolli 👍 x100. So both of you have context, a service-level differentiator is important for Citygram as it establishes its future as a sustainable independent enterprise. I see this as critical to creating an offering upon which governments can rely.