Framapiaf

Boud<a href="https://mastodon.ouvaton.coop/@ouvaton" class="u-url mention">@ouvaton</a> Je ne savais pas que le code source d'Overleaf soit sous l' <a href="https://framapiaf.org/tags/AGPL" class="mention hashtag" rel="tag">#AGPL</a> . Ce qui implique que chaque instance doit de façon *évidente* informer ses utilisateurs de cela : "a convenient and prominently visible feature" [0]A coup d'oeil et par <a href="https://framapiaf.org/tags/SearXNG" class="mention hashtag" rel="tag">#SearXNG</a> j'ai l'impression qu'Overleaf.com viole grossièrement l' <a href="https://framapiaf.org/tags/AGPLv3" class="mention hashtag" rel="tag">#AGPLv3</a> . La licence est hyper-cachée.<a href="https://framapiaf.org/tags/AGPLViolation" class="mention hashtag" rel="tag">#AGPLViolation</a> <a href="https://framapiaf.org/tags/AGPLv3Compliance" class="mention hashtag" rel="tag">#AGPLv3Compliance</a> [0] <a href="https://www.gnu.org/licenses/agpl-3.0.html" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://www.gnu.org/licenses/agpl-3.0.html</a> [1] <a href="https://www.overleaf.com" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://www.overleaf.com</a> [2] <a href="https://search.ononoki.org/search?q=overleaf+agpl" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://search.ononoki.org/search?q=overleaf+agpl</a> [3] <a href="https://search.ononoki.org/search?q=overleaf+affero" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://search.ononoki.org/search?q=overleaf+affero</a>

Asta [AMP]Any license experts want to weigh in from a legal and moral perspective? I want to be as close to Misskey compatible as I can with my database; the Misskey project has the actual SQL commands for initializing the database in the Misskey repo (seen here: <a href="https://github.com/misskey-dev/misskey/blob/develop/packages/backend/migration/1000000000000-Init.js" rel="nofollow noopener noreferrer" target="_blank">https://github.com/misskey-dev/misskey/blob/develop/packages/backend/migration/1000000000000-Init.js</a> and in other files). If possible, I would like to use their SQL commands. Normally when I use other people's code, I try and fork to maintain history; however, in this case, I just want the queries. I also won't be hosting on GitHub. Would it be appropriate for me to copy/paste the queries into my own file, mark the location where they're coming from to give credit (and include the original copyright, of course), then license (at least) that file as AGPL? Would I need to license the whole project as AGPL? I'm not opposed to that; I just want to make sure I'm as transparent as possible about where these queries and code are coming from. (For the record, the plan is to embed them into Rust functions because I don't want to load SQL queries from arbitrary text files; that is, all the SQL I want to be run will be internal). <a href="https://fire.asta.lgbt/tags/openSource" rel="nofollow noopener noreferrer" target="_blank">#openSource</a> <a href="https://fire.asta.lgbt/tags/gpl" rel="nofollow noopener noreferrer" target="_blank">#gpl</a> <a href="https://fire.asta.lgbt/tags/agplv3" rel="nofollow noopener noreferrer" target="_blank">#agplv3</a> <a href="https://fire.asta.lgbt/tags/agplv3Compliance" rel="nofollow noopener noreferrer" target="_blank">#agplv3Compliance</a> <a href="https://fire.asta.lgbt/tags/misskey" rel="nofollow noopener noreferrer" target="_blank">#misskey</a> <a href="https://fire.asta.lgbt/tags/sql" rel="nofollow noopener noreferrer" target="_blank">#sql</a> <a href="https://fire.asta.lgbt/tags/openSourceLicense" rel="nofollow noopener noreferrer" target="_blank">#openSourceLicense</a> <a href="https://fire.asta.lgbt/tags/licensing" rel="nofollow noopener noreferrer" target="_blank">#licensing</a>

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#AGPLv3Compliance