Add keyword generics initiative announcement post to the internals blog

[yoshuawuyts]

This adds the announcement of the keyword generics initiative to the rust internals blog. I've set the release date for Monday the 25th of July, and marked the blog post as release: false in case it gets merged before then.

Thanks!

cc/ @rust-lang/initiative-keyword-generics

[Mark-Simulacrum]

The release keyword is a marker for Rust releases, used to produce https://blog.rust-lang.org/releases.json (I believe currently feeding the version number on https://www.rust-lang.org/, but I'm not sure).

So it won't help with accidental merging :)

[Mark-Simulacrum]

It also looks like this post is in posts/, not posts/inside-rust/, which is presumably an oversight? It sounds like you intended to put this on Inside Rust.

[yoshuawuyts]

Updated with all feedback! - Also changed to date to tomorrow (Tuesday) to publish as it's getting quite late today.

[oli-obk]

You need to mark it as release: false, that flag is about whether the post is a rust version release, not whether to publish the post.

I can press the merge button, I don't know if I'm allowed to XD who makes the final decision on blog posts?

[yoshuawuyts]

You need to mark it as release: false, that flag is about whether the post is a rust version release, not whether to publish the post.

I don't believe such a flag is needed for the inside Rust blog? Here's the front matter from a previous post, which matches most other posts too:

---
layout: post
title: Rust Compiler June 2022 Steering Cycle
author: Felix Klock
description: "The compiler team's June 2022 steering cycle"
team: The Compiler Team <https://www.rust-lang.org/governance/teams/compiler>
---

I can press the merge button, I don't know if I'm allowed to XD who makes the final decision on blog posts?

My understanding from talking about this with the lang team is that any Rust team can publish to the inside rust blog, as long as it's relevant to the Rust project and we follow proper review etiquette - like we've done. I believe this is the reason why when you're added to a Rust initiative, you get commit access on the blog as well. Ideally this would all be documented in a CONTRIBUTING.md file on the repo, but there is none currently.