makeplane / makeplane/plane

AGPL v3.0 and the proprietary apps/api/plane/utils/email.py

Open
#8,996 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

I found a file, which seems to have a "Proprietary and confidential" notice on top: apps/api/plane/utils/email.py

# SPDX-FileCopyrightText: 2023-present Plane Software, Inc.
# SPDX-License-Identifier: LicenseRef-Plane-Commercial
#
# Licensed under the Plane Commercial License (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
# https://plane.so/legals/eula
#
# DO NOT remove or modify this notice.
# NOTICE: Proprietary and confidential. Unauthorized use or distribution is prohibited.

I'm not sure how compliant this is. The Community Edition is supposed to be licensed under AGPL v3.0 and it should be possible to build it without any proprietary files.

https://developers.plane.so/self-hosting/editions-and-versions states:

About our self-hosted editions
Community
Built with transparency in mind, the Community Edition,

  • Is governed by the AGPL v3.0 license, ensuring free and open usage
  • Allows contribution to the repo by way of modifications and customizations
  • Has no code dependencies or restrictions on and from the Commercial Edition

Pangolin seemed to have a similar issue, which was resolved in the past: https://github.com/fosrl/pangolin/issues/1620

Contributor guide

Open the contributing guide

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.

Research direction

Start with apps/api/plane/utils/email.py and compare its license notice with the Community Edition claims in the linked self-hosting documentation. Trace whether this file is included in the Community Edition build and whether it introduces a Commercial Edition dependency or restriction. Done means the licensing conflict is resolved or the project documents a clear, supported explanation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.