Hi,
Well, at the time we started the project the version 3 wasn't out, so I
have no idea what we "indented" to do.
For ddccontrol, it's very clear. COPYING contains GPLv2, but all sources
files clearly use the header stating GPLv2+.
For ddccontrol-db, COPYING also contains GPLv2, but we do not put any
copyright header in the files contributed by ourselves or users, so I'm
not clear if we meant GPLv2+ or just GPLv2 (or even public domain,
actually).
I'd say the conservative option is GPLv2. But I assume no one would be
offended if you put GPLv2+.
Hope this helps.
Best,
Nicolas
On 04/09/12 00:10, Jaroslav Skarvada wrote:
> Hi,
>
> FYI we are currently trying to get ddccontrol into Fedora,
> there are review requests (feel free to comment there :)
> https://bugzilla.redhat.com/show_bug.cgi?id=852893
> https://bugzilla.redhat.com/show_bug.cgi?id=852892
>
> My question is, what is the license for ddccontrol-db?
> According to https://bugzilla.redhat.com/show_bug.cgi?id=852892#c2
> the current state seems to be GPL+, but according to
> ddccontrol package itself I suspect the ddccontrol-db license
> is intended to be GPLv2+. Could you clarify?
>
> thanks & regards
>
> Jaroslav
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> ddccontrol-devel mailing list
> ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddccontrol-devel
>
|