Reminder: if you are interested in this committee, the application
closes in 6 days.
On 6/26/23 15:25, Josh Berkus wrote:
Fellow licensing enthusiasts:
As some of you know, OSI currently has a legal intern reviewing all of
our data on approved licenses on our website and elsewhere. In some
On Mon, Jun 26, 2023 at 4:26 PM Thorsten Glaser wrote:
> I question that the OSI uses such a proprietary thing anyway.
>
I understand it, it's a known issue and technical debt we carry.
This topic pops up often and I repeat the answer here: OSI has a very
limited budget, we can't afford to hire
Kevin P. Fleming dixit:
>> https://forms.gle/DVNrLk7A5hX1YAfG6
>
>It appears that this form needs to have its permissions opened up to
>allow people who are not members of the OSI group in Google Workspace
>to see it :-)
I question that the OSI uses such a proprietary thing anyway.
This is appall
On Mon, Jun 26, 2023, at 19:16, Josh Berkus wrote:
> On 6/26/23 16:07, Kevin P. Fleming wrote:
>> It appears that this form needs to have its permissions opened up to allow
>> people who are not members of the OSI group in Google Workspace to see it :-)
>
> Thank you! Fixed, I think.
Confirmed.
On 6/26/23 16:07, Kevin P. Fleming wrote:
It appears that this form needs to have its permissions opened up to allow
people who are not members of the OSI group in Google Workspace to see it :-)
Thank you! Fixed, I think.
--
Josh Berkus
___
The o
On Mon, Jun 26, 2023, at 18:25, Josh Berkus wrote:
> As such, the OSI Board is forming a committee, the License Consistency
> Working Group[1], to evaluate and recommend how inconsistent licenses,
> if any, be treated. If you are interested in contributing to this
> effort, please fill out this
Fellow licensing enthusiasts:
As some of you know, OSI currently has a legal intern reviewing all of
our data on approved licenses on our website and elsewhere. In some
cases, this might result in the discovery of licenses whose pedigree or
approval status isn't entirely clear, or are inconsi
