On Thu, Jan 09, 2020 at 10:48:48AM +0100, Piotr Drąg wrote:
> czw., 9 sty 2020, 10:26 użytkownik Jean-Baptiste Holcroft <
> jean-baptiste@holcroft.fr> napisał:
>
> > Dear translators,
> >
> > ABRT dev want to have a different license for translation than the one
> > used for the software.
> >
> > Their software is GLP 2.0 or after.
> > They would like to have some kind of "Public Domain" License for
> > translation.
> >
> > I never had this situation before and don't know if this is acceptable
> > or not.
> >
> > According to https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing
> > It means: "Being in the public domain is not a license; rather, it means
> > the material is not copyrighted and no license is needed."
> >
> > What do you think?
> >
>
>
> It's absolutely unacceptable. I'm quite baffled, to be honest. What is
> their reasoning for this?
Why should it be unacceptable ?
I get some people find it distasteful to not have a formal license
text for "Public Domain", but none the less "Public Domain" is an
accepted licensing approach for software in most distros including
Fedora.
The very permissive licenses such as BSD are effectively giving users
the same usage rights as "public domain", but with a formal license
text behind them. So if people are uncomfortable with "public domain"
translations, then just using 2-clause BSD would achieve the same
end result for ABRT in practice IMHO.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
_______________________________________________
trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org
No comments:
Post a Comment