Browse Source

fix readme and license

pull/8/head
Swrup 4 months ago
parent
commit
18d2b56e07
  1. 45
      LICENSE.md
  2. 7
      README.md

45
LICENSE.md

@ -613,48 +613,3 @@ an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
### 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
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
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 <https://www.gnu.org/licenses/>.
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 <https://www.gnu.org/licenses/>.

7
README.md

@ -7,7 +7,7 @@ Permap's aim is to help people find friends with similar interests around them
and build local communities.
You can make threads with geographical coordinate,
this way you can find people near you doing interesting stuffs,
this way you can find people near you doing interesting things,
socialize with them and share local knowledge.
## Permap's future
@ -21,3 +21,8 @@ Instead of making threads with a simple (latitude * longitude) data,
we want to be able to make threads on any OpenStreetMap's item/ActivityPub object
that can resolve to a geographical position.
# License
[AGPL-or-later]
[AGPL-or-later]: ./LICENSE.md

Loading…
Cancel
Save