Ben,
The companies I do Open Source compliance work for would not be inclined to
approve an Open Source review of what you suggest for use in the
company, due to ambiguity.
Licenses can, and should, clearly state when an API is meant to be a
connector to another work which can be under a differen
Here is a solution that is worth considering.
Create 2 pieces of software that are compatible. One is under a BSD
license and will accept the plugins in question. The other is under the
AGPL. Any plugin written against the BSD version is clearly not derivative
of the AGPL version and therefore
Joel Kelley wrote:
> However, a small team faced with changing business rules is all too likely
> to end up hardcoding a position or employee ID number into an approval
> plugin instead of using an environmental variable.
It's definitely an engineering problem if there is hard-coding of this sort
Josh Berkus dixit:
> to the main project, they just need to be open source somewhere, which
> can just be a matter of creating their own public GH/GL repo.
Not even that, they just need to be made available to users of
the service.
bye,
//mirabilos
--
I believe no one can invent an algorithm. O
On 8/12/22 16:46, Joel Kelley wrote:
We are interested in a plugin exception due to the reality of software
development at colleges and universities, particularly mid-sized and
smaller institutions. A few areas we've broken out into plugins are
validation, approvals, and payroll exports. Our
Dear All,
I would like to thank you all for your kind and helpful responses.
To provide some background, hopefully helpful, on the application in
question, it helps manage timesheets, faculty contracts, and student offer
letters as are commonly used in Higher Education. It is a web application
w
On Fri, Aug 12, 2022 at 2:01 PM Bradley M. Kuhn wrote:
> While the post is about additional permissions unlike the one Joel is
> pondering, the on-topic point there is that there are so many ways to draft
> these things, and so many potential pitfalls, and that is what leads me to
> first focus o
McCoy Smith wrote:
> the … site does list the Classpath Exception
> (https://spdx.org/licenses/Classpath-exception-2.0.html) and the GCC RTL
> Exception (https://spdx.org/licenses/GCC-exception-3.1.html), of which you
> say you were a "key drafter," so I'm not sure why you think that site
> should
> -Original Message-
> From: License-discuss On
> Behalf Of Bradley M. Kuhn
> Sent: Wednesday, August 10, 2022 7:54 PM
> To: license-discuss@lists.opensource.org
> Subject: Re: [License-discuss] Question about AGPLv3 with a Plugin Exception
>
> Having been a key
Kevin P. Fleming wrote:
>>> Please keep in mind that if your application incorporates or relies upon
>>> any other code (to which you do not hold the copyrights) that is also
>>> licensed under the AGPL, you cannot grant an exception (really, an
>>> 'additional permission') on your code which is co
en
707-478-8932
3001 King Ranch Rd., Ukiah, CA 95482
-Original Message-
From: License-discuss On
Behalf Of Kevin P. Fleming
Sent: Wednesday, August 10, 2022 5:12 PM
To: license-discuss@lists.opensource.org
Subject: Re: [License-discuss] Question about AGPLv3 with a Plugin Exception
Please
Please keep in mind that if your application incorporates or relies
upon any other code (to which you do not hold the copyrights) that is
also licensed under the AGPL, you cannot grant an exception (really,
an 'additional permission') on your code which is combined with it,
since you can't grant th
You might want to check out the SPDX lists of exceptions:
https://spdx.org/licenses/exceptions-index.html
> On Aug 10, 2022, at 12:35 PM, Joel Kelley wrote:
>
___
The opinions expressed in this email are those of the sender and not
necessarily those
Dear All,
The university I work for wants to open source one of our internal tools.
We would like to use the AGPLv3 since it is a web application. However, we
would like to include a plugin exception as there are places where internal
organization specific business logic rules have been separated
14 matches
Mail list logo
