For Developers‎ > ‎

Status Update Email Best Practices

  • Send to list with +status, e.g.
  • Minimize boilerplate subject line.
    • Do not include the date, that is already in email headers.
  • Summarize highlights in subject, or as first line of email.
    • This improves skim-ability of threads.
  • One line description of the project with feature linked.
    • is already established and maintained for many other needs and includes:
      • Longer project description
      • Specification link
      • Launch bug
      • Owners
      • Implementation Status.
  • Main content follows as a bulleted list of key status updates.
  • Every 2 weeks works well for many projects. Adjust as appropriate given the news of an update.
  • Optimize for skimmability.



Subject: Bluetooth Status - Experiment targeting M51, Opera demoed at MWC.

Web Bluetooth provides Bluetooth GATT Access to web apps.