search

18F / dashboard

DEPRECATED: A site to track our projects' status and much, much more...
Other
44 stars 25 forks source link

about.yml parse errors should cause an annotation on project page... #264

Closed ultrasaurus closed 9 years ago

ultrasaurus commented 9 years ago

about.yml parse errors should cause an annotation on project page, ideally with a link to the specific error and a link to the failing about.yml file

depends on https://github.com/18F/team-api.18f.gov/issues/122

DavidEBest commented 9 years ago

@ultrasaurus @gboone @mbland Just to be clear - the dashboard is a public-facing resource. Are we all okay with putting the errors there? Or should they be exposed to the team via another mechanism?

mbland commented 9 years ago

As a potential alternative, we could parse the "contact" field and either send an email or post an issue. That'd be a little more work, but it'd probably be a more reliable mechanism.

gbinal commented 9 years ago

FWIW - I'm okay with errors being publicly visible on the dashboard.

ultrasaurus commented 9 years ago

I'm ok with it too -- it's real! Also if we point to the about.yaml, then people can find the actual information. The yaml might be intimiditating for some folks, but if anyone really needs the info, that will be able to read it.

ultrasaurus commented 9 years ago

love that idea @mbland -- wrote it up as a separate issue: https://github.com/18F/dashboard/issues/269. Let's do this first, then add the notification!

DavidEBest commented 9 years ago

In progress here: https://github.com/18F/team-api.18f.gov/issues/122

ultrasaurus commented 9 years ago

from sprint planning @gboone thinks this is good for now. Improvements may be opened in the future as seprate stories.