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

[Karan, Cem F CIV USARMY RDECOM ARL (US)]

+1 here too.  Except that I want one project per license; that way the issue tracker is for that particular license, and not for all licenses in general.  Maybe one extra project that covers writing licenses in general?  That way we can point people to issues that come up over and over again (IIRC, you can reference any issue anywhere on GitHub, not just the issues in your own project).

Thanks,
Cem Karan

________________________________
From: License-review [license-review-bounces at lists.opensource.org] on behalf of Brendan Hickey [brendan.m.hickey at gmail.com]
Sent: Tuesday, June 19, 2018 1:50 PM
To: License submissions for OSI review
Subject: [Non-DoD Source] Re: [License-review] moving to an issue tracker [was Re: Some notes for license submitters]

All active links contained in this email were disabled. Please verify the identity of the sender, and confirm the authenticity of all links contained within the message prior to copying and pasting the address to a Web browser.

________________________________


+1, nothing to add but my emphatic agreement.

On Tue, Jun 19, 2018, 1:48 PM Josh berkus <josh at postgresql.org < Caution-mailto:josh at postgresql.org > > wrote:
On 06/19/2018 10:29 AM, Luis Villa wrote:
> On Tue, Jun 19, 2018 at 7:57 AM Josh berkus <josh at postgresql.org < Caution-mailto:josh at postgresql.org >
>     For my part, I think even moving to a bugzilla instance would be an
>     improvement over the current workflow, but apparently I don't have
>     consensus on that.
>
>
> Any particular reason not to move to GitLab? Seems like an issue tracker
> there (maybe a new project per license, maybe not?) might be pretty easy
> to set up and get running.
>
> (Or, frankly, GitHub, since OSI has already bitten the bullet and hosted
> projects there.)

WFM.  Just an issue tracker, really.

Something that allows per-line comments would be delightful, actually,
so GitLab/GitHub would be great.

We'd only need one project, but we'd put the list of licenses in
directories and license submitters can send in PRs.  This will then
permit us to do a "code review" of the licenses.

--Josh


_______________________________________________
License-review mailing list
License-review at lists.opensource.org < Caution-mailto:License-review at lists.opensource.org >
Caution-http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org < Caution-http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20180619/39840d89/attachment-0001.html>