Skip to content
Browse files
Improve and rename license (#200)
* Improve and rename license

* Remove unnecessary license files

* Fix license badge
  • Loading branch information
josepjaume authored and oriolgual committed Nov 11, 2016
1 parent 55c5bd2 commit 545725c3a39092dc3f1460cd39be7a02eefc9102
Showing with 43 additions and 2,477 deletions.
  1. +42 −0 LICENSE.txt → LICENSE-AGPLv3.txt
  2. +1 −1
  3. +0 −619 decidim-admin/LICENSE.txt
  4. +0 −619 decidim-api/LICENSE.txt
  5. +0 −619 decidim-core/LICENSE.txt
  6. +0 −619 decidim-system/LICENSE.txt
@@ -617,3 +617,45 @@ Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.


How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published
by the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <>.

Also add information on how to contact you by electronic and paper mail.

If your software can interact with users remotely through a computer
network, you should also make sure that it provides a way for users to
get its source. For example, if your program is a web application, its
interface could display a "Source" link that leads users to an archive
of the code. There are many ways you could offer source, and different
solutions will be better for different programs; see section 13 for the
specific requirements.

You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU AGPL, see
@@ -1,4 +1,4 @@
# Decidim [![Gem](]( [![Gem](]( [![License: AGPL v3](](
# Decidim [![Gem](]( [![Gem](]( [![License: AGPL v3](](

### Code quality
[![Build Status](](

0 comments on commit 545725c

Please sign in to comment.