Locally building my app (through extra-data, no sources, few modules like zypak), I encountered lots of known issues related to meson build systems, kernel errors and some minor issues, especially when using Flatpak builder itself as a flatpak app.
Or is it better to leave it in the hands of Flathub. If so, what is the process to make a submission on behalf of an org? Also can we get it verified after publication, transfer ownership etc?
The title does not match what you are asking.
Or is it better to leave it in the hands of Flathub.
It must be buildable, “leaving it at the hands of Flathub” will not automatically make it buildable and working. That’s upto you or whoever is submitting to make it work.
If so, what is the process to make a submission on behalf of an org?
Same as how you’d submit it individually. You can submit with a GitHub account that’s member of the org. Submission | Flathub Documentation
Also can we get it verified after publication
Yes Verification | Flathub Documentation
transfer ownership etc?
By transfer ownership I guess you mean adding more maintainers / changing maintainers. Then yes you can ask additional maintainers to be added or removed if you are upstream of the app. Maintenance | Flathub Documentation
Flatpak does get built through flatpak-builder but not through the flatpak app - org.flatpak.Builder. The linter does get passed but the maintenance part does get tricky since theres a lot of abstraction of Flathub’s infra.
If I got this right, if I make the submission to flathub and gets reviewed I need not worry about gpg signing and verification since the flatpak repo is created and maintaned by flathub while I maintain the Github.
Also, how to get verified in flathub? The unique ID which should be hosted under org domain, how to generate the token?
Yes, correct
The linter does get passed but the maintenance part does get tricky since theres a lot of abstraction of Flathub’s infra.
Yes those will be handled by Flathub infra or during submission review.
Also, how to get verified in flathub? The unique ID which should be hosted under org domain, how to generate the token?
After it is accepted, you have to log on to the website to get it.
I assume it is flathub.com logged in with my github credentials. Does the verification work with subdomains token hosted. like if my app is com.myorg.myapp, Can I host the token in myapp.myorg.com?
And after submission and review of code, who initiates publication? I also have a few linter exceptions, can I submit that PR first?
And after submission and review of code, who initiates publication?
Happens automatically after being accepted.
I also have a few linter exceptions, can I submit that PR first?
Sure
Does the verification work with subdomains token hosted. like if my app is com.myorg.myapp, Can I host the token in myapp.myorg.com?
No, if the ID is com.myorg.myapp then you have to place the token at myorg.com/.well-known, if it is com.myorg.subdomain.myapp then you can place it at subdomain.myorg.com/.well-known.
See Requirements | Flathub Documentation on how this is calculated, the definitions are mentioned in that section.
Great! How are the checks made for the metainfo file. I am planning to provide the image links to the screenshots directly from raw github conent so its all in one place. But the PR I raise cannot validate the image links since I gave the source branch as master for the image links. Can it still be merged?
Also the developer_name tag. Can it be used in metainfo?
No that’s a bit of chicken and egg situation. You can switch the screenshot links once the repo is created. We need a working link in the submission PR.
Ok. Thanks. But what about subsequent PRs for the screenshots and updates? can I merge it myself or does someone who contributes manually does it?
And the developer_name tag seems to be in a lot of Apps. Can I use that?
Ok. Thanks. But what about subsequent PRs for the screenshots and updates? can I merge it myself or does someone who contributes manually does it?
And the developer_name tag seems to be in a lot of Apps. Can I use that?
Yes, to both.
Sorry I am confused. Yes - to I merge it myself?
Sorry I am confused. Yes - to I merge it myself?
Yea, the submitter gets access to the created repo. So you can merge PRs.