| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Peter Cock <p(dot)j(dot)a(dot)cock(at)googlemail(dot)com>, Filipus Klutiero <chealer(at)gmail(dot)com> |
| Cc: | spi-general(at)lists(dot)spi-inc(dot)org |
| Subject: | Re: Issue #5 - Please explain the topic of each mailing list |
| Date: | 2016-10-10 17:08:45 |
| Message-ID: | dac884b8-05ec-168f-297f-c787122698a1@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox |
| Thread: | |
| Lists: | spi-general |
On 10/10/2016 01:57 AM, Peter Cock wrote:
>>> Anything that is confidential. For example, a potential legal issue.
>>
>> Why would a potential legal issue be confidential?
>
> I would have thought legal issues should be private by default.
> e.g. Project X has noticed company Y appears to be using their
> software in breach of license and wants advice and legal assistance.
> Going public with allegations might be good strategy, but personally
> I would want to discuss this situation with lawyers privately first.
>
> As an example of a legal issue which could be public, I asked
> on behalf of Biopython (part of the Open Bioinformatics Foundation
> umbrella) about *getting* legal advice on changing our open source
> licence. SPI referred us to the Software Freedom Law Center (SFLC).
Right so there are many types of legal issues. The one you bring up is
fine to be public. However there are others that are not.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-10-10 18:10:55 | Re: Resolution The Open MPI Project as an associated project |
| Previous Message | Peter Cock | 2016-10-10 08:57:54 | Re: Issue #5 - Please explain the topic of each mailing list |