Re: [License-discuss] Coordinated release of security vulnerability information.

security fixes or bundled things with security fixes that are either clearly not or that very much depend on who is defining both "security" and "fix". -john -- John Sullivan | Executive Director, Free Software Foundation GPG Key: A462 6CBA FF37 6039 D2D7

Re: [License-discuss] Government licenses

In countries where copyright protection is available (which does not > include the U.S.), contributions made by U.S. Federal government > employees are released under the License. Merged contributions from > private contributors are released under the License. ..so far I know they have re

Re: [License-discuss] The pro se license constructor

subject line so that people who have not been able to track the discussion threads can jump in, see where things stand, and still contribute meaningfully. It doesn't help with the uncomfortable part. -john -- John Sullivan | Executive Director, Free Software Foundation GPG Key: A462 6CBA FF

Re: [License-discuss] discussion of L-R process [was Re: [License-review] Approval: Server Side Public License, Version 2 (SSPL v2)]

essed by finding more volunteer facilitators for OSI, no matter what platform is used. (I do like Discourse, and we use it at the FSF.) -john -- John Sullivan | Executive Director, Free Software Foundation GPG Key: A462 6CBA FF37 6039 D2D7 5544 97BA 9CE7 61A0 963B https://status.fsf.org/j

Re: [License-discuss] [License-review] Encouraging discussion around the technicalities of licensing

r insight as to how the license drafter expects the license to function. Could be especially useful for deciding how to read any ambiguities. The process should still consider other possible interpretations of the ambiguities, but it seems likely that the interpretations of the license author wil