> 
> What license is Repoforge?  I couldn't find one, but that probably
> means it beneath my nose :)

I've taken one patch and according to a Repoforge admin in #repoforge,
it's fine:

> 12:25 < plaxx> under what license are the repoforge specs and patches?
> 12:25 <@zaytsev> plaxx: most public domain, some gpl
> 12:26 < plaxx> I've taken a patch from the asciidoc package (which was 
> probably adapted from a fedora one) and integrated it 
>                into an updated asciidoc SPEC that is meant for Fedora.
> 12:27 < plaxx> so I guess this is ok with both licenses?
> 12:29 <@zaytsev> plaxx: yes, i believe so. these patches techincally contain 
> asciidoc source, so they can't be released 
>                  under anything but gpl
> 12:30 < plaxx> ok, super! thanks for clarifying
> 12:31 <@zaytsev> plaxx: honestly, no one ever raised concern with regards to 
> specs themselves and hence there is no general 
>                  consesus or any official statements with regards to which 
> licenses they are covered by and whether they are 
>                  licensable at all. dag used to say though, that specs the he 
> authors he considers to be public domain, so 
>                  do i.
> 12:32 <@zaytsev> plaxx: patches are a bit different in that when you make a 
> patch, in forcibly contains source code from the 
>                  original application. it is arguable whether it can be 
> considered a derivative work, but i can imagine so, 
>                  and therefore for gpl licensed softwre, i would assume that 
> released patches are also under gpl
> 12:33 <@zaytsev> plaxx: otherwise most patches are just one-liners to fix 
> build system hicckups, so makes no sense to use 
>                  anything but public domain

We went on a little bit and, of course, he told me he is not a lawyer.
Due to size of the said "borrowed work" and the positive reaction of
someone embodying that community, I think it'll be an acceptable
contribution for Fedora.

I contacted the maintainer. He gave me two other things to do:

- vim plugin should be separately [sub]packaged
- build the git doc with it and it shall still be pretty

I'll get to tasks, eventually, and let you guys know.

Cheers!
-- 
Olivier Bilodeau
[email protected]  ::  +1.514.447.4918 *115  ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to