#fdroid-dev

/

      • Tovok7 has quit
      • andybalaam has quit
      • _hc joined the channel
      • _hc has quit
      • ShapeShifter499 joined the channel
      • thezero has quit
      • NicoAlt joined the channel
      • _hc joined the channel
      • _hc_roving joined the channel
      • _hc_roving
        uniq[m]: actually it is kind if open so I'm here
      • _hc joined the channel
      • _hc_roving has quit
      • CiaranG joined the channel
      • CiaranG joined the channel
      • _hc joined the channel
      • _hc
        ok, finally made it in
      • hey CiaranG pserwylo cdesai est31 krt[m] mimi89999_0 mimi89999_m NicoAlt uniq[m], meeing time
      • for those who are around
      • mimi89999_m
      • NicoAlt
        Good morning!
      • _hc
        its a Catholic holiday here, so everything's closed, but I'm far from being a Catholic ;-)
      • NicoAlt
        Here too
      • and me too :P
      • mimi89999_m
        Or maybe it is good actually...
      • pserwylo
        hi, finally here for one :)
      • uniq[m]
        hey
      • _hc
        its funny, even our Jewish kindergarten has to be closed on the catholic national holidays
      • so the big news this week is that we finally merged s!176, which supports KVM has a full buildserver setup
      • NOTICE: [server] !176: complete staging buildserver setup on jenkins.deb… - https://gitlab.com/fdroid/fdroidserver/merge_requests/176
      • its been tested a lot, so I hope that it does not affect the f-droid.org buildserver at all, which is based on VirtualBox
      • NicoAlt
        Nice!
      • _hc
        we did that so we can run on Debian's reproducinle builds infrastructure
      • and that's working, we now have weekly full rebuilds
      • of the buildserver, then of the latest version of all apps in fdroiddata
      • NicoAlt
        Will Debian verify F-Droid's builds in some way?
      • _hc
        its currently up to 811 apps rebuilt on that run
      • Debian won't, but we will, using this job on jenkins.debian.net
      • NicoAlt
        On verification.f-droid.org?
      • _hc
        we still have to work out the detals
      • most likely, the builds will happen on jenkins.debian.net, and the info will be published on verification.f-droid.org
      • NicoAlt
        That's great!
      • _hc
        I'm also quite close to having a full VirtualBox buildserver instance running that will be the full staging setup for the f-droid.org setup
      • pserwylo
        yup, very cool.
      • _hc
        I'll add that as a gitlab-ci runner so that all merge requests to fdroiddata will be built on a copy of the real buildserver
      • and in other news, working on nailing down ideas for the Netidee grant application.
      • I talked with a doctor here who is pretty tech savvy (he spent 5 years working as a programmer). I was looking for info on how doctors use mobile devices
      • there were two cases that were relevant to us, with the Google-free device platform (e.g. Copperhead, Fairphone, etc)
      • one, doctors are starting to use their own devices, but with no oversight
      • two, in Austria, there is a big push to move a lot of record keeping to digital.
      • only Windows desktops are allowed, so they literally have PCs on a cart that they wheel around to access records while visiting patients
      • seems like a nice Copperhead Nexus 9 would work much better for reading PDFs
      • and hospital IT staff can then run repomaker and fully control the devices
      • that reminds me, I owe the Flyve people some replies
      • that's the free software Device Management platform built with fdroid and Fairphone
      • CiaranG
        _hc: Great news about the buildserver instance, let me know if you get stuck on anything
      • _hc
        CiaranG: will do, ideally, I could use the exact same scripts you use you copy files between build and signing boxes (VMs in this case)
      • if we can make the staging setup mirror the real one, then it'll make testing a lot easier
      • CiaranG
        Yep, I can help with that
      • _hc
        CiaranG: I could just give you root on the box, or you could send me docs
      • its IPv6 only though...
      • CiaranG
        IPv6 is fine. Let's do it by docs though, there's no point me doing anything if you can't reproduce what I've done
      • _hc
        ok
      • works for me
      • CiaranG: did you have a chance to look at the website deploy? pserwylo is also here, so its a good time to work out any open issues
      • CiaranG
        Started, but not finished. I don't have any issues yet.
      • Probably wiki accounts will need password resets afterwords, by the way
      • NicoAlt
        Do we want the wiki to stay actually? In the forum you can also create wiki posts.
      • We need to rewrite the buildserver logs and it's JS, though.
      • _hc
        NicoAlt: yeah, the wiki needs to stay
      • CiaranG
        Ultimately perhaps not, I don't know? But the app data, etc, on there is important, it would need somewhere else to go.
      • _hc
        we haven't (yet?) replaced the wiki for buildlogs, etc
      • yeah, with the goal of doing this migration in stages, this should only replace the wordpress and any static parts of the website
      • NicoAlt
        I forgot about the app pages. Maybe we can all integrate this in the new Jekyll one once, but there are big steps to go, I realize.
      • _hc
        the docs have been moved from the wiki also
      • but that's just manually copying wiki pages
      • unless we missed something, wordpress should be able to be entirely shutdown after the dploy
      • and the wiki needs to remain as is
      • CiaranG
        That's how I see it, yeah
      • pserwylo
        agreed.
      • NicoAlt
        We need to make static copies of the old forum, imho.
      • _hc
        yeah, that would be nice to have.
      • pserwylo
        well, we can optionally remove individual pages from the wiki to docs in the Jekyll site, but that is different to taking the wiki down completely.
      • _hc
        I guess we could do that with a scraper
      • CiaranG
        I can't help wondering how important it actually is
      • NicoAlt
        I would definitely do this, otherwise we are loosing years of discussions.
      • _hc
        I'm happy to do the scrape, it should be easy to deploy
      • just a one time copy
      • CiaranG
        cool
      • NicoAlt
        +1
      • _hc
        I'll do the scrape today
      • anything else on the website? that's all I've got. Time for someone to report next?
      • NicoAlt
        I think that's all from the website. I can go.
      • pserwylo
        i think i finished responding to your feedback NicoAlt
      • on the translation thing, so my question is:
      • merge for launch, but remove the language selector?
      • or make a launch branch, then merge into master?
      • _hc
        do you need to merge now? since the deploy is underway, can we just wait until its done before merging the l18n?
      • or I suppose we could just do the release tag on the website now and start merging
      • NicoAlt
        _hc: Actually, that's the best idea!
      • pserwylo
        no, but it may get conflict-ey if left
      • happy to tag as is too
      • _hc
        CiaranG: did you decide who should be in the website deploy whitelist? anything is fine by me. I was thinking that it could be whoever currently have post access, which I think is CiaranG pserwylo and mvdan
      • pserwylo
        in the meantime, my only report is that I'm back on client stuff after spending time i18n the website. fixing bugs around notifications when there shouldn't be notifications (which is really annoying me as a user) and the updates screen causing lots of ACRA reports and often showing the wrong info. Have a MR ready for the first problem, which I'll clean up and post tomorrow, then work on the updates tab.
      • _hc
        ok, I should be able to review it tomorrow
      • CiaranG
        _hc: I hadn't even considered it yet, but that sounds like a sensible starting point
      • _hc
        I could potentially do a 0.103.2 also
      • pserwylo
        the fixing notification stuff required refactoring how AppDetails listens for updates about the download progress. Instead of listening to DownloaderService broadcasts (which is only a subset of interesting events around installing an app), it now uses the events from AppUpdateStatusManager that mvp76 added, which are more semantic and easier to keep track of.
      • _hc
        CiaranG: ok, so pserwylo can make a release tag on fdroid-website.git now, and it'll be all set for deploy. Then we can merge new stuff in now without worrying about the deploy yet
      • then if we need to fix things for the deploy, we can make a 'launch' branch on pserwylo's release tag
      • pserwylo
        _hc: i still need to move my new key that you and the FOSDEM people signed onto the NitroKey you gave me.
      • alternatively I can suggest using my existing key for now, then let CiaranG know when my offline key is ready to roll.
      • _hc
        the new key is better
      • so there is a consistent history
      • perhaps CiaranG could do the first release tag, I think it should just be the HEAD of master right now
      • pserwylo
        I have been delaying it because it is really bloody hard to sign other peoples key with an offline key. How do you use caff and email people when you are not connected to the internet?
      • _hc
        yeah, I don't use caff then
      • pserwylo
        i can do the signing, then move the signature to an online machine, then manually attach to an email.
      • but I have ~100 keys to sign :(
      • _hc
        I just ask people: do you want me to publish this to the keyservers?
      • ah, right
      • maybe you can just copy the mail queue file from the offline machine
      • anyway, a topic for a nother time
      • pserwylo
        i'm thinking of, for practical reasons, keeping it "mostly-offline" and still only booting into an internet-enabled tails USB.
      • yup
      • i'm done with my report then.
      • NicoAlt
        OK, so I can go?
      • _hc
        one quick qesution for pserwylo
      • pserwylo: shall I do 0.103.2 tomorrow?
      • or you can tell me tomorrow, just send me an email
      • I'm done
      • NicoAlt: go!
      • NicoAlt
        I haven't been in meetings for quite some time (due to school), so I'm summarizing the last weeks.
      • Our UI designer Carrie has made a lot of beautiful sketches for Repomaker which Torsten and me are implementing.
      • Mostly me, but Torsten also did some stuff recently.
      • These are the screens I implemented so far: Create Repo, Repo Details (partly), Edit Repo, App Details
      • And the Repo homepage outside of Repomaker, so you don't have a Apache index but a beautiful page when clicking on /fdroid/repo.
      • I did this for mobile devices, Torsten for desktops.
      • Currently I'm working on "Add Apps".
      • Beside that, I fixed bugs, reviewed MRs and participated in UI discussions.
      • Because Torsten is not here, I'll also conclude partly what he has done.
      • He made remote repos update regularly, implemented some minor functions in the UI, made Repomaker more robust against errors and implemented the designs for login and repo lists.
      • For sure he worked on the server too, but I did not follow this.
      • Torsten will deploy the current Repomaker to repomaker.grobox.de next Wednesday for the UI tests, so you all can then check out what we've done :)
      • That's it.
      • _hc
        wow, the repo index is nice!
      • NicoAlt
        Thanks, that's Carrie's and Torsten's work.
      • Ah bummer that we don't have it in F-Droid server by default.
      • pserwylo
        NicoAlt: Looking great. I had a look at `master` a couple of days ago and it is very nice.