Proposal: Allow REUSE compatible License Statements in License Policy

[Andreas Cord-Landwehr]

On Montag, 13. Januar 2020 20:50:30 CET Johan Ouwerkerk wrote:
> On Sun, Jan 12, 2020 at 3:19 PM Andreas Cord-Landwehr
> 
> <cordlandwehr at kde.org> wrote:
> > Moreover, I prepared a first version of a licensing howto and added it to
> > the guidelines/howto section into the community wiki (please feel free to
> > update/ extend/clarify it!):
> > - https://community.kde.org/Guidelines_and_HOWTOs/Licensing
> 
> Thanks for taking the time to writing this document. As a developer I
> found it to be clear and concise and it was quite easy to get started
> with `reuse` on Keysmith.
> 
> However, one thing I am not entirely sure about yet is translations.
> More specifically: how should various files be tagged which are
> automatically maintained by tools such as ScriptKiddy? I.e. what
> license applies to translations? Maybe the document could be extended
> to clarify the correct licensing on this point?

Hi Johan,

the licensing of automatically generated files is an interesting question. 
Actually with ScriptKiddy it becomes even more interesting, because it is not 
just ScriptKiddy but there are copyrightable translation contents that are 
inserted via ScriptKiddy.
Unfortunately, I do not have the full insight into how the licensing for 
translations is handled right now. But I think that this is a topic, we should 
cover, too, after we got the copyright statements of the source code files 
right. I will have a look into it (if not somebody else will pick it up first), 
but it might happen that it will take until an Akademy BoF until it gets into 
my focus.

Cheers,
Andreas