2994 Attribution and Claim Discussion
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Opening this separately as the main issue thread has become quite noisy and to help move the process forward.
My PR set #3359, #3360, #3361 has been proven working both in my own testing and by @unpluggederan's [thorough testing](https://github.com/microg/GmsCore/issues/2994#issuecomment-4390002020).
At this point, @unpluggederan has suggested that attribution/payment can be discussed separately from the remaining code review and polish.
From what @omarsoufiane told me, the platform process works through approval emails sent to bounty contributors when a claim is submitted.
Are there any concrete contributions people believe should be considered for this claim?
Mentioning relevant people:
@mar-v-in
@unpluggederan
@malsatin
@azhao12345
@omarsoufiane
Recording of my local test
https://github.com/user-attachments/assets/b225ee32-3f90-4dc5-b954-3f0990622c89
[CI build for reference](https://github.com/opstic/GmsCore/actions/runs/26002196432), please install as a system app and turn everything on.
This is intended as a bounty attribution thread, not a microG issue report.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing PRs #3359, #3360, and #3361 together with the linked CI build and testing evidence. The thread is complete when the relevant contributions are identified and the bounty attribution claim has a clear decision; it does not define a code change to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100