document flow of data from git repo through to F-Droid client
As a contributor to software in the f-droid repo, it would help no end to understand the flow of software through the f-droid project. What happens when a project is accepted to be included? Where is the code stored on the f-droid servers? Where are the build logs for software? What are pipelines? How is software updated? How often? Where are the binaries stored? Where is the list of packages? What format is it in? etc., etc. These are only examples of useful info I'd like to see, I'm sure there are more steps in the process.
At the moment I ask for a piece of software to be included, and then as if by magic it appears in the client a few days later. How? No idea. Sometimes the build breaks and it's hard to know why, whether I as a developer have done something wrong. I'm sure it would take load off the f-droid devs if upstream devs were able to figure out problems and fix them without asking for help.