Minutes, 2017 05 22
Michael Hall edited this page Feb 28, 2018
·
1 revision
- Allan
- Alex
- Georges
- Joaquim
- Jorge
- Mario
- Richard
- Cosimo
- Florian
- RobMcQ
- Mailing list should now be working, Rob restored his root password
- Who should be on the list?
- People that are interested in maintaining the infrastructure
- What's the policy to access the list?
- We look at the requests individually
- Who should be on the list?
- Legal Framework
- The GNOME Foundation Board agreed to connect to our legal counsel to try and get answers to our questions
- Next step is to prepare the questions on an Etherpad, which Rob is working on at the moment
- Sysadmin time
- It may be easiest to manage the Flathub hosts as GNOME hosts, but that's not easy if we need to keep them outside of the GNOME administrative domain
- We will have to understand the legal framework around liability before we can architect a good solution for how the hosts' network should be built
- Alex posted architecture requirements document on the mailing list, but we hit the problem above while analysing it
- Outreach
- Allan about to go on holiday, but he'll set up a call with KDE and TDF when he's back
- Having an initial chat sounds useful at this point, even though the overall legal framework is not in place yet
- For organizations like Mozilla which build their own binaries, do we have any technical work to do to accommodate this?
- According to Alex we can add some kind of trusted path for partners that want to ship their own binaries without building them on our own infrastructure, should this be a blocker
- This could be a slippery slope though
- If we had the separation between a "store" that contains bundles made by other companies, and flathub as a build system, this would not be an issue
- Flathub does not necessarily end up being the only place to go at least in version 1, but this is something good to think about in the future, when the format gains more momentum
- A "partner" program sounds like a good idea in general though
- How do we handle the ownership of Flathub bundles? Application IDs don't have the name of the packager, but the upstream name
- That's generally OK, it's not different from how it works in packages at the moment
- We also as a policy will give access to the upstream developers whenever they ask for it or want to make changes to their bundle
- Website
- We have a new homepage, thanks to Jakub!
- Still a placeholder, but a nicer looking one
- Flathub for GNOME builds
- Now OSTree has a repository redirection feature that Alex implemented
- Technically this could already be made to work, but we don't know how reliable the infrastructure would be, so perhaps we should figure out things like backup and a better maintenance policy
- Themes
- We got most of the GTK3 themes, at least those that are in use by the most popular distributions
- Need to add icon themes now
- Also there's no hook from gnome-software to install the theme "runtime" automatically
- Screenshot hosting
- Alex landed this into Flatpak today
- Will land this in Flathub once it's released -- screenshots will be hosted there too
- Source code archiving
- Not enabled yet, will come as part as the release tomorrow as well
- Jorge demoes a web app that displays all the applications inside Flathub in a nice UI
- Upon clicking on an app, the details are displayed and a .flatpakref file can be downloaded
- Next steps
- CSS improvements
- Reviews
- Ratings
- Related applications
- Displaying screenshots
- We have designs, but they don't exist yet
- Allan is doing them for GUADEC