I wanted to ask if there are any known guidelines or limits regarding merge request waiting times for applications in the F-Droid repository?
My merge request has been pending for about one month now. While I understand that volunteer-driven projects operate on their own schedule, I was wondering if I should realistically expect further delays - perhaps 6 months or even a year or if this is within normal range?Any insight into typical wait times, current backlog status, or tips for improving the review process would be greatly appreciated.
Thank you for your work maintaining F-Droid!
As contributors have time 
That being said, this should not be a blocker for you or any other project to contiue as usual. 
True. Could you add a note to the Guideline mentioning that the requests may not be merged at all? That would be fair.
That’s not true, I mean, if the app respects the inclusion policy, it’s a question of time.
App won’t be merged at all
No, it can’t be said so. Many apps get merged within one day, many takes weeks, many even takes month. My own app took somewhere around 5 months. Earlier I thought same it’s too lengthy of a process, but Now As a Reporter on the Team I see every sort of time duration from 1 day to month.
Yep. Reply over there. I’ll do my best to test it today so yrs not stucked in queue
Thank you!
For a context: the App is basically a Tusky fork which core was replaced from ActivityPub to libp2p.
You need a running desktop Warpnet node physically reachable from the phone (the one that shows the pairing QR). Desktop node from the monorepo must be the same version: Release v0.7.475 · Warp-net/warpnet · GitHub MacOS is not supported - it could only be built from source, tag v0.7.475.
While QR code pairing the App runs its own micro-libp2p node and takes connection data from QR code. Data example:
{“user_id”:“01KTRA1Q83VBTES33BRQV79JN6”,“token”:“rkGt+lg=”,“psk”:“6f7854”,“node_id”:“12D3KooWQ3umNTQweTREML1gqyag4T2Ps82wLnHV7fUNQA8CnMa9”,“addresses”:[“/ip4/207.154.221.44/tcp/4033/p2p/12D3KooWNXSGyfTuYc3JznW48jay73BtQgHszWfPpyF581EWcpGJ/p2p-circuit”],“bootstrap_peers”:[“/ip4/207.154.221.44/tcp/4011/p2p/12D3KooWMKZFrp1BDKg9amtkv5zWnLhuUXN32nhqMvbtMdV2hz7j”],“network”:“mainnet”}
The App own micro-libp2p node connects to the network and sends libp2p stream pairing request to the desktop node. Pairing request contains “token” which was passed in QR code. Desktop node validates token and completes pairing.
After that the App downloads its timeline and posting is available. All messages sent thru libp2p streams - multiplexed TCP conns.