Skip to content

chore: Merge branch dev to main #5

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

Open
wants to merge 17 commits into
base: main
Choose a base branch
from
Open

chore: Merge branch dev to main #5

wants to merge 17 commits into from

Conversation

github-actions[bot]
Copy link

This pull request will Merge branch dev to main.

brosssh and others added 6 commits July 3, 2025 14:27
# [1.1.0-dev.3](v1.1.0-dev.2...v1.1.0-dev.3) (2025-07-03)

### Bug Fixes

* Fix release workflow (again) ([5bde601](5bde601))
# [1.1.0-dev.4](v1.1.0-dev.3...v1.1.0-dev.4) (2025-07-03)

### Bug Fixes

* Add gradle sha256 checksum ([f259821](f259821))
# [1.1.0-dev.5](v1.1.0-dev.4...v1.1.0-dev.5) (2025-07-04)

### Bug Fixes

* Correctly removing bundle attributes from manifest ([6433d98](6433d98))
@brosssh brosssh requested a review from Axelen123 July 4, 2025 13:17
@brosssh
Copy link
Member

brosssh commented Jul 4, 2025

The repository name should be changed to revanced-manager-downloaders , as well as the description to 🔌 ReVanced Manager Downloaders.

@brosssh brosssh marked this pull request as ready for review July 4, 2025 13:22
brosssh and others added 2 commits July 4, 2025 18:37
# [1.1.0-dev.6](v1.1.0-dev.5...v1.1.0-dev.6) (2025-07-04)

### Bug Fixes

* Showing progress if downloading an APK + minor fixes ([d46f002](d46f002))
@brosssh brosssh requested a review from Axelen123 July 4, 2025 16:45
Copy link
Member

@Axelen123 Axelen123 left a comment

Choose a reason for hiding this comment

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

The -downloader suffix seems unnecessary since the downloaders are inside the downloaders folder.

brosssh and others added 2 commits July 8, 2025 13:23
# [1.1.0-dev.7](v1.1.0-dev.6...v1.1.0-dev.7) (2025-07-08)

### Bug Fixes

* Refactor of shared module + minor fixes ([5f6c7e5](5f6c7e5))
@brosssh brosssh requested a review from Axelen123 July 8, 2025 11:28
@brosssh
Copy link
Member

brosssh commented Jul 8, 2025

Should the downloader APK file name start with revanced-manager-?

@Ushie
Copy link
Member

Ushie commented Jul 8, 2025

Yes, as it is scoped specifically for ReVanced Manager

brosssh and others added 2 commits July 8, 2025 21:08
# [1.1.0-dev.8](v1.1.0-dev.7...v1.1.0-dev.8) (2025-07-08)

### Bug Fixes

* Prefixing APKs with `revanced-manager-` ([f4c91f0](f4c91f0))
@brosssh brosssh requested a review from oSumAtrIX July 8, 2025 20:13
@oSumAtrIX
Copy link
Member

We should probably change names to a better naming convention, like:

"ReVanced Manager v1.2.3.apk" instead of "revanced-manager-v1.2.3.apk"

For downloaders, I mentioned the naming question in another place i don't remember but i pinged the relevant parties

@brosssh
Copy link
Member

brosssh commented Jul 13, 2025

We should probably change names to a better naming convention, like:

"ReVanced Manager v1.2.3.apk" instead of "revanced-manager-v1.2.3.apk"

For downloaders, I mentioned the naming question in another place i don't remember but i pinged the relevant parties

Is this blocking merge into main? What should be the naming convention for downloaders?

@oSumAtrIX
Copy link
Member

Personally, I would like to see the following changes:

  • The term "plugin" should be removed entirely. Currently, downloaders are referred to as "plugins," but unless we have other plugins apart from downloaders, this labeling is confusing. Please remove it from the code, as well as any references in strings, documentation, etc.
  • The base name should be "ReVanced Manager downloader" (or "ReVanced Manager downloaders" once multiple APKs can be supported).
  • Conventionally, the name for downloaders would be something like "ReVanced Manager APKMirror downloader." However, once more options are available, the name of the APK should follow the format "ReVanced Manager downloaders," for example, "ReVanced Manager Brosssh downloaders."

Here are some issues and questions to consider:

  • In our case, it would be named "ReVanced Manager ReVanced downloaders." Should we omit "ReVanced"? If we do that, should we also consider omitting "ReVanced" in "ReVanced Patches"? Not doing so would create inconsistency etc.
  • Simply using "downloaders" is ambiguous. We should specify "APK downloaders." Furthermore, we need to decide on the term: should it be "app downloader," "apps downloaders," or "app downloaders"? This could also lead to longer names like "ReVanced Manager ReVanced app downloaders."
  • What should we name the internal packages? Here are some possibilities:
    • app.revanced.manager.downloaders.
    • app.revanced.manager.apkdownloaders.
    • .revanced.manager.downloaders.
    • And potentially others...

@Axelen123
Copy link
Member

The term "plugin" should be removed entirely. Currently, downloaders are referred to as "plugins," but unless we have other plugins apart from downloaders, this labeling is confusing. Please remove it from the code, as well as any references in strings, documentation, etc.

What should we name the internal packages? Here are some possibilities:

  * app.revanced.manager.downloaders.
  * app.revanced.manager.apkdownloaders.
  * .revanced.manager.downloaders.
  * And potentially others...

We had lengthy discussions while the downloader system was still in development, and I am sure this was discussed at some point. Why is this being brought up again?
I see no issue with using the word "plugin" in code or here in Manager:
image

I don't think these two uses are confusing. The README does not use the term "plugin" at all.

The base name should be "ReVanced Manager downloader" (or "ReVanced Manager downloaders" once multiple APKs can be supported).

Conventionally, the name for downloaders would be something like "ReVanced Manager APKMirror downloader." However, once more options are available, the name of the APK should follow the format "ReVanced Manager downloaders," for example, "ReVanced Manager Brosssh downloaders."

The two downloaders in this PR seem to be following this already.

In our case, it would be named "ReVanced Manager ReVanced downloaders." Should we omit "ReVanced"? If we do that, should we also consider omitting "ReVanced" in "ReVanced Patches"? Not doing so would create inconsistency etc.

In that situation, "ReVanced Manager official downloaders" or just "ReVanced Manager downloaders" would do.

Simply using "downloaders" is ambiguous. We should specify "APK downloaders." Furthermore, we need to decide on the term: should it be "app downloader," "apps downloaders," or "app downloaders"? This could also lead to longer names like "ReVanced Manager ReVanced app downloaders."

Downloader is not ambiguous in the context of ReVanced Manager, since it only deals with Apks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants