@@ -616,46 +616,4 @@ an absolute waiver of all civil liability in connection with the
616616Program, unless a warranty or assumption of liability accompanies a
617617copy of the Program in return for a fee.
618618
619- 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- Copyright (C) <year> <name of author>
634-
635- This program is free software: you can redistribute it and/or modify
636- it under the terms of the GNU Affero General Public License as published
637- by the Free Software Foundation, either version 3 of the License, or
638- (at your option) any later version.
639-
640- This program is distributed in the hope that it will be useful,
641- but WITHOUT ANY WARRANTY; without even the implied warranty of
642- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
643- GNU Affero General Public License for more details.
644-
645- You should have received a copy of the GNU Affero General Public License
646- along with this program. If not, see <https://www.gnu.org/licenses/>.
647-
648- Also add information on how to contact you by electronic and paper mail.
649-
650- If your software can interact with users remotely through a computer
651- network, you should also make sure that it provides a way for users to
652- get its source. For example, if your program is a web application, its
653- interface could display a "Source" link that leads users to an archive
654- of the code. There are many ways you could offer source, and different
655- solutions will be better for different programs; see section 13 for the
656- specific requirements.
657-
658- You should also get your employer (if you work as a programmer) or school,
659- if any, to sign a "copyright disclaimer" for the program, if necessary.
660- For more information on this, and how to apply and follow the GNU AGPL, see
661- <https://www.gnu.org/licenses/>.
619+ END OF TERMS AND CONDITIONS
0 commit comments