TeamAmaze / TeamAmaze/AmazeFileManager

Handle Copycats (License fraud)

Open
#1,529 6 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Discussion
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

I'ts ok to copy AmazeFileManager as long as you do not violate our GPL3 License. Please inform yourself about GPL3 before forking!!!

How should we handle these copycats in the future?

List of copies/forks

Forks in Playstore
Paid
Not Paid

Removed

This is a copy of the issue at NewPipe.

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 by reviewing LICENSE.txt and the linked GPLv3 guidance, then compare the reported Play Store copies with the discussion in the linked NewPipe issue. Done means the project has an agreed, documented approach for handling future copycat reports; the issue does not identify a code file or test to change.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.