Skip to content

Relicense core to FSL #388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 20, 2025
Merged

Relicense core to FSL #388

merged 2 commits into from
Jul 20, 2025

Conversation

msukkari
Copy link
Contributor

@msukkari msukkari commented Jul 20, 2025

TL;DR in v4.5.3 we relicensed our core from MIT to the Functional Source License (FSL). If you’re just using Sourcebot as a developer tool, your rights to use, modify, and redistribute the tool doesn’t change. However, if you’re using Sourcebot’s code for a product that competes with us, you will no longer have the right to do so moving forward.

Have a question about this change? Feel free to reach out to us at license@sourcebot.dev

Learn more here

@msukkari msukkari requested a review from brendan-kellam July 20, 2025 02:07
Copy link

coderabbitai bot commented Jul 20, 2025

Walkthrough

The project’s licensing terms were updated. The LICENSE file was changed from the MIT Expat license to the Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2), and the changelog was updated to document this license change under the "Unreleased" section referencing pull request #388.

Changes

File(s) Change Summary
LICENSE Replaced MIT Expat license with Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2).
CHANGELOG.md Updated "Unreleased" section to note the core's relicensing to FSL-1.1-ALv2 (PR #388).

Poem

A license anew, the project now wears,
FSL-1.1-ALv2, with future Apache flares.
The changelog records this legal leap,
While code and bunnies quietly keep
Hopping forward, tails held high—
New terms beneath an open sky! 🐇📜


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

This comment has been minimized.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
LICENSE (1)

1-8: Add an SPDX license identifier
Many build and compliance tools rely on an SPDX header to auto-detect the license. Consider inserting it right after the copyright line:

 Copyright (c) 2025 Taqla Inc.
+SPDX-License-Identifier: FSL-1.1-ALv2
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dea1807 and d491e28.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • LICENSE (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/style.mdc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (2)
CHANGELOG.md (1)

10-12: Changelog entry looks good
The note accurately reflects the relicensing and references the correct PR.

LICENSE (1)

97-115: Verify license metadata in all package manifests
I’ve searched JSON, TOML, Python, and YAML files for any lingering MIT license declarations and found none. To be safe, please also manually confirm that other manifest formats don’t still reference MIT, for example:

  • Maven POMs (pom.xml)
  • Ruby Gemspecs (*.gemspec)
  • .NET projects (*.csproj)
  • Gradle builds (build.gradle, build.gradle.kts)

@msukkari msukkari merged commit 008d8ec into main Jul 20, 2025
6 checks passed
@msukkari msukkari deleted the fsl branch July 26, 2025 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy