<p dir="ltr">Great, wonderful </p>
<div data-smartmail="gmail_signature">itelRS24</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, May 13, 2025, 12:40 PM <<a href="mailto:license-discuss-request@lists.opensource.org">license-discuss-request@lists.opensource.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send License-discuss mailing list submissions to<br>
<a href="mailto:license-discuss@lists.opensource.org" target="_blank" rel="noreferrer">license-discuss@lists.opensource.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:license-discuss-request@lists.opensource.org" target="_blank" rel="noreferrer">license-discuss-request@lists.opensource.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:license-discuss-owner@lists.opensource.org" target="_blank" rel="noreferrer">license-discuss-owner@lists.opensource.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of License-discuss digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Submission of PFSSL v1.0 for OSI Review and Approval<br>
(<a href="mailto:rafael@senties-martinelli.com" target="_blank" rel="noreferrer">rafael@senties-martinelli.com</a>)<br>
2. Re: Submission of PFSSL v1.0 for OSI Review and Approval<br>
(Kevin P. Fleming)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 12 May 2025 17:18:11 +0000 (UTC)<br>
From: <a href="mailto:rafael@senties-martinelli.com" target="_blank" rel="noreferrer">rafael@senties-martinelli.com</a><br>
To: license-discuss <<a href="mailto:license-discuss@lists.opensource.org" target="_blank" rel="noreferrer">license-discuss@lists.opensource.org</a>><br>
Subject: [License-discuss] Submission of PFSSL v1.0 for OSI Review and<br>
Approval<br>
Message-ID:<br>
<<a href="mailto:170982128.104196173.1747070291446.JavaMail.zimbra@senties-martinelli.com" target="_blank" rel="noreferrer">170982128.104196173.1747070291446.JavaMail.zimbra@senties-martinelli.com</a>><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
<br>
Hello, <br>
<br>
I am writing to submit a new free/open source software license for review and approval: The Privative-Friendly Source-Shared License (PFSSL) v1.0 <br>
<br>
This license aims to offer a middle ground between permissive licenses (such as MIT or BSD) and stronger copyleft licenses (such as LGPL or AGPL). It ensures compatibility with proprietary software (i.e., it is non-infective), while requiring source code availability, proper attribution, and consideration of network-based software usage. <br>
<br>
Key details: - License name and version: PFSSL v1.0 - Author: Myself (Rafael Senties Martinelli) - Compliance: The license complies with the Open Source Definition, including criteria such as OSD 3, 5, 6, and 9 - Adoption: No projects are currently using the license; however, I am preparing to release some of my own software under it - License text: Provided as an attachment and available in HTML format - SPDX submission: Not yet submitted; I understand OSI approval should come first I welcome your feedback and am available to clarify any details regarding the license or its intended use. Thank you for your time and consideration, Rafael Senties Martinelli <br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20250512/da16cc03/attachment-0001.htm" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20250512/da16cc03/attachment-0001.htm</a>><br>
-------------- next part --------------<br>
Privative-Friendly Source-Shared License (PFSSL) v1.0<br>
<br>
Version 1, Revision 0, published on 25 April, 2025.<br>
<br>
Copyright (c) 2025 Rafael Senties Martinelli. All rights reserved.<br>
<br>
This license may be copied and shared freely, but its text must not be modified.<br>
See Clause 14 (Integrity of License Text) for more details.<br>
<br>
Introduction<br>
<br>
This license is designed to allow usage and integration with other software<br>
(including proprietary), while ensuring that the source code covered by this<br>
license is made available to users. It also emphasizes clear attribution and<br>
responsible reuse.<br>
<br>
Definitions<br>
<br>
- "Software" refers to the collection of files distributed under this license,<br>
including source code, header files, scripts, configuration files,<br>
documentation, artwork, and any other material included in the project.<br>
- "Source code" means the preferred form of the software for making<br>
modifications, including build instructions, configuration files, and any<br>
supporting materials required to compile, install, or run the software.<br>
- "Corresponding Source Code" for the Software means the Source Code of the<br>
Software, including all scripts, configuration files, and other materials as<br>
found in the Software's source distribution that are needed to compile,<br>
install, and run the Software. It specifically excludes the source code of<br>
libraries, tools, or other components that are external dependencies of the<br>
Software and are typically obtained separately.<br>
- "You" refers to any individual or entity using, modifying, or distributing<br>
the software under the terms of this license.<br>
<br>
How to Use the License<br>
<br>
To apply the Privative-Friendly Source-Shared License (PFSSL) v1.0 to a file or<br>
project, you should include the full license in your project, and a notice like<br>
the following at the top of each source file:<br>
<br>
This file is part of [Project Name].<br>
<br>
Copyright (c) [Year] [Your Name or Organization]<br>
<br>
Licensed under the Privative-Friendly Source-Shared License (PFSSL) v1.0.<br>
You may use, modify, and distribute this file under the terms of that license.<br>
<br>
This software is provided "as is", without warranty of any kind.<br>
The authors are not liable for any damages arising from its use.<br>
<br>
See the LICENSE file located at [License location] of this project for details.<br>
<br>
<br>
Summary of Terms<br>
<br>
1. Disclaimer of Warranty<br>
2. Limitation of Liability<br>
3. License Grant<br>
4. Linking<br>
5. Use of Header Files<br>
6. Contributions<br>
7. Modification Notice Requirement<br>
8. Naming, Attribution, and Authorship<br>
9. Trademarks<br>
10. Source Code Availability<br>
11. Patent Grant and Termination<br>
12. Termination<br>
13. Severability<br>
14. Integrity of License Text<br>
<br>
1. Disclaimer of Warranty<br>
<br>
This software is provided "as is" and without warranty of any kind, express or<br>
implied, including but not limited to the warranties of merchantability, fitness<br>
for a particular purpose, and noninfringement.<br>
<br>
2. Limitation of Liability<br>
<br>
In no event shall the authors or copyright holders be liable for any claim,<br>
damages, or other liability, whether in an action of contract, tort, or<br>
otherwise, arising from, out of, or in connection with the software or the use<br>
or other dealings in the software.<br>
<br>
3. License Grant<br>
<br>
You are hereby granted, free of charge, a non-exclusive, worldwide,<br>
royalty-free license to use, copy, modify, distribute, and sublicense this<br>
software, subject to the following conditions.<br>
<br>
4. Linking<br>
<br>
You may compile, link, and use this software with any software (open-source or<br>
proprietary). If you distribute a binary or executable that links to this<br>
software, you are not required to release the source code of your own<br>
application.<br>
<br>
Note that while linking is generally permitted, the distribution of the<br>
Software, including when statically linked or used to provide network services,<br>
triggers source code disclosure obligations under Clause 10.<br>
<br>
5. Use of Header Files<br>
<br>
You are permitted to import and reference the header files provided by this<br>
software in proprietary or closed-source software, solely for the purpose of<br>
compiling and linking against this software. This includes the use of type<br>
declarations, function signatures, macros, and constants.<br>
<br>
However, this permission does not extend to the incorporation of code from<br>
header files that implements significant logic or core functionality of the<br>
Software. The inclusion of such code from header files into proprietary software<br>
is not permitted under this clause, as the primary purpose of this clause is to<br>
facilitate compilation and linking, not to allow the embedding of the<br>
Software's operational core into a work not covered by this license. Trivial<br>
inline definitions (such as simple data accessors or basic type manipulation)<br>
are permitted.<br>
<br>
This clause is intended to prevent circumvention of the source code availability<br>
obligations under Clause 10.<br>
<br>
6. Contributions<br>
<br>
By submitting a contribution to this software, you agree to license your<br>
contribution under the terms of the Privative-Friendly Source-Shared License<br>
(PFSSL) v1.0. You must have the legal right to submit the contribution and to<br>
license it under these terms.<br>
<br>
If your contribution incorporates code from other open-source projects, such<br>
incorporated code must be under terms compatible with this License. Terms are<br>
considered compatible if they do not impose obligations on the combined work<br>
that conflict with the terms of this License or are more restrictive than the<br>
obligations of this License, and if their requirements (such as attribution and<br>
license inclusion) can be fulfilled while complying with this License. When<br>
distributing the Software that includes such incorporated code, you must also<br>
include a copy of the original license(s) covering that code.<br>
<br>
7. Modification Notice Requirement<br>
<br>
If you modify this software in any way, you must include the year and the name<br>
of the author of the modifications within each modified file. For clarity,<br>
"name of the author" in this context includes their legal name, a commonly used<br>
pseudonym, or a username that they use consistently for contributions to the Software.<br>
<br>
8. Naming, Attribution, and Authorship<br>
<br>
If you distribute the Software:<br>
<br>
- Unmodified: You may retain the original name and identifiers.<br>
- Modified: You must take reasonable steps to effectively differentiate your<br>
version from the original Software and to clearly indicate that it is a<br>
modified version, thereby avoiding any suggestion that your version is the<br>
original or endorsed by the original authors.<br>
<br>
Methods for achieving this differentiation include changing the name of the<br>
software and any public-facing identifiers (e.g., logos, binary names,<br>
documentation titles). If your modifications are minor (such as bug fixes or<br>
compatibility patches), providing a clear and prominent notice with the<br>
software stating that it is a modified derivative and not the original, or<br>
using versioning suffixes that indicate the modification, may be sufficient to<br>
satisfy this requirement. However, if your modifications are significant or<br>
could otherwise lead to confusion with the original Software, a change of the<br>
primary name and identifiers is required to avoid suggesting your version is the<br>
original, unless explicitly granted permission by the upstream authors.<br>
<br>
In all cases, you must preserve all existing copyright notices and author<br>
attributions. You may only add new authors to reflect your contributions.<br>
<br>
You may not use the name of the original authors or contributors to endorse or<br>
promote products derived from this software without prior written permission.<br>
<br>
Notwithstanding the above, the original authors retain the right to request that<br>
any distributor or user of a modified version cease using the original name and<br>
logo of the Software. Upon receiving such a request, the distributor or user<br>
must cease all use of the original name and logo within a reasonable timeframe.<br>
<br>
Suggestions for Attributions and Modification Tracking<br>
<br>
One suggested format for including detailed attribution and tracking<br>
contributions within individual source files is as follows:<br>
<br>
This file is part of [Project Name].<br>
<br>
Copyright (c) [200X-20XX] [Creator Name or Organization]<br>
Copyright (c) [20YY-20YY] [Maintainer 1, Maintainer 2]<br>
<br>
Licensed under the Privative-Friendly Source-Shared License (PFSSL) v1.0.<br>
You may use, modify, and distribute this file under the terms of that license.<br>
<br>
This software is provided "as is", without warranty of any kind.<br>
The authors are not liable for any damages arising from its use.<br>
<br>
See the LICENSE file located at [License location] of this project for details.<br>
<br>
Contributions to this file by year:<br>
20XY: Person 1, Person 7, Person 9<br>
20XX: Person 1, Person 2, Person 3<br>
<br>
This format clearly distinguishes between the main authors or maintainers of the<br>
file and contributions made by others over time. By listing contributions<br>
concisely, typically by year and name, the format helps keep the file header<br>
manageable even in projects with a large number of contributors, without becoming<br>
overly verbose. When making modifications, you should update the relevant<br>
attribution information in the file header, such as copyright years or adding<br>
your name to the list of contributors for the current year, in accordance with<br>
Clause 6.<br>
<br>
9. Trademarks<br>
<br>
This License does not grant you any rights to use any trademarks, service marks,<br>
or logos associated with the Software. Any use of such marks must comply with<br>
applicable trademark law and be subject to separate permission from the owner of<br>
the marks.<br>
<br>
10. Source Code Availability<br>
<br>
The terms for making source code available depend on whether the Software has<br>
been modified. For the purposes of this clause, "Origin" refers to the primary<br>
source or location where the Software was obtained under this License (e.g., a<br>
specific URL, a package repository, or a defined distribution channel).<br>
<br>
If you Distribute the Software, or use the Software to provide services over a<br>
network (such as web applications, SaaS platforms, or APIs), you must adhere to<br>
the following conditions:<br>
<br>
Note on Package Manager Distribution: If the Software is distributed as a<br>
package manager dependency, and the metadata of that package clearly specifies<br>
the Origin from which the Corresponding Source Code can be obtained, this method<br>
of distribution is generally considered to fulfill the requirement of specifying<br>
the Origin under this section (a).<br>
<br>
a) If the Software has NOT been Modified:<br>
<br>
You are not required to provide the Corresponding Source Code with the<br>
distribution or network service. Instead, you must clearly specify the Origin<br>
from which the recipient or user can obtain the Corresponding Source Code of the<br>
unmodified Software.<br>
<br>
a.1) Fallback Source Availability:<br>
<br>
If the specified Origin for the unmodified Software subsequently becomes<br>
unavailable or no longer provides the Corresponding Source Code, and if the<br>
method by which the Origin was specified did not guarantee that recipients<br>
automatically received the Corresponding Source Code with their copy of the<br>
Software, then you must then make the full Corresponding Source Code of the<br>
unmodified Software available to recipients of any future distributions or users<br>
of any future network interactions of the work that includes the Software, and<br>
also to any party who previously received the work (or interacted with the<br>
service) and requests the source code after the original Origin is no longer<br>
available.<br>
<br>
b) If the Software has been Modified:<br>
<br>
You must make the full Corresponding Source Code of the Modified Software<br>
available to the recipient or users interacting with the service. The<br>
Corresponding Source Code must be complete and in a form that can be compiled<br>
and used to recreate and run the Modified Software, assuming a standard<br>
development environment with commonly available system libraries and external<br>
dependencies. The build instructions included in the Corresponding Source Code<br>
should clearly identify any necessary external dependencies and how they can be<br>
obtained, but the source code for these external dependencies does not need to<br>
be included. The method of making the Corresponding Source Code available should<br>
be reasonable and not impose undue burdens on the recipient (e.g., providing a<br>
download link or including it with the distribution).<br>
<br>
c) Failure to Comply with Source Availability:<br>
<br>
If you are required to provide the Corresponding Source Code under section a.1)<br>
(Fallback Source Availability for unmodified Software) or section b) (If the<br>
Software has been Modified), and you fail to provide that source code as<br>
required by the relevant section, you must cease all further distribution and<br>
use of the Software (as part of the larger work or service) until you are able<br>
to comply with that section's requirements.<br>
<br>
11. Patent Grant and Termination<br>
<br>
Subject to the terms and conditions of this license, the upstream authors hereby<br>
grant you a non-exclusive, worldwide, royalty-free patent license, to make,<br>
use, sell, offer for sale, import, and otherwise run, modify, and distribute<br>
this software, solely to the extent that such activity would otherwise infringe<br>
a patent owned or controlled by the upstream authors, that is necessarily<br>
infringed by the use or distribution of this software as permitted by this<br>
license.<br>
<br>
If you initiate patent litigation (including a cross-claim or counterclaim in a<br>
lawsuit) alleging that this software or a contribution incorporated within it<br>
infringes a patent, then your rights under this license shall terminate<br>
immediately.<br>
<br>
12. Termination<br>
<br>
Your rights under this License will terminate automatically if you fail to<br>
comply with any term of this License.<br>
<br>
If your breach of this License is curable, your rights will be reinstated if you<br>
cure the breach within 30 days of becoming aware of the breach.<br>
<br>
However, if your breach is a deliberate and significant violation of your<br>
obligations, your rights under this License will terminate immediately and<br>
permanently.<br>
<br>
Provisions which, by their nature, should survive termination of this License<br>
shall survive termination, including but not limited to Clauses 1 (Disclaimer<br>
of Warranty), 11 (Patent Grant and Termination - for past litigation), and this<br>
Clause 12.<br>
<br>
13. Severability<br>
<br>
If any provision of this License is held to be invalid, illegal, or<br>
unenforceable in any respect, that invalidity, illegality, or unenforceability<br>
shall not affect the validity, legality, or enforceability of the remaining<br>
provisions, and the license shall be construed as if the invalid, illegal, or<br>
unenforceable provision had never been contained herein.<br>
<br>
14. Integrity of License Text<br>
<br>
You may distribute this license along with the software, but you may not alter<br>
or remove the license text itself.<br>
<br>
Any copy of the software must be accompanied by the complete text of this<br>
license, included in a form that is readily accessible to the recipient and<br>
which preserves the original content and terms of the license without<br>
alteration. This permits including the license text within documentation files,<br>
software packages, or other standard distribution formats, provided the full<br>
text is present and its substance is not changed.<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 13 May 2025 07:39:00 -0400<br>
From: "Kevin P. Fleming" <<a href="mailto:lists.osi-license-discuss@kevin.km6g.us" target="_blank" rel="noreferrer">lists.osi-license-discuss@kevin.km6g.us</a>><br>
To: <a href="mailto:license-discuss@lists.opensource.org" target="_blank" rel="noreferrer">license-discuss@lists.opensource.org</a><br>
Subject: Re: [License-discuss] Submission of PFSSL v1.0 for OSI Review<br>
and Approval<br>
Message-ID: <<a href="mailto:3bcc469a-ed1c-4971-9072-d6e75aa9e7d1@app.fastmail.com" target="_blank" rel="noreferrer">3bcc469a-ed1c-4971-9072-d6e75aa9e7d1@app.fastmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Mon, May 12, 2025, at 13:18, <a href="mailto:rafael@senties-martinelli.com" target="_blank" rel="noreferrer">rafael@senties-martinelli.com</a> wrote:<br>
> <br>
> Hello,<br>
> <br>
> I am writing to submit a new free/open source software license for review and approval: The Privative-Friendly Source-Shared License (PFSSL) v1.0<br>
<br>
Please take a few moments to review the "License review process" page at <a href="https://opensource.org/licenses/review-process" rel="noreferrer noreferrer" target="_blank">https://opensource.org/licenses/review-process</a>.<br>
<br>
In particular the submission needs to be sent to the license-view list if your goal is to seek approval and not just generate discussion, and you'll need to provide more information:<br>
<br>
**In addition to the information required for a legacy license**, the license submitter must:<br>
<br>
\u2022 Describe what gap not filled by currently existing licenses that the new license will fill.<br>
\u2022 Compare it to and contrast it with the most similar OSI-approved license(s).<br>
\u2022 Describe any legal review the license has been through, including whether it was drafted by a lawyer.<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20250513/f6b08455/attachment.htm" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20250513/f6b08455/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
License-discuss mailing list<br>
<a href="mailto:License-discuss@lists.opensource.org" target="_blank" rel="noreferrer">License-discuss@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org" rel="noreferrer noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of License-discuss Digest, Vol 146, Issue 1<br>
***********************************************<br>
</blockquote></div>