Skip to content
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

Add RFC for officially adopting Ferris #2328

Closed
wants to merge 4 commits into from
Closed
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
56 changes: 56 additions & 0 deletions text/0000-epoch-mascot.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
- Feature Name: epoch_mascot
- Start Date: 2018-02-01
- RFC PR: (leave this empty)
- Rust Issue: (leave this empty)

# Summary
[summary]: #summary

Have a mascot for each epoch.

# Motivation
[motivation]: #motivation

Branding is an important thing when selling your technology to others, including the non-technical
or project managers in charge of what gets used. As things change though we also want to be able to
convey that to users who might not have picked up or used Rust since the last epoch. In this way we
can have Ferris wear a new costume every epoch, or have an epoch-specific critter mascot much like
Ubundu does. It also conveys what we mean by [what an epoch is]: Each epoch plays nicely with the
Copy link
Member

@ashleygwilliams ashleygwilliams Feb 20, 2018

Choose a reason for hiding this comment

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

spelling (s/Ubundu/Ubuntu)

previous ones despite having breaking changes. In the same way that Ferris has multiple costumes
they can all be worn, or mixed and matched, and are able to play with each other nicely. On top of
this they can act as a marker for embodying the accomplishments of the community after each epoch
begins.

# Detailed design
[design]: #detailed-design

Every epoch, the community team will look for mascot designs. These can be obtained
by paying a designer, or from submissions from the community. An idea thread may be put
up to get ideas for what the "theme" of the mascot will be.

# How We Teach This
[how-we-teach-this]: #how-we-teach-this

Unlike the more technical RFCs this is one where there would be tribal knowledge
on the matter and not one that would be documented in places like `TRPL`, or the
`Nomicon` for instance. Instead it would be taught through engagement with the
community, having events with the different mascots, as well as things
like conference T-Shirts.

# Drawbacks
[drawbacks]: #drawbacks

* Splits up the branding amongst multiple mascots rather than just one.

# Alternatives
[alternatives]: #alternatives

- We do nothing at all and continue the course as is without any mascot at all.
- We adopt different critters for each epoch, like Ubuntu

# Unresolved questions
[unresolved]: #unresolved-questions

Should we also be naming the epochs?
Copy link
Member

Choose a reason for hiding this comment

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

i believe that @rust-lang/core said they would be named by year (she says realizing she is on core). i'll sort this!

Copy link
Member

Choose a reason for hiding this comment

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

Sure but they could also have a nick name...

Copy link
Member

Choose a reason for hiding this comment

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

Precendent would be something like Android; version 2.3 is "gingerbread" and version 4.0 is "ice cream sandwich"

officially, we've only decided to name them by year, but we could do "code names". that feels like a different RFC in some sense... though i guess maybe not


[what an epoch is]: https://github.com/rust-lang/rfcs/blob/master/text/2052-epochs.md#the-basic-idea