Since I've began using a computer, I've been "agreeing" to the kilometric blurbs software is bundled with way too often, without really understanding what they mean (or even trying in case of EULAs). It's true that English is not my native tongue, but why should such complicated terminology be used? Can't we express the same, common meaning with more ease?
I find this frustrating.
One day I came across the SUSHI-WARE license: while I was struck by MakeNowJust's effort, I was a bit underwhelmed by the sushi part. Don't get me wrong, I like Japanese food but my Italian DNA absolutely demands some coffee: espresso, ristretto e senza zucchero.
Thus, the Espresso license was born.
The SUSHI-WARE license is a derivative of the BEER-WARE license.
Please read the Notice section below.
Just copy the LICENSE
file into your project's root folder, fill the placeholders and push.
Following MakeNowJust's footsteps I also created this nice badge (a fascinating process indeed...) you can include in your documentation or README.md
, by copying the following:
[![Espresso License :coffee:](https://img.shields.io/badge/license-Espresso%20☕-7890F0.svg)](https://github.com/jack23247/espresso-license)
In case you ever use this license in your project, feel free to sign the guestbook!
If you have an issue or you're keen to translate this document, please feel free to open an issue or send a pull request.
This project was born as an effort to understand more about software licenses, and is not a certified OSI or FSF license. Please consider using a real, yet easy to grasp, license like MIT in your project.
If you still feel like using the Espresso license, go ahead, I'd be glad.