In general osgeo recommends use of Creative Commons license for
documentation, in order afford writers the same "remix" culture we enjoy in
our open source projects. The alternative is of course the writing practice
of "quoting" and "citation" but does does not provide the same ability to
format
On Fri, 28 Feb 2020 at 18:34, Pierre Abbat wrote:
>
> On Friday, 28 February 2020 09:59:12 EST Mateusz Loskot wrote:
> > Unusual, very.
>
> https://www.gnu.org/licenses/gpl-faq.html#WhyNotGPLForManuals
Well, GPL, that explains why I had no idea of such an approach.
Best regards,
--
Mateusz
On Friday, 28 February 2020 09:59:12 EST Mateusz Loskot wrote:
> Unusual, very.
https://www.gnu.org/licenses/gpl-faq.html#WhyNotGPLForManuals
--
lo ponse be lo mruli ku po'o cu ga'ezga roda lo ka dinko
___
Discuss mailing list
On Fri, 28 Feb 2020, 15:36 Pierre Abbat, wrote:
> On Friday, 28 February 2020 02:40:30 EST Mateusz Loskot wrote:
> > Are you considering separate licences, one for source code
> > and one for documentation?
>
> Yes.
Unusual, very.
ML
___
Discuss
On Friday, 28 February 2020 02:40:30 EST Mateusz Loskot wrote:
> Are you considering separate licences, one for source code
> and one for documentation?
Yes. All the source code files have a note at the top, except the icons, for
which the note is in the QRC file. The documentation files don't
On Fri, 28 Feb 2020 at 03:04, Pierre Abbat wrote:
>
> PerfectTIN has two documentation files: two pages explaining how to use the
> program, and four pages describing the file format (which I just changed, so I
> have to edit the doc). There's no license note in the documentation. Which
> license
