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

[Luis Villa]

On Tue, Jun 19, 2018 at 2:38 PM Karan, Cem F CIV USARMY RDECOM ARL (US) <
cem.f.karan.civ at mail.mil> wrote:

> +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.
>

Yeah, that's why I suggested per-license projects - makes it pretty easy to
understand the state of one license. The flip side is that it makes it
harder to understand the meta "what licenses is OSI looking at right now".
My understanding is that neither GitLab nor GitHub do good multi-level
issue tracking so it's possible we just have to hack up a solution (e.g.,
list active things by hand in a wiki somewhere).

re stet/taiga, there was also an AGPL discussion tool (forked from?
inspired by?) stet that we used for MPL. But the company that was trying to
turn that into a SaaS business folded.

Frankly, OSI's core competence right now is not hosting software (nor
should it be!) so IMNSHO a hosted, third-party service is a better option -
perfect enemy of the good, etc. I also think it's a good idea for OSI to
prefer open source tools, hence my initial GitLab suggestion, but reminder
that the GitHub ship has already sailed: https://github.com/OpenSourceOrg

Luis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20180619/08a71567/attachment.html>