Skip to content

[RFC] blog.rust-embedded.org #191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 26, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 58 additions & 0 deletions rfcs/0000-blog.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
- Feature Name: blog
- Start Date: 2018-08-22
- RFC PR: (leave this empty)
- Rust Issue: (leave this empty)

# Summary
[summary]: #summary

Host a blog at blog.rust-embedded.org and use it for our newsletters and
announcements.

# Motivation
[motivation]: #motivation

So far we have been posting our newsletters and announcements to
https://users.rust-lang.org but it would be nice to have them on a place that's
*ours* and that would be a blog.

An advantage to having a blog is that it would be easier for readers to browse
through our newsletters and announcements. Right now, they get lost in the
stream in of new content posted to the users forum. Also, with a blog we can
provide RSS which is something our readers have requested before.

# Detailed design
[design]: #detailed-design

We'll create a new repository named `blog` that the resources team will be in
charge of developing and maintaining.

The content for the blog will be authored as markdown files, and the blog will
be hosted as a static web site on https://blog.rust-embedded.org . The blog
posts will *not* have a comments section. The exact mechanism by which the
markdown files will be converted into a static site will be decided by the
resources team.

The WG newsletters and announcements will be posted on this blog. The resources
team will be in charge of reviewing all the new content before its published.

Finally, the newsletters directory in this repository will be moved into
the blog repository.

# Drawbacks
[drawbacks]: #drawbacks

- Readers would lose the ability to comment on newsletters and announcements.
Copy link
Member

@ithinuel ithinuel Aug 24, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to have a disqus as the comment section in the articles ?
I rather use a forum post/reddit

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are trying to avoid having to host anything ourselves for now; I don't know if that'd be the case for disqus. My preference would be to use the users forum as mentioned in the next line of the RFC.

But, if we wish to, we can post a link to blog posts on reddit or the users
forum and use that space to receive comments.

# Alternatives
[alternatives]: #alternatives

- Continue posting our newsletters and announcements to
https://users.rust-lang.org.

# Unresolved questions
[unresolved]: #unresolved-questions

None