Low-traffic one-way communication channel(s) for important stuff

[theoretical]

Obviously the forums are great.  But they're less than ideal for communicating important messages:

- There are a lot of subforums that fragment everything
- People tend to stop re-reading the sticky titles on every visit, so new stickies are hard to notice
- There's often good back-and-forth Q&A and discussion between community members and developers, but insightful posts tend to get buried in pages of people giving their or general chatter

We've discussed various ways of improving our communication in the past.  I'm thinking we should have three different channels aimed at different groups:

- End-user announcements:  Announcements of policy changes and mandatory upgrades.  Tell end-users and delegates about changes that will directly affect them.
- Development announcements:  Discussion of planned features, changes to the long-term road map, and development activities.  Keep community members involved in development and I3 members working remotely informed.
- Marketing blog:  Discussion of current BitShares features, project philosophy, the rationale for changes, and How To explanations.  Explain all the goodness of BitShares to casual BitShares users who might not be aware of all our features, and crypto-enthusiasts considering getting involved in the BitShares ecosystem.

End-user announcements sort of exists as a sticky at https://bitsharestalk.org/index.php?topic=7067.0 however, when we implement changes to short mechanics, users also want to know the details of the new rules.  So something like e.g. https://bitsharestalk.org/index.php?topic=9521.msg125135 (note:  illustrative purposes only, the content of this post is out of date) should be included in the announcement.

The marketing blog already basically exists at http://bitshares.org/blog/

As for development announcements, Github tickets are useful for tracking individual implementation issues but aren't as useful at providing a big picture.  For example, the Github tickets show what kinds of bugs are being worked on related to BitShares Mail, but developers who aren't privy to I3 internal discussions are likely wondering about the overall design and vision of BitShares Mail.

This is just my personal opinion and doesn't reflect any I3 consensus.