[Feature Request] Keep Android Open initiative
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
Research direction
The issue names no file, test, or entry point. Start by reviewing the Keep Android Open site and the linked F-Droid merge request, then identify where a user-facing announcement could belong in this client. Done should be defined by choosing one concrete form of support, such as an in-app banner, and agreeing on its placement and content.
Written by the indexing model from the issue text.
Description
Before you submit
- I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
- I'm not requesting app support for a specific repo — that's up to repo maintainers
- I understand this might not get built (Droid-ify is maintained by a single person)
What's the problem?
Hello, as you probably know google announced enrolling mandatory developer verification for all installed apk (even those which are installed outside of playmarket). Practically rendering android as very unfree OS. In response to that emerged "Keep Android Open" initiative. If it resonates with you and your goals, please support it and spread the word.
What would help?
For more info look at their site https://keepandroidopen.org/ but here is a short list of what you can do:
- Spread the word between your users
- Add in app banner for example how fdroid did
- Add banner to your site https://keepandroidopen.org/banner/
- Add banner to your projects page like this or even this
- Share on social media like fdroid did on their mastodon
- Sign the letter https://keepandroidopen.org/open-letter/
- Let Google know you disagree with it
Alternatives?
No response
Anything else?
You are client for fdroid which means if they enroll it you can find yourself in critical situation
- Dominant language
- Kotlin
- Stars
- 7.7k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Droid-ify/client
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in Droid-ify/client
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
liberation-data/drivine4j#547 ·
Maintainers usually reply within 1 day
-
App asks for diameter for emergency=hydrant + water_source=groundwater. But should probably not.Openfeedback required
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
streetcomplete/StreetComplete#7354 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Lists import errorOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PimpinPumpkin/Vela#921 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day