@fourstepper @logseq @obsidian Hello, any open source project of a reasonable size is going to require a CLA. Firefox, Apache, Signal and many others do. They exist because if the license ever needs to be changed it would be impracticable to get the authorisation of all previous contributors. That being said, just because there's no CLA doesn't mean the license will never change. An MIT project for example can have its license changed with or without the contributors agreement.
this post was submitted on 22 Nov 2023
1 points (60.0% liked)
Logseq
611 readers
1 users here now
Logseq is a knowledge management and collaboration platform. It focuses on privacy, longevity, and user control. It is Free Libre Open Source Software (AGPL-licensed).
Logseq offers a range of powerful tools for knowledge management, collaboration, PDF annotation, and task management with support for multiple file formats, including Markdown and Org-mode, and various features for organizing and structuring your notes.
Logseq's Whiteboard feature lets you organize your knowledge and ideas using a spatial canvas with shapes, drawings, website embeds, and connectors. You can visually group and link your notes and external media (such as videos and images), enabling visual thinkers to compose, remix, annotate, and connect content from their knowledge base and emerging thoughts in a new way.
In addition to its core features, Logseq has a growing ecosystem of plugins and themes that enable a wide range of workflows and customization options. Mobile apps are also available, providing access to most of the features of the desktop application. Whether you're a student, a professional, or anyone who values a clear and organized approach to managing your ideas and notes, Logseq is an excellent choice for anyone looking to improve their productivity and streamline their workflow.
founded 2 years ago
MODERATORS
@joplinapp @logseq @obsidian Hi, to address your points:
- You mention if the license ever needs to be changed - what circumstances would warrant a license change, in your opinion? I would generally expect the license not to change
- In cases of both Apache and Signal the CLA one signs signs off the contribution to the respective foundations, not an LTD as is case with Joplin
- MIT (or other permissive licenses) re-licensing can be protected by a DCO https://developercertificate.org , (under point 4)
@fourstepper @logseq @obsidian That would be a good question for big open source projects who may have lawyers to advise them. For Joplin, this was mostly my decision and done "just in case". AGPL is suitable but not perfect - if a better license comes up later on, then we can switch to it. With a CLA we can do this, without it we're stuck with the same license pretty much permanently.