> * Copyright law may categorically exclude the work. This is often the
> case if the work was produced by the USA government, but not always.
Kind of unrelated, but I just thought that I should point out that this is only
the case for Americans. The USA government claims copyright on their doc
lumin writes:
> (please CC me if reply, thanks)
Done.
> I'm maintaining a package and encountered some copyright issues,
> I believe here is the right place to ask for help :-)
Yes, this is the place to ask about legal (such as copyright) issues
with packages that may prevent them getting into
On Thu, 26 Feb 2015 06:37:20 +
lumin wrote:
> On Thu, 2015-02-26 at 17:27 +1100, Riley Baird wrote:
> >
> > If you're cherry-picking, I'd say that it would probably be fine.
> > Copying full pages, probably not. If you tell us what package it is, it
> > might give us a better idea.
>
> I'm
On Thu, 2015-02-26 at 17:27 +1100, Riley Baird wrote:
>
> If you're cherry-picking, I'd say that it would probably be fine.
> Copying full pages, probably not. If you tell us what package it is, it might
> give us a better idea.
I'm maintaining fortune-zh, Chinese Data files for fortune,
which
> There are many quotes/paragraphs from famous people on wikiquote.org,
> and I'd like to cherry-pick some of those content
> (they are distributed under CC-BY SA 3.0)
> into the package I am maintaining.
>
> At first I thought ignoring the license issue is ok,
> as the content I chose is *definite
Hi debian-legal,
(please CC me if reply, thanks)
I'm maintaining a package and encountered some copyright issues,
I believe here is the right place to ask for help :-)
There are many quotes/paragraphs from famous people on wikiquote.org,
and I'd like to cherry-pick some of those content
(they ar
Simon pointed out the key question: if it is a derivative work or just
an aggregation of two works (code + logo, or logo + text). I don't think
it would be considered a derivative but IANAL.
Also note that even if the executable was a derivative work of the logo
(and thus subject to the CC-BY-SA
On Wed, 25 Feb 2015, Simon McVittie wrote:
> > "share alike" (thus copyleft) licensing of the entire project, i.e. it
> > would not be available for close-source derivatives?
> The important question is, is the code or documentation legally a
> derivative work of the logo, or have they just been
On 25/02/15 15:55, Yaroslav Halchenko wrote:
> Now at least we agreed that logo could be released under CC BY SA
> (share-alike) license but I wondered: if I have a software project
> which is under more permissive license (MIT or BSD-3) and then includes
> that logo a) in the code b) in the doc
Dear IANALs,
I am in a dialog about a license for a logo I once envisioned and then
some proper designed helped to design but because naive me didn't
disclose upfront the terms of the logo release -- got problematic.
Now at least we agreed that logo could be released under CC BY SA
(share-alike)
10 matches
Mail list logo
