Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://floss.social/users/be/statuses/111365415950612191">CEO of Anti-Clock Society (be@floss.social)'s status on Tuesday, 07-Nov-2023 09:50:41 JST</a><a href="https://floss.social/@be" title="be@floss.social"><img src="https://gnusocial.jp/avatar/9445-48-20220908152240.webp" width="48" height="48" alt="CEO of Anti-Clock Society" style="position: absolute; left: 0; top: 0;">CEO of Anti-Clock Society</a><div><a href="https://social.coop/@shauna/111365202713669482" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/21209" title="cwebber@octodon.social">Christine Lemmer-Webber</a></li><li><a href="https://gnusocial.jp/user/75487" title="luis_in_brief@social.coop">Luis Villa</a></li><li><a href="https://gnusocial.jp/user/84683" title="shauna@social.coop">Shauna GM</a></li></ul></div></section><article><p><a href="https://social.coop/@shauna">@shauna</a> <a href="https://social.coop/@luis_in_brief">@luis_in_brief</a> <a href="https://octodon.social/@cwebber">@cwebber</a> <a href="https://sms.cybik.moe/@root">@root</a> I'd encourage them to add a clause to the CLA like Signal and Slint (<a href="https://github.com/slint-ui/slint/discussions/244" rel="nofollow noreferrer">https://github.com/slint-ui/slint/discussions/244</a>) that obliges them to continue publishing the software with an OSI approved license, so that they can't just decide to make it proprietary one day (which they could have before with the Apache license).</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2290151#notice-4517147">In conversation</a><time datetime="2023-11-07T09:50:41+09:00" title="Tuesday, 07-Nov-2023 09:50:41 JST">about a year ago</time> <span>from <span><a href="https://floss.social/@be/111365415950612191" rel="external" title="Sent from floss.social via ActivityPub">floss.social</a></span></span><a href="https://floss.social/@be/111365415950612191">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/slint-ui/slint/discussions/244">guarantee FOSS licensing of SixtyFPS · slint-ui/slint · Discussion #244</a></h5><div></div></header><div>I'm really interested and excited for what SixtyFPS will become, but I'm also very wary of using it, promoting it, or contributing to it because of the CLA, especially in the context of recent even...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
CEO of Anti-Clock Society (be@floss.social)'s status on Tuesday, 07-Nov-2023 09:50:41 JSTCEO of Anti-Clock Society
in reply to
@shauna @luis_in_brief @cwebber @root I'd encourage them to add a clause to the CLA like Signal and Slint (https://github.com/slint-ui/slint/discussions/244) that obliges them to continue publishing the software with an OSI approved license, so that they can't just decide to make it proprietary one day (which they could have before with the Apache license).
In conversationabout a year ago from floss.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  guarantee FOSS licensing of SixtyFPS · slint-ui/slint · Discussion #244
  I'm really interested and excited for what SixtyFPS will become, but I'm also very wary of using it, promoting it, or contributing to it because of the CLA, especially in the context of recent even...

Public

Embed Notice

HTML Code

Corresponding Notice