<div dir="ltr"><div dir="ltr">Hi Duman-san,<br><br>This license looks like a GPLv3/AGPLv3 family variant, with an even stronger focus on network operation and on preventing practical barriers to accessing corresponding source.<br>Two points stood out to me:<br><br>1. Potential tension with OSD #10<br><br>OSD #10 says: "No provision of the license may be predicated on any individual technology or style of interface."<br>Section 5 requires that "public availability" be provided "through a network server" and "without requiring registration, payment, or acceptance of terms" (inconsistent with the license). Section 7 similarly states that access to Corresponding Resource and Installation Information "must not require any special password, key, registration, or authorization."<br><br>Is mandating a "network server" and banning "registration" an OSD #10 issue (interface/technology assumptions), or is it better read as a permissible anti-restriction rule to keep rights practically exercisable?<br><br>2. Repeated "publicly available" requirements, plus equal access and no-delay mandates.<br><br>Section 3 triggers a "publicly available" obligation for Corresponding Resource when the work is operated to provide functionality to third parties over a network. Section 14 requires "equivalent access" for all recipients "without discrimination, delay, or additional restriction," and Section 16 treats staged releases or selective disclosure for "commercial or strategic advantage" as a violation.<br><br>I understand the policy goal, but this goes beyond what OSD explicitly requires and may strongly constrain distribution and business workflows. I am curious how others see the tradeoff here.<br></div><br><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">2026/1/21 21:09 M.samet Duman via License-review <<a href="mailto:license-review@lists.opensource.org">license-review@lists.opensource.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>Hello license-review list,</div><div><br></div><div>I am submitting the Project Tick General Public License, Version 1.0,</div><div>for review and approval as an OSI-approved Open Source license.</div><div><br></div><div>License name:</div><div>Project Tick General Public License</div><div><br></div><div>Version:</div><div>Version 1.0 (17 January 2026)</div><div><br></div><div>License text:</div><div><p>[ATTACHMENT: PT-GPL-<span>1.0</span>.txt \u2014 plain text]</p></div><div></div></div><div><div></div><div><br></div><div>License steward:</div><div>Project Tick (<a href="https://projecttick.org/" target="_blank">https://projecttick.org/</a>)</div><div>Contact: <a href="mailto:dumanmehmetsamet@icloud.com" target="_blank">dumanmehmetsamet@icloud.com</a></div><div><br></div><div>Submitter:</div><div>Mehmet Samet Duman, on behalf of the license steward</div><div><br></div><div>Statement of compliance:</div><div>I affirm that the Project Tick General Public License complies with the</div><div>Open Source Definition, including OSD Sections 3, 5, 6, and 9.</div><div><br></div><div>License category:</div><div>New license</div><div><br></div><div>Purpose and gap addressed:</div><div>This license is intended to address gaps not fully covered by existing</div><div>OSI approved copyleft licenses, particularly regarding:</div><div>- Mandatory source availability for network-based operation of software</div><div>- Prevention of discriminatory or selective access to corresponding source</div><div>- Ensuring practical, timely, and non-obstructive access to source code</div><div><br></div><div>Comparison to existing licenses:</div><div>The license is most similar in spirit to the GNU GPL v3 and the AGPL v3,</div><div>but differs materially in that it:</div><div>- Treats public network operation as triggering source availability obligations</div><div> without introducing separate licensing layers</div><div>- Explicitly prohibits selective, delayed, or discriminatory access to source</div><div>- Clarifies compliance expectations in SaaS and hosted environments</div><div><br></div><div>Legal review:</div><div>This license was authored by the license steward without formal legal counsel.</div><div>However, it has been iteratively reviewed for internal consistency and</div><div>alignment with the Open Source Definition.</div><div><br></div><div>Existing usage:</div><div>The license is newly published and currently used by Project Tick projects.</div><div><br></div><div>Thank you for your time and review. I am available to answer questions</div><div>and participate actively in the review process.</div><div><br></div><div>Best regards,</div><div>Mehmet Samet Duman</div></div>_______________________________________________<br>
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an <a href="http://opensource.org" rel="noreferrer" target="_blank">opensource.org</a> email address.<br>
<br>
License-review mailing list<br>
<a href="mailto:License-review@lists.opensource.org" target="_blank">License-review@lists.opensource.org</a><br>
<a href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" rel="noreferrer" target="_blank">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a><br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Shuji Sado</div><div>Chairman, Open Source Group Japan<br><a href="https://opensource.jp/" target="_blank">https://opensource.jp/</a><br>English blog: <a href="https://shujisado.org/" target="_blank">https://shujisado.org/</a></div><div>Japanese blog: <a href="https://shujisado.com/" target="_blank">https://shujisado.com/</a></div><div><br></div></div></div></div>