Merge #187

187: [RFC] Embedded Rust Showcase r=japaric a=adamgreig

Follow-up from #147 and today's IRC meeting.

[Rendered](https://github.com/rust-embedded/wg/blob/embedded-rust-showcase/rfcs/0000-embedded-rust-showcase.md)

cc @rust-embedded/resources 

Co-authored-by: Adam Greig <[email protected]>
Co-authored-by: Adam Greig <[email protected]>

Author: bors[bot]

rfcs/0000-embedded-rust-showcase.md

@@ -0,0 +1,107 @@
+# Summary
+[summary]: #summary
+
+This RFC proposes establishing a new repository for a web page advertising
+noteworthy embedded Rust projects. This new resource would go beyond the
+existing [awesome-embedded-rust] list by allowing long form
+descriptions, photographs, and videos to best demonstrate the projects.
+
+[awesome-embedded-rust]: https://github.com/rust-embedded/awesome-embedded-rust
+
+# Motivation
+[motivation]: #motivation
+
+We would like a well-presented list of interesting embedded projects using Rust
+to advertise Rust's abilities in this domain. Existing lists are mainly
+targeted at embedded Rust developers looking for libraries; this list would
+instead be advertising the final projects people have accomplished with Rust,
+and so should appeal to potential users who are not already embedded Rust
+developers.
+
+The main embedded Rust website will contain a shortlist of especially notable
+projects, but is aimed at presenting a very high-level overview to all users
+including non-technical users. This proposed list would be able to present more
+projects in more detail, and will require that their source code is publicly
+available so embedded developers interested in Rust can inspect it.
+
+# Detailed design
+[design]: #detailed-design
+
+## New Repository
+
+We create a new repository, `showcase` (TBC), in the
+rust-embedded organisation and under the existing Resources team. It will use
+the same underlying technology as the upcoming embedded Rust website to render
+Markdown to a web page.
+
+## New Web Page
+
+The new web page would live at https://showcase.rust-embedded.org (TBC).
+
+Each project is listed with a photograph/GIF/video, description, and other
+details (see Submission section).
+
+Additionally, each project has a badge indicating whether it builds on stable
+Rust or requires a nightly compiler.
+
+## Project Requirements
+
+To be considered for inclusion, projects must:
+
+* Involve embedded Rust, in other words, use Rust and run on embedded hardware
+
+* Have publicly available source code
+
+The objective of this list is to showcase Rust code in action; we can't do this
+if people can't read the code! There might be space on the main Embedded Rust
+website to showcase projects known to use Rust but without public code. We
+don't require any specific license; just that it's available for interested
+users to read.
+
+* Have working CI builds
+
+Since we want people to be able to learn from the code, we require it at least
+builds successfully. Working CI also shows what versions of Rust it builds on,
+which is useful to establish if a project works on stable Rust.
+
+* Have build instructions
+
+These might be as simple as `cargo build` or might document any specific
+Rust versions, build oddities, or other steps required to produce the
+final firmware. Projects could also document their physical build, for example
+whether a particular development board was used, or what custom hardware is
+present, but this is not required.
+
+* Have at least one photograph/video/GIF of the project in action
+
+## Project Submission
+
+Projects are submitted by their authors via pull requests. Submissions must
+contain the following information:
+
+* Project name
+* Author name
+* Project website/repository
+* Project description
+* Images, GIFs, or video of the project
+* Whether or not the project builds on stable Rust
+
+After a project is submitted, the resources team will review the PR, possibly
+consulting the other teams when relevant. Approval can then be granted by any
+of the resources team members.
+
+# Alternatives
+
+* Instead of badges for builds-on-stable projects, the nightly-only projects
+  could be binned together at the bottom of the page.
+* The web page could instead be maintained as part of the main embedded-rust
+  website, existing as a page in that website.
+* We could extend awesome-embedded-rust to permit longer descriptions of
+  projects.
+* We could integrate this concept into the existing awesome-embedded-rust
+  repository, but still render the projects to a web page.
+
+# Unresolved Questions
+[unresolved]: #unresolved
+
+* Final name for repository/web page