Skip to content

Sharqiewicz/GNU-GENERAL-PUBLIC-LICENSE

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

45 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Understand what this license means

The whole idea is that we can mash-up each other's work by giving original credits.

First, let's Seth Godin explain what it is. Taken from Seth's podcast Akimbo, episode "All rights reserved." This worths 1m40 of your time. https://pascalandy.com/blog/what-is-the-gnu-gpl-license/

Second, here is Plain English explanation by the GNU's creator Richard Stallman.

2019-01-07_20h53

https://youtu.be/iBVgcjhYV2A?t=17m11s (between 17m11 to 19m24)

Why forking this license?

I wanted a clean Markdown version of the license.

No matter how I trust the open-source community, I feel it’s not best practice to:

  • Use a link that points to a licence written by a third party
  • Use licence(s) proposed by GitHub

If any changes happen, how do you know it's still right for you? By using scenario #1 or #2, you could put yourself in a position where you may lose control of what the licence was supposed to mean at the moment you read it.

I believe everyone should fork the licence they want to use on their git repo.

 

Brought to you by

FirePress

FirePress.org | play-with-ghost | GitHub | Twitter

If you are looking for an alternative to WordPress, Ghost might be the CMS you are looking for. Check out our hosting plans.

ghost-v2-review

Why, Contributing, License

Expand content (click here).

Why all this work?

Our mission is to empower freelancers and small organizations to build an outstanding mobile-first website.

Because we believe your website should speak up in your name, we consider our mission completed once your site has become your impresario.

Find me on Twitter @askpascalandy.

The FirePress Team 🔥📰

Contributing

The power of communities pull request and forks means that 1 + 1 = 3. You can help to make this repo a better one! Here is how:

  1. Fork it
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request

Check this post for more details: Contributing to our Github project. Also, by contributing you agree to the Contributor Code of Conduct on GitHub.

License

Copyright (C) 2019 — Pascal Andy

Project: https://github.com/pascalandy/GNU-GENERAL-PUBLIC-LICENSE

Find the GNU General Public License V3 at: https://github.com/pascalandy/GNU-GENERAL-PUBLIC-LICENSE/blob/master/LICENSE.md

Basically, you have to credit my work AND keep it open source. by Pascal Andy | https://pascalandy.com/blog/now/

About

GNU General Public License (version 3), 29 June 2007

Resources

License

Unknown, Unknown licenses found

Licenses found

Unknown
LICENSE
Unknown
LICENSE.md

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Shell 97.5%
  • Dockerfile 2.5%