#fdroid-dev

/

      • Tovok7 has quit
      • perepujal joined the channel
      • _hc_roving joined the channel
      • _hc_roving
        uniq[m]: hey at metalab, impact hub was locked
      • uniq[m]: you around?
      • uniq[m]
        _hc: yes I'm at metalab now
      • _hc_roving has quit
      • _hc joined the channel
      • _hc
        cdesai: uniq[m] krt[m] pserwylo hello all meeting
      • uniq[m]
        hi
      • Tovok7 joined the channel
      • _hc
        hi Tovok7
      • Tovok7
        hi all!
      • mimi89999_m
        Did we came to a conclusion about Gradle 4?
      • cdesai
        hello
      • _hc
        mimi89999_m: didn't know this was a discussion, is there a link?
      • mimi89999_m
        What link?
      • _hc
        mimi89999_m: about gradle 4
      • mimi89999_m
        I asked here several days ago...
      • _hc
        ah, ok. as far as I know, we always just add new gradle versions. Is there a reason to not do that now?
      • Tovok7
        Not that I am aware of. I think just nobody has added it, yet.
      • mimi89999_m
        4 isn't stable yet, but several apps are using it, that I would like to see updated.
      • _hc
        mimi89999_m: I think its just a matter of adding the official release zip to ./makebuildserver
      • as usual
      • but then you have to wait until the buildserver is updated, which happens once a month
      • we should really support ./gradlew, then this would be a lot easier
      • I haven't heard of the reason why we don't
      • its explicitly not allowed
      • anyway, I have my report ready to go, so here goes:
      • I spent a lot of time writing the monthly report.
      • This is taking longer these days because we are nearing the end of the funding,
      • so I have to start clearly showing how we have achieved the things that are in the contract.
      • Plus the funder is now looking at issues and merge requests.
      • Some of the user research work is now published on the guarian project blog:
      • I'll post those to f-droid.org once the new site launches.
      • I've been reviewing merge requests, especially the website localization work from pserwylo w!70
      • seems to be a very complicated path where we see the perfect path, only to have it crushed by the strong point of view of one of the pieces of software in the chain
      • I've also been lining up the paid translators for Tibetan, Chinese, Spanish, and Farsi.
      • I was fascinated to learn that F-Droid will be the first app store available in Tibetan after that work is done.
      • I also looked into it a bit more. There are some other languages with many millions of speakers that are not available in app stores
      • For some of them, we already have active contributors, like Arabic, Armenian, Belarusian, Burmese, Hebrew, and Shona.
      • I've also been helping out with supporting APKs that have the same versionCode and packagename, but only a different signature
      • this means changes across the stack
      • we're quite close, and That's what I'll be focusing on going forward
      • NOTICE: [website] !70: I18n homepage - https://gitlab.com/fdroid/fdroid-website/merge_requests/70
      • EOF
      • Tovok7
        thanks _hc! I've read the report yesterday. Awesome work!
      • mimi89999_m
        Link?
      • _hc
        thanks, I guess it is readable?
      • cdesai
        +1 on the report being awesome.
      • mimi89999_m
        +1
      • uniq[m]
        it's amazing to see all the progress :)
      • _hc
        yeah, I should remember to think about it that way
      • I still mostly think about all the things we are supposed to finish
      • mimi89999_m
        What is to be done yet?
      • Tovok7
        don't remind _hc about that ;)
      • _hc
        full reproducible build process
      • supporting mirrors in the client
      • are two big once
      • ones
      • supporting APKs that differ only by sig
      • getting swap working well
      • and more :-)
      • but I'm not so worried, especially once we launch the new website with localization
      • mimi89999_m
        c!35 I see
      • _hc
        that will be a big thing done
      • who's next?
      • cdesai
        I have a very small report this week
      • shall I?
      • _hc
        go
      • NOTICE: [client] !35: Show update errors to the user - https://gitlab.com/fdroid/fdroidclient/merge_requests/35
      • cdesai
        got back after a break for exams this week, and started with !486 which is wrapped up now
      • NOTICE: [client] !486: PrivExt API >= 24 uninstall fixes. - https://gitlab.com/fdroid/fdroidclient/merge_requests/486
      • looking at !478 right now, and once that is done I will look at media support, and then other 0.104 things.
      • NOTICE: [client] !478: WIP: System app uninstall fixes - https://gitlab.com/fdroid/fdroidclient/merge_requests/478
      • EOF
      • _hc
        yay media support! I think it shouldn't be too hard. that's one of the things on the list that needs doing
      • cdesai
        you pretty much wrote the entire code in that issue, I think all I need to do is add it in and test.
      • _hc
        I forgot to mention: one of the Fairphone developers finally tried out cdesai's priv-ext merge requests
      • Tovok7
        what did they say?
      • _hc
        cdesai: testing the media support will be important. We want it to automatically show up in popular viewer/player apps
      • cdesai
        _hc: understood, will remember that.
      • _hc
        Tovok7: they said it worked for them, and they reported a bug that we know about, where client always shows an update for itself
      • it'll be fixed in the next release
      • Tovok7
        so once that is fixed, it will be included in their next image?
      • _hc
        no specific news on that yet
      • but that's what we all talked about back in Amsterdam
      • as the plan
      • also, I forgot to mention. go free software: I reported bugs in Weblate with details, and they are already fixed!
      • Tovok7
        wohoo \o/
      • _hc
        I'll be sending them some kind of payment from the Bazaar2 budget, I just have to figure out exactly how much
      • probably like $200-300
      • who's next
      • Tovok7
        I can go
      • _hc
        g
      • o
      • Tovok7
        We had remote video UI testing sessions for repomaker with several people which was largely successful, but still identified some areas for improvement.
      • So last week, we've been doing mostly those and also fixing some issues we had put back due to the testing coming up.
      • The biggest new feature that I merged yesterday is support for other file types than APKs. It is still a bit basic, but so is this feature all over our stack.
      • Also interesting maybe that we now use the Boards from Gitlab do keep an overview over our work and to prioritize it as we are approaching project's end.
      • We have two boards. One for development: https://gitlab.com/fdroid/repomaker/boards?mile...
      • Actually, it is the same board, but filtered by different labels. The ToDo list on the left is our backlog sorted by priority/cost/benefit.
      • Last, but not least yesterday I slightly improved the fdroidserver library API (that is slowly shaping up) in s!288
      • I'll be travelling tomorrow, so will miss the next meetings.
      • EOF
      • cdesai
        <Tovok7> The biggest new feature that I merged yesterday is support for other file types than APKs. - great :)
      • NOTICE: [server] !288: Break down the update.scan_apk() method into smal… - https://gitlab.com/fdroid/fdroidserver/merge_requests/288
      • _hc
        media support all over!
      • Tovok7
        cdesai: I'll deploy this to repomaker.grobox.de soon
      • will let you know when done
      • cdesai
        thanks Tovok7
      • _hc
        cdesai: let me know if you need more media files added to testy.at.or.at
      • Tovok7
        I'd prefer cdesai uses repomaker to add his own test files, so this new feature gets some testing exposure as well :)
      • cdesai
        _hc: sure.
      • Tovok7 can always test both, to ensure everything works.
      • _hc
        ok, as long as it is quick for him to setup
      • cdesai
        adding files to repomaker.grobox.de was super quick :)
      • _hc
        cool, and publishing?
      • Tovok7
        he doesn't need to setup anything
      • this instance has default storage configured
      • _hc
        ah, ok, cool
      • :)
      • Tovok7
        right on the same webserver for convienince
      • _hc
        who's next?
      • uniq[m]
        i can go
      • I've finally finished `frdoid publish` to wrap up APKs with developer signatures.
      • The convention now is to also append the first 7 hex-digits of the signing-keys sha256 fingerprint.
      • eg: repo/info.guardianproject.browser_7010_d716207.apk
      • FDroids esablished singing mechanism remains completely untouched.
      • So this means there'll also be an APK without signing-fingerprint in its name, signed with the configured local keystore.
      • Should the signature stored in the metadata not validate on the APK which is about to be signed, the APKs for this app won't get published since they're not reproduceible.
      • I also made a new sub-command called `fdroid fetchsigs APK [APK...]`.
      • It will extract signatures from APKs and store them as metadata.
      • Http URLs will also work with this sub-command.
      • that's it for me.
      • _hc
        maybe it should be called `fdroid signatures` since the folder is called metadata/signatures
      • mimi89999_m
        _hc: +1
      • _hc
        this should then give us the whole stack for people to submit reproducible builds
      • uniq[m]
        sure :)
      • I'm also not entirely sure if we should allow fetching APKs via http for extracting signatures
      • looked convenient for me when I implemented it, I'm just not sure if this allows sloppy handling of signatures
      • _hc
        seems like we could use a standard pattern like --no-check-https to disable that, and by default require valid https
      • uniq[m]
        good point
      • _hc
        wget has --no-check-certificate
      • this stuff will also be cool, since we can go back and add the developer signatures to any APKs that we can already reproduce
      • mimi89999_m
        Once the first app version is published, then http is not an issue since we can check if the sig matches the one of the version before.