• Try to get community to Dockerize their stuff
  • Invite people to fill in the wiki space
  • Get community to answer questions about their tech

Types of Contact

  • Server -> Client
    • Announcements
      • Beta
      • New services / versions
      • New api / ui / versions
    • Notifications
      • System maintenance
      • Outages
  • Client -> Server
    • Support
      • Troubleshooting
      • Usage Questions
      • Reporting bugs
    • Feedback
      • I don’t like your colors
      • general comments
      • etc

Server → Client

Announcements (how will we announce the beta)

  • Announce at the meeting, then communicate with full consortium
  • Who gets approved and when?
    • Need to get input from TAC and steering committee

___________________

  • social media?
    • Twitter / Trello / etc
    • Google Group?
  • send an e-mail?
    • sent to:
      • preview / soft launch (TAC / stakeholders)
      • then full beta (NDSC members)
    • instructions:
      • what is the beta?
      • what does this mean?
      • how to get access
        • sign-up
        • get approved or declined
        • approved people get access
        • idea: staggered approval to more closely monitor scale
      • who gets approved?
        • all TAC / steering committee members
        • active NDSC participants / tutorials
        • Mike feels like this should be inclusive
        • Craig feels like this should be exclusive
        • Before doing any work towards this, we need to discuss with Kenton and Kandace
      • how do we create accounts?

Notifications (how do we notify beta users of changes, system outages, etc)

  • social media
    • Twitter / Trello / etc
  • query for all e-mails and cc them in bulk?
    • beta users mailing list?
    • google group
  • build in some notification functionality? (WebSockets?)

Client → Server

Support

  • “Contact Us” <— totally necessary
    • e-mail alias (NDS-52?)
    • gitter
    • google group
    • social media
      • Twitter / Trello / etc
    • use a real ticketing system to track issues?
      • can we leverage JIRA for this?

Feedback

  • General comments
  • Wishes
  • Suggestions
  • No labels