Skip to content

Conversation

@alexandruradovici
Copy link
Collaborator

@alexandruradovici alexandruradovici commented Apr 18, 2025

This pull request adds the initial website template for the https://arewesafetycriticalyet.org website.

Most of the text here is just placeholders, as soon as we agree on a structure, I will ask @PLeVasseur and @AlexCeleste to fill out their sections.

Logos are generated using chatgpt, I hope they don't breach an copyright.

TODOs

  • Agree on the structure
  • Fill in the details about the subcommittees
    • Coding Guidelines
    • Tooling
    • Liaison
  • Add test workflow
  • Add deploy workflow
  • Add deploy workflow for each pull request

Svg: require('@site/static/img/tooling.svg').default,
description: (
<>
Aims to define and maintain a minimal, community-approved set of tools required for certifying Rust

Choose a reason for hiding this comment

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

The mission statement (tooling/statement.md) phrases this a bit differently:

Aggregate community-vetted minimal required tooling package to be able to certify Rust in safety-critical applications.

I propose that these words are meaningfully different and would be better to use here.

We also discussed, on the call today, that we might want to say "community-identified" and possibly "suggested" rather than "required".

Copy link
Contributor

Choose a reason for hiding this comment

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

My interpretation of "community-vetted" is "community reviewed carefully".
Is that correct ? I still prefer "community-identified"
Why "minimal" ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We aim to provide at least the bare minimal required tools for certifying, no?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I modified the text, @manthonyaiello @pellico can you take a look at it?

Copy link
Contributor

Choose a reason for hiding this comment

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

It is fine ! 👍

@x0rw
Copy link

x0rw commented Apr 18, 2025

It looks great — clean and professional.

One note about the logo: modifying trademarked logos generally requires written permission from the trademark holder. However, since this project is considered an internal initiative under the Rust Foundation, it’s unclear whether those restrictions apply in the same way.
it's worth checking he Rust Foundation’s trademark policy:
https://rustfoundation.org/policy/rust-trademark-policy/#require

@MerrimanInd
Copy link
Contributor

MerrimanInd commented Apr 18, 2025

Tasks from the tooling subcommittee meeting (#282):

Logo

  • A consortium logo was drafted between the Rust Foundation and some members. @PLeVasseur to check with @JoelMarcey about whether that logo is available to be used on this website.
  • Ferrous systems made the ‘safety critical Ferrous’ logo (crab with hardhat). Is that available for broad use for all safety critical Rust? Can we use that for the subcommittee? @MerrimanInd to follow up with Ferrous.

Subcommittee Pages

  • Other subcommittee heads to add content for their respective groups
  • Change "community-approved" to "community-identified" in tooling subcommittee overview
  • Remove "required" from tooling subcommittee overview
  • @alexandruradovici to look into the technical feasibility ability to pull in markdown files from other areas of the repo without maintaining duplicating information

Answering "Are we Safety Critical Yet"

  • @MerrimanInd to draft regulation-based tables on what has been certified in Rust, what could possibly be, and what is not yet possible
  • @PLeVasseur to ask some companies that have certified Rust if they're willing to share a small testimonial or even just a press release

I think this was everything discussed in the meeting today!

Edit: I'm not necessarily listing these as blockers to merging this PR. Another point discussed in the meeting was that we should just get some website framework up and start adding content via PRs as it comes in or is needed.

@JoelMarcey
Copy link
Contributor

A consortium logo was drafted between the Rust Foundation and some members. @PLeVasseur to check with @JoelMarcey about whether that logo is available to be used on this website.

Logo use approved.

Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

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

Thanks @alexandruradovici for scaffolding this out!

As @MerrimanInd said:

Edit: I'm not necessarily listing these as blockers to merging this PR. Another point discussed in the meeting was that we should just get some website framework up and start adding content via PRs as it comes in or is needed.

Let's merge a most-minimal version of this PR. Then we can flesh it out in follow-up PRs.

@JoelMarcey
Copy link
Contributor

@alexandruradovici When would you like me to make the necessary DNS, etc. changes to get the website domain live?

@alexandruradovici
Copy link
Collaborator Author

It looks great — clean and professional.

One note about the logo: modifying trademarked logos generally requires written permission from the trademark holder. However, since this project is considered an internal initiative under the Rust Foundation, it’s unclear whether those restrictions apply in the same way. it's worth checking he Rust Foundation’s trademark policy: https://rustfoundation.org/policy/rust-trademark-policy/#require

@JoelMarcey I think this is a question that you might be able to answer.

@PLeVasseur
Copy link
Contributor

@JoelMarcey is on holiday this week I think, but my understanding was that he approved via this comment:

A consortium logo was drafted between the Rust Foundation and some members. @PLeVasseur to check with @JoelMarcey about whether that logo is available to be used on this website.

Logo use approved.

@alexandruradovici alexandruradovici merged commit 195f68f into rustfoundation:main May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants