Document rules

[tfausak]

I have a bunch of unwritten rules for Haskell Weekly. I've written about some of them incidentally:

• Job section #57 (comment)
• Include link to discussion #55 (comment)
• Figure out a way to feature old content #51 (comment)
• https://www.reddit.com/r/haskell/comments/5m6p05/issue_36_haskell_weekly/dc1k9kx/?context=3

It would be nice to codify these (and other) rules in something like CONTRIBUTING.markdown.

[tfausak]

Summarizing those links:

• Don't link to job postings. They are one of the potential ways to monetize Haskell Weekly. Until I get that figured out I don't want to give them away for free, per se.

• Don't link to discussions about posts on Reddit or Hacker News or whatever. People that are interested in that know where to find it. Also its not clear which site to link to anyway.

• Stick to posting news. At the end of the year, post a recap of the most popular content of that year.

• Link to primary sources. Link to Reddit (or Hacker News or whatever) if it's a self post or the discussion is interesting on its own.

[tfausak]

In addition to documenting all my "rules", I should document all the services used to make Haskell Weekly happen. The ones I can think of right now are:

• Name.com for domain name registration.
• Cloudflare for DNS and HTTPS.
• GitHub (duh) for repository hosting.
• Travis CI for tests and static file generation.
• GitHub Pages for static file hosting.
• Google Analytics for site analytics.
• MailChimp for email stuff, including managing subscribers, sending emails, and analytics.

[tfausak]

Oh, also:

• Feedly for keeping up with Atom/RSS feeds.
• Twitter for announcing new issues and generally interacting with the community.

And I sometimes use my personal Reddit, Hacker News, and Lobsters accounts to post new issues.

[tfausak]

More rules: https://www.reddit.com/r/haskell/comments/6emu1w/issue_57_haskell_weekly/dibm01j/?context=2

• Try to surface content that hasn't been featured in other places. (Don't choose worse stuff just because it's obscure though.)
• Maybe start linking to GHC tickets and proposals, but only if they're broadly understandable.

[tfausak]

More ramblings here: https://www.reddit.com/r/haskell/comments/6g13wr/issue_58_haskell_weekly/dio6y39/

• Avoid linking to PDFs because they aren't HTML.
• Avoid linking to videos because they're not text.
• Don't count on the community to interact.

[tfausak]

The stuff listed in this issue is good enough for now.