[License-review] moving to an issue tracker [was Re: Some notes for license submitters]

[Bruce Perens]

It's nice when contributors are *willing *to change their license text as
part of the review process. That has been *one* in four of the recently
submitted ones. The others either did not have their attorneys directly
engaged with the license-review mailing list, or their attorneys were only
willing to explain the license, rather than alter it.

IMO license review is generally a policy discussion, and having a linear
flow works well. Balloon text review works well when everybody's checking
it regularly, as they were during the GPL3 review process.

    Thanks

    Bruce

On Tue, Jun 19, 2018 at 12:49 PM, Allison Randal <allison at opensource.org>
wrote:

> One thing I've seen work well for
> this kind of process is to have an "review" directory and an "approved"
> directory, so that licenses in draft can go through multiple revisions
> with clear diffs between each revision, and then the final PR to
> "approve" the license just changes the directory.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20180619/c7cb1d09/attachment.html>