POST: open source impoverishment

Open
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
content

Research direction

No file, test, or entry point is identified, and the issue does not define a specific content change. First clarify whether the Docusaurus/Markdown website should publish an article or revise existing material, identify the target page, and agree on acceptance criteria before starting; completion cannot be determined from the current issue.

Written by the indexing model from the issue text.

Description

blog ready-to-post

What are the benefits of open source software or free, libre and open source software?

If open source is defined by licensing, then the biggest win of open source has been to move legalese and legal discussion about software licensing to the background.

The essence of open source licensing has been to remove most of the friction about legales from software development.

I can talk about MIT, BSD or GPL and with each of these three letters, you know what licensing terms I am talking about. In contrast, a commercial contract or an unknown license will require legal review.

As a dev, I can make quick policy-aligned decision about whether or not I can reuse a piece of code with these few letters.

But a new generation of programmers wants to revisit this well established community status quo.
To them, developers do not care about "open source" as defined by the OSI or the FSF, and only a few old activist guys with backward ideas care for that.

And they are coming with new FUBAR fauxpensource licenses that erode and impoverish the discourse about software licenses, bringing legalese back to the forefront.

The sad thing is that these thrive on confusion and often present to be open source and use license that look like open source licenses, deceiving developers that cannot grasp all the minute details of legal shenanigans.

So this is a plea for open source licensing clarity, against things that look like but are not open source:

  • Commercial licenses are fine.
  • Open source and free and open source licenses are great.
  • Proprietary and source available licenses based on confusing, open source-like terms that are trying to ride the coattails of FOSS goodwill with deception are a terrible poison pill.

Let's get rid of these.

Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.