-
Notifications
You must be signed in to change notification settings - Fork 101
[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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thank you, @japaric!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello! I’m @sekineh from irr2018 team.
I think it’s generally OK, but every blog post must be announced somewhere.
I suppose we use the channels like:
- User forum
- RSS
- This week in Rust (Important!)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
# Drawbacks | ||
[drawbacks]: #drawbacks | ||
|
||
- Readers would lose the ability to comment on newsletters and announcements. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
This seems to now have 10 approvals. I will wait to merge, to see if anyone has any last minute objections. I have created https://github.com/rust-embedded/blog, currently with no content. My first plan would be to move all of the |
There don't seem to be any outstanding comments (sorry for only waiting an hour), so I will go ahead and merge. bors r+ |
👎 Rejected by label |
Trying again after removing label bors r+ |
191: [RFC] blog.rust-embedded.org r=jamesmunns a=japaric This a proposal to create and maintain our own blog. [Rendered version of this proposal](https://github.com/rust-embedded/wg/blob/blog/rfcs/0000-blog.md) This proposal (PR) needs at least 10 votes (approvals) from @rust-embedded/all to be accepted. After the proposal has been accepted we'll proceed to implement it. @rust-embedded/all please vote on this proposal using [pull request reviews]. Or if you have a concern leave a comment. [pull request reviews]: https://help.github.com/articles/about-pull-request-reviews/ cc #148 Co-authored-by: Jorge Aparicio <[email protected]>
Build succeeded |
This was merged, but the RFC document is still |
It should have the same number as the PR number that merged it. That would be: 0191-*.md |
This a proposal to create and maintain our own blog.
Rendered version of this proposal
This proposal (PR) needs at least 10 votes (approvals) from @rust-embedded/all
to be accepted. After the proposal has been accepted we'll proceed to implement
it.
@rust-embedded/all please vote on this proposal using pull request reviews.
Or if you have a concern leave a comment.
cc #148