Skip to content

Latest commit

 

History

History
33 lines (23 loc) · 3.89 KB

CONTRIBUTING.md

File metadata and controls

33 lines (23 loc) · 3.89 KB
Raw

Contributor License Agreement

We'd love to accept your patches and contributions to this project. There is just one thing you need to do first...

Contributions to Google projects, even unofficial ones like this, must be accompanied by a Contributor License Agreement. This is not a copyright assignment, it simply gives Google permission to use and redistribute your contributions as part of the project.

https://cla.developers.google.com

You generally only need to submit the Google CLA once, so if you've already submitted one for a different project, you probably don't need to do it again.

After your contribution is included, you will be listed in CONTRIBUTORS and/or AUTHORS files; CONTRIBUTORS is the official list of people who can contribute (and typically have contributed) code to this repository, while the AUTHORS file lists the copyright holders.

New Font Family Requirements

If you would like to include a new font family in the Google Fonts collection we'll be very happy to include it, if it also meets the following criteria:

  • The typeface design is original, or a legitimate revival of a design in the public domain, and of good quality. The Google Design team curates the overall Google Fonts collection and decides if fonts are of good quality. You can get general reviews of your project from the wider international type community during development by posting review requests in the googlefonts-discuss group, and the typedrawers review forum.
  • The project is licensed under the SIL Open Font License v1.1, with no Reserved Font Name (why)
  • The font family name does not include any company names or initials, and no registered trademarks; it should be a simple and unique name.
  • The project is developed on Github or similar, with complete corresponding sources, open to public participation, and actively maintained. Complete corresponding sources means that the fonts are available in your preferred form of modification, the files you actually use to develop the project, along with all the build instructions or scripts needed to reproduce the process of turning those source files into your released font binaries.
  • All font files are available in TTF format, with hinting (such as with ttfautohint)
  • All font files have at a minimum the 215 glyphs listed in our [latin_unique-glyphs.nam](https://github.com/google/fonts/blob/master/tools/encodings/latin_unique-glyphs.nam) file
  • All font files within the family have the same Unicode character set (unencoded glyphs can differ)
  • A README.md file is included in the root of the source repository, and inside of that file we can read about FONTLOG information, and your github usernames, so that we can prepare a description (example) and link your name to your profile.
  • More detailed design and production details are listed in github.com/googlefonts/gf-docs/ProjectChecklist.md

When your project meets these criteria, please file an issue with a link to the source repository. (In the future we hope to provide guidance on making pull requests directly, but since we carefully check the technical aspects of the fonts, it's better to work with us on your upstream project.)

Google Fonts may provide financial or design assistance for some type projects. If you would like to discuss this, please mention that you would like someone to contact you privately when filing an issue.