[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: openSUSE packagers' take on the 3 month release cycle
From:       Vishesh Handa <me () vhanda ! in>
Date:       2013-07-09 12:46:46
Message-ID: CAOPTMKB4Mk7afnK1ghyXV_xpiyzGJ2FJkeANwp7H8CFJ2H1Aeg () mail ! gmail ! com
[Download RAW message or body]

On Tue, Jul 9, 2013 at 5:58 PM, Scott Kitterman <kde@kitterman.com> wrote:
> There I'd a licensecheck script that does this. It helps, but the results=
 have to be checked and properly documented and so thete is still substanti=
al manual work required. KDE packages are generally better about consistent=
ly documenting copyright and licensing, but we still find bugs and it's sti=
ll a lot of work.

Can we as KDE developers do something to reduce this work load? We
could create git hooks which reject patches with incompatible
licesnses? Or something like that?

Once the script has extracted the infromation, do you really need to
check it? Proper documentation can be automatically generated. (Unless
I'm missing something)

My overall point is that this problem seems more of a technical one
than one related to release schedules. It should be fixed as it would
considerably reduce the work distributions have to do.

--
Vishesh Handa
[prev in list] [next in list] [prev in thread] [next in thread]