-
Hey, apologies for posting this on your issues page, but I couldn't find any other info on how to get in contact with you.
It's really cool to see this repo and the effort you put into it! I especi…
-
### DESCRIPTION
Since it is GPLv3, will you put it into the F-Droid store?
### STEPS
https://f-droid.org/en/docs/Submitting_to_F-Droid_Quick_Start_Guide/
### EXPECTED
Yes or no :)
-
Debrief has some fairly inconsistent license headers, mostly not present.
These should be made more consistent.
We've selected GPLv3.
The license will be structured like this:
```
/*
* Debr…
-
```
This is derived from code which was originally GPLv3, not BSD.
```
Original issue reported on code.google.com by `jimatj...@gmail.com` on 25 Jan 2010 at 9:00
-
```
This is derived from code which was originally GPLv3, not BSD.
```
Original issue reported on code.google.com by `jimatj...@gmail.com` on 25 Jan 2010 at 9:00
-
You should add a LICENSE file to let everyone know how they can use your project!
For example, can I assume I can fork it, edit it and release it under GPLv3?
-
the LGPL v3 is only compatible with (L)GPLv3'd code, whereas LGPL 2.1 + (+ == and later) is compatible with almost any open source license.
please consider relicensing as LGPLv2.1+
-
You should [choose a license](https://choosealicense.com/) for your code and put a copy of the license file in your repo. [Seems like](http://seankross.com/2016/08/02/How-R-Packages-are-Licensed.html…
-
The REAMDE.md currently says that this project is licensed under GNU GPL.
Is this GPLv2 or GPLv3?
I've created a fork of this project that updates bind instead of resolvconf, and I want to make sure…
-
This is a great set of educational material, thank you for creating this repository!
Can the maintainer please add a LICENSE to this repository such as the GNU GPLv3 or later? Thanks!
avamk updated
4 years ago