Skip to content

Commit

Permalink
update wording
Browse files Browse the repository at this point in the history
  • Loading branch information
ezekg committed Oct 17, 2024
1 parent bfc0e09 commit 396a51a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -128,10 +128,10 @@ <h4>
What types of projects are a good fit for the <abbr title='Fair Core License'>FCL</abbr>?
</h4>
<p>
Projects with commercial features that are self-hosted or run on-premise, and want to safely share <em>all</em> of their code — not just <em>some</em> of it. If your project doesn't monetize self-hosting, you may want to consider the <a href='https://fsl.software' target='_blank' rel='noopener'>FSL</a> instead, which isn't concerned with commercial features.
Projects with commercial features that are self-hosted or run on-premise, and want to safely share <em>all</em> of their code — not just <em>some</em> of it. If your project doesn't monetize self-hosting, you may want to consider the <a href='https://fsl.software' target='_blank' rel='noopener'>FSL</a> instead.
</p>
<p>
In addition, the <abbr title='Fair Core License'>FCL</abbr> may be an ideal choice for projects moving from a closed source model to Fair Source, because commercial features can simply be wrapped in a license key check, requiring minimal project reorganization compared to Open Core.
In addition, the <abbr title='Fair Core License'>FCL</abbr> may be an ideal choice for projects moving from a closed source model to Fair Source, because commercial features can simply be wrapped in a license key check, requiring minimal project reorganization.
</p>
<h4>
How does the <abbr title='Fair Core License'>FCL</abbr> contribute to Open Source?
Expand Down

0 comments on commit 396a51a

Please sign in to comment.