Skip to content

Minutes, 2017 04 10

Michael Hall edited this page Feb 28, 2018 · 1 revision

Attendees

  • Cosimo
  • Allan
  • Matthias
  • Alex
  • Emmanuele
  • Florian
  • Jorge
  • Juraj
  • Mario
  • Patrick

Minutes

Current implementation

  • Used buildbot because it was the easiest
  • Works for i386 and x86_64
  • Single signing key
  • Super-minimal, allows to build stuff and install stuff

Branches

  • Each app has its own individual commit history, so it lives in its own branch
  • If something needs to be shared, requires a git submodule or something like that

How does the review process work?

  • PR-based flow on the github repo
  • Buildbot can also do "try builds" from a branch
  • Somewhat hard to make a PR that goes to a new branch, which we'd be asking people to do
    • People that review the PR would need to adjust the target branch

How would we delete an app after it has been published?

  • On one side, we can remove the app from the github repository, but some other process would need to purge it from the OSTree repo
  • There's also an idea of a "tombstone" commit in OSTree that would flag it in such a way that it should be removed from the system (e.g. because it's malicious)
    • But for now it's just an idea, does not exist

Review team?

  • Right now just Alexander and Juraj
  • Alex can add more people to the team

Can we start adding recipes?

  • We should ask people to start adding their recipes and manifests
  • Not yet at a point where people should start using it in production/for wide use yet

ARM builders

  • These are still needed -- Alex wants to follow up with Tristan and/or use the other ARM machine we have in the GNOME datacenter

Licensing

  • Is GNOME a viable place to host these binaries, legally speaking?
  • Allan, Cosimo and Neil talked with the Board about it
    • Not a definitive answer but right now the GNOME Foundation would not be very happy about hosting non-free software
    • There is no problem however to using the GNOME Foundation as an incubator purely with free software
    • Neil was also looking into alternatives wrt. the legal organization/framework
      • Would this kind of solution be acceptable to our partners?
  • A free/non-free split could also be something to consider
    • Certainly we should always have an option to only ever receive free software
    • Another alternative would be to tag things differently

Stats/metrics

  • Would be great to have numbers for app publishers about the number of downloads

Store API in flatpak

  • Jorge shared a small presentation about this idea
  • Would require a "smart server" with a REST API
  • Could be good to have a better search experience from the command line

Hackfest around Flathub

  • Cosimo has found a place in Florence that could host us
  • Late May/early June? - about 6 weeks time
  • Does not feel it's required right now, but perhaps to face the next set of problems
    • Also will need to find some sysadmin time for this

Runtimes

  • They're hosted on the same server/repo, but not built there
  • They're imported from their canonical repo

Website

So what's next? ACTION ITEMS!

  • Get more stuff built to make sure it works (Alex)
  • ARM builders (Alex)
  • Try builds, figuring out the PR workflow
  • Review guidelines and documentation
  • Recruit a small team of people for reviews/management (Allan)
    • Sysadmin wanted -- ask the GNOME sysadmin list (Allan)
  • KDE applications/outreach
    • Aleix has been quite active, we'll try to get him involved, especially if it helps with the ARM story
  • Improve the website - replace the homepage at flathub.org with a placeholder (Allan to ask Jimmac)
  • Dogfooding!