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 FedRAMP (US government compliance program) #2318

Merged
merged 1 commit into from Jan 16, 2020
Merged

Add FedRAMP (US government compliance program) #2318

merged 1 commit into from Jan 16, 2020

Conversation

dacut
Copy link
Contributor

@dacut dacut commented Jan 9, 2020

  • Add fedramp.svg

  • Add FedRAMP data

Issue:

This is the logo for the US FedRAMP compliance program (fedramp.gov); that website has an Alexa rank of 192,588, but I'm actually using this for other federal agencies (e.g., nasa.gov, 1,352).

Checklist

  • I updated the JSON data in _data/simple-icons.json
  • I optimized the icon with SVGO or SVGOMG
  • The SVG viewbox is 0 0 24 24

Description

Logo was vectorized in Adobe Illustrator by tracing the PNG files from the FedRAMP logo guidelines (alas, they do not provide vectorized logos) using guides at the intersect points on pixel boundaries at 64000% zoom. (Auto vectorization was not so good.) See attached working sample.

The hex value was taken from the official FedRAMP logo guidelines PDF.

FedRAMP Vectorization

* Add fedramp.svg

* Add FedRAMP data
@PeterShaggyNoble
Copy link
Member

Thanks for your work on this one, @dacut 👍

Although, I personally prefer the version you've used and it is in an option they offer in their brand guidelines, I do think we should go with their boxed "official approved FedRAMP logo". What do the other @simple-icons/maintainers think?

@PeterShaggyNoble PeterShaggyNoble added awaiting reply Issues or pull requests awaiting reply from an individual before it may be addressed new icon Issues or pull requests for adding a new icon labels Jan 9, 2020
@dacut
Copy link
Contributor Author

dacut commented Jan 9, 2020

I have an objective reason -- and a selfish one :-) -- for choosing the unadorned version.

  • The blue square/circle does not have a flat color version in either the guidelines or the kit, but is always a gradient (!). The red version is flat, but I have never seen it used outside of the branding guidelines (and I suspect we're probably amongst the dozen folks outside the GSA who have actually read the branding guidelines :-)). My thinking here: if someone wants to use Simple Icons to reproduce this accurately, they would render the square themselves and insert the FR logo in white.
  • My selfish reason: I want to use this as a build badge via https://shields.io/ to indicate whether a package uses only FedRAMP-compliant services or not. Adding the square would make it somewhat less legible there.

But I'd be happy to redo it in the square/inverse version if that's the way folks sway.

@runxel
Copy link
Member

runxel commented Jan 9, 2020

Yeah, it's clearly stated that a unboxed version is also okay to use.
And if this is the case I'm always a big advocate on that :D

@runxel runxel removed the awaiting reply Issues or pull requests awaiting reply from an individual before it may be addressed label Jan 9, 2020
Copy link
Contributor

@ericcornelissen ericcornelissen left a comment

Choose a reason for hiding this comment

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

Since both version are explicitly allowed, I do agree that this version better fits our needs.

My thinking here: if someone wants to use Simple Icons to reproduce this accurately, they would render the square themselves and insert the FR logo in white.

I disagree with that, I think most people just get the icons they need and leave them untouched, this is especially true if you don't download them through the website but use the CDN or packages instead.

@ericcornelissen ericcornelissen merged commit 0e13f10 into simple-icons:develop Jan 16, 2020
@ericcornelissen
Copy link
Contributor

Thanks a lot for the manual vectorization @dacut, it is much appreciated! 🎉

ericcornelissen added a commit that referenced this pull request Jan 20, 2020
New icons

- Bulma (#2290)
- Bluetooth (#2293)
- Google Assistant (#2296)
- Emby (#2304)
- OpsLevel (#1890)
- ioBroker (#2302)
- Douban (#2303)
- Apache Pulsar (#2314)
- Amazon Lumberyard (#2232)
- Bandsintown (#2319)
- Discogs (#2320)
- ChartMogul (#2308)
- Just Eat (#2109)
- KeePassXC (#2273)
- Parity Substrate (#2324)
- Slackware (#2289)
- Grunt (#2321)
- Transport for Ireland (#2323)
- Quest (#2325)
- Skype for Business (#2337)
- Rhino (#2197)
- Wear OS (#2305)
- NetApp (#2327)
- Kyocera (#2328)
- Fortinet (#2329)
- Citrix (#2330)
- Apache Ant (#2342)
- protocols.io (#2344)
- Google Maps (#2196)
- The Register (#2346)
- Tide (#2307)
- Mocha (#2347)
- Citroën (#2359)
- Opel (#2361)
- Flood (#2349)
- Google Lens (#2354)
- Google Fit (#2355)
- LogMeIn (#2356)
- Das Erste (#2198)
- CD Projekt (#2292)
- HelloFresh (#2295)
- Polymer Project (#2353)
- Jenkins X (#2333)
- Material Design Icons (#2371)
- Apache Maven (#2374)
- LMMS (#2350)
- FedRAMP (#2318)
- Semantic Web (#2372)
- Claris (#2381)
- XAMPP (#2086)
- Pixabay (#2301)
- AngularJS (#2379, b95baf4)
- Aiqfome (#2400)
- Airbus (#2396)

Updated icons

- SourceForge (#2294)
- Xamarin (#2297)
- Fedora (#2300)
- Brave (#2362)
- Microsoft Edge (#2378)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new icon Issues or pull requests for adding a new icon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants