Skip to content

Commit b7752a1

Browse files
author
Igor Milhit
committed
license: removes documentation part of the license
* Adds affiliation mention of authors. Co-Authored-by: Igor Milhit <[email protected]>
1 parent b446370 commit b7752a1

File tree

2 files changed

+16
-60
lines changed

2 files changed

+16
-60
lines changed

AUTHORS.rst

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -17,19 +17,19 @@
1717
Credits
1818
=======
1919

20-
* Aly Badr
21-
* Sébastien Délèze
22-
* Mana Deweerdt
23-
* Olivier Dossmann
24-
* Laurent Dubois
25-
* Benoit Erken
26-
* Nicolas Labat
27-
* Johnny Mariéthoz
28-
* Renaud Michotte
29-
* Igor Milhit
30-
* Miguel Moreira
31-
* Gianni Pante
32-
* Nicolas Prongué
33-
* Peter Weber
34-
* Alicia Zangger
35-
* Bertrand Zuchuat
20+
* Aly Badr [RERO]
21+
* Sébastien Délèze [RERO]
22+
* Mana Deweerdt [UCLouvain]
23+
* Olivier Dossmann [RERO]
24+
* Laurent Dubois [UCLouvain]
25+
* Benoit Erken [UCLouvain]
26+
* Nicolas Labat [RERO]
27+
* Johnny Mariéthoz [RERO]
28+
* Renaud Michotte [UCLouvain]
29+
* Igor Milhit [RERO]
30+
* Miguel Moreira [RERO]
31+
* Gianni Pante [RERO]
32+
* Nicolas Prongué [RERO]
33+
* Peter Weber [RERO]
34+
* Alicia Zangger [RERO]
35+
* Bertrand Zuchuat [RERO]

LICENSE

Lines changed: 0 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -617,47 +617,3 @@ Program, unless a warranty or assumption of liability accompanies a
617617
copy of the Program in return for a fee.
618618

619619
END OF TERMS AND CONDITIONS
620-
621-
How to Apply These Terms to Your New Programs
622-
623-
If you develop a new program, and you want it to be of the greatest
624-
possible use to the public, the best way to achieve this is to make it
625-
free software which everyone can redistribute and change under these terms.
626-
627-
To do so, attach the following notices to the program. It is safest
628-
to attach them to the start of each source file to most effectively
629-
state the exclusion of warranty; and each file should have at least
630-
the "copyright" line and a pointer to where the full notice is found.
631-
632-
<one line to give the program's name and a brief idea of what it does.>
633-
634-
Copyright (C) {{ year }} {{ organization }}
635-
636-
This program is free software: you can redistribute it and/or modify
637-
it under the terms of the GNU Affero General Public License as published by
638-
the Free Software Foundation, version 3 of the License.
639-
(at your option) any later version.
640-
641-
This program is distributed in the hope that it will be useful,
642-
but WITHOUT ANY WARRANTY; without even the implied warranty of
643-
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
644-
GNU Affero General Public License for more details.
645-
646-
You should have received a copy of the GNU Affero General Public License
647-
along with this program. If not, see <http://www.gnu.org/licenses/>.
648-
649-
Also add information on how to contact you by electronic and paper mail.
650-
651-
If your software can interact with users remotely through a computer
652-
network, you should also make sure that it provides a way for users to
653-
get its source. For example, if your program is a web application, its
654-
interface could display a "Source" link that leads users to an archive
655-
of the code. There are many ways you could offer source, and different
656-
solutions will be better for different programs; see section 13 for the
657-
specific requirements.
658-
659-
You should also get your employer (if you work as a programmer) or school,
660-
if any, to sign a "copyright disclaimer" for the program, if necessary.
661-
For more information on this, and how to apply and follow the GNU AGPL, see
662-
<http://www.gnu.org/licenses/>.
663-

0 commit comments

Comments
 (0)