#fdroid-dev

/

      • Tovok7 has quit
      • larjona joined the channel
      • _hc
        krt[m]: ah, right, sorry, I forgot! yes, studying and exams comes first!
      • _hc has quit
      • _hc joined the channel
      • BubuIIC joined the channel
      • BubuIIC
        Just installed the latest fdroid version. Looks really, really nice!
      • _hc
        thanks!
      • BubuIIC has quit
      • Tovok7 joined the channel
      • _hc has quit
      • _hc joined the channel
      • Tovok7
        _hc: would be interesting to have your opinion on rm#56
      • NOTICE: [repomaker] #56: Need to know the source, disable editing details … - https://gitlab.com/fdroid/repomaker/issues/56
      • ludkiller
        oh _hc
      • _hc
        Tovok7: thezero uniq[m] pserwylo CiaranG krt[m] cdesai hey all meeting time :)
      • Tovok7: responded
      • Tovok7
        thanks _hc!
      • _hc
        I'll start then
      • pserwylo and i finished up the website deploy procedure, and I documented it:
      • website!72
      • I've been setting up a new, dedicated box to run a mini staging version of the f-droid.org build infrastructure.
      • uniqx and I are putting together a proposal for funding "F-Droid as core to 100% free software Android" for the https://www.netidee.at fund. Up to 50,000 Euro.
      • we'll probably also put in a Guardian Project proposal for CipherKit/NetCipher/etc work and maybe also privacy-preserving analytics and crash reporting
      • did some accounting work as usual
      • NOTICE: [website] !72: Deploy doc and update - https://gitlab.com/fdroid/fdroid-website/merge_requests/72
      • about the netidee proposal, we need more info on use cases for Google-free devices in the EU
      • the use of android devices in the medical context is one of them
      • Tovok7
        The netidee stuff sounds intersting. Good luck with it!
      • _hc
        about the website deploy procedure, CiaranG OK'ed the use of Docker, and will hopefuilly be able to set it up this weekend! :-D
      • Tovok7
        wohoo!
      • _hc
        this is a bad time for pserwylo, so I'll throw in that he's been working away on making the website fully localizable
      • its pretty close, but we're going to launch the new website only in English
      • to make sure it gets launched
      • then we can launch the localized work when its ready
      • mvdan has quit
      • [gibot] has quit
      • I also started the process to hire translators for Tibetan and Simplified Chinese for everything, and Spanish and Farsi for repomaker
      • [gibot] joined the channel
      • spanish and chinese are both very widely spoken, and also priorities of the funder
      • mvdan joined the channel
      • Tibetan presents an interesting opportunity, since F-Droid will probably be the only app store available in Tibetan
      • EOF
      • who's next?
      • cdesai
        I've been away another week due to college work, but it seems I'll have time before exams in the next week.
      • Tovok7
        Last week, I worked on lots of smaller issues to improve the repomaker prototype. Here are some examples:
      • We know store the mirrors of remote repositories, but we don't use them yet when the main location is down. But we are updating remote repositories daily now and disable them when fetching them fails permanently.
      • We support now localized feature graphics and support searching through apps from all remote repositories you have access to.
      • The keystore of each repository now uses a different password. This is a step to later maybe allow the password to be entered by the user or to limit access to the keystore.
      • We wrote more tests and increased our test coverage to 85%.
      • Also, more UI designs are getting ready and we implemented the first ones already. There is for example already a repository homepage with instructions for how to add the repo and a preview with the apps inside that repo.
      • We have a UI test scheduled now, but still a lot of work ahead of us: https://gitlab.com/fdroid/repomaker/milestones/1
      • According to our burndown rate in the past, we will most likely not be able to finish all the designs in time.
      • EOF
      • _hc
        we can always user test with paper mockups :)
      • i'm a big fan of that approach to start with
      • Tovok7
        haha, well the features to be tested are all there, they just don't look like the UX designer wants to, yet.
      • _hc
        let me know when you're ready to post strings to weblate
      • Tovok7
        we could start that process now, also to see if we are missing anything. Is there a way in weblate to block people from translating?
      • _hc
        if its easy to do, and there is a subset of strings that are ready for translation now, I'd like to post them to start the process
      • Tovok7: what weblate can do depends on the source format of the strings
      • for example XLIFF has lots of features
      • .po some
      • Tovok7
        or to add a warning, that people are welcome to translate, but strings will most likely still change a lot?
      • we have .po
      • _hc
        I'll lok into that and get back to you
      • Tovok7: actually here it is: first, you can just strip out incomplete source strings from the .pot file
      • so the .pot file only includes strings that are useful to start translating
      • you'll need to commit the .pot file to git anyway, so you can easil ymanully edit it after its generated
      • then for more vague ones, you can add "translator comments" to any string: https://www.gnu.org/software/gettext/manual/htm...
      • Tovok7
        We have the .pot files in git already, but somehow I don't see us to manually edit those, especially since this gets overwritten each time we change any of the source strings
      • _hc
        ok, you could either temp disable the auto-generation
      • or script the removal of strings
      • Tovok7
        It is also hard to tell which strings to remote, because they are all good, but we don't know which ones are going to change in the future due to the UX designs or which ones will go away completely
      • *remove
      • _hc
        ok, well, I'll leave that as an exercise for Carrie, Nico, and you
      • :-)
      • just png me when you have something to put on weblate
      • Tovok7
        very simple example: We had 'Create Repository' in our prototype, but it got changed to 'Next' in the UX design and then later changed to 'Create repo'.
      • I'd be happy to put it up now, but maybe a warning or disabling it for now would be nice to translators
      • _hc
        sure, just add the translator comment to all the strings for now
      • ok, who's next!
      • uniq[m]
        me maybe?
      • _hc
        go
      • uniq[m]
        I've finally got yaml based metdadata useable for building apps, also inside a buildserver vm.
      • Apart from that I'm still in the process of refactoring my kvm branch so that is can be merged into master.
      • I also accidentaly stumbled upon a promotion event for NetIdee and tried to get some insights about applying there.
      • I hope we can start using yaml metadata soon. One word of caution thou, I only tested transcribing fdroidclient metadata to yaml and building that particular app.
      • Maybe a mass-test would also be a good idea.
      • Or will we be migrating step-by-step.
      • Tovok7
        indeed, test all apps from fdroiddate beforehand
      • _hc
        you could try using tests/dump_internal_metadata_format.py
      • its meant to do that
      • an easy test to start with would be a round trip txt -> yml -> txt
      • then compare to fdroiddata
      • uniq[m]
        sounds like a solid plan
      • EOF
      • _hc
        thezero pserwylo CiaranG krt[m] any of you up for a report?
      • thezero
        Yes! I'm ready
      • _hc
        go
      • thezero
        This week I've been working on s!271
      • NOTICE: [server] !271: Use Gitlab Pages as mirror instead of Raw - https://gitlab.com/fdroid/fdroidserver/merge_requests/271
      • Now git-mirror use Gitlab Pages (that has a CDN) instead of Raw resources
      • Right now for Github we still use Raw that is behind Fastly CDN
      • In the future maybe we can consider using Github Releases that are on AmazonS3
      • _hc
        thezero: what's next?
      • thezero
        I'm slowly working also on s#256
      • NOTICE: [server] #256: support full build and publish workflow on gitlab… - https://gitlab.com/fdroid/fdroidserver/issues/256
      • fighting with gitlab-ci
      • _hc do you have some Issue I can work on for the next week? :D
      • _hc
        for sure, there is plenty to do :)
      • Tovok7
        this will be awesome, looking forward to nightly f-droid repos
      • _hc
        thezero: do you think you'll finish s#256 this week?
      • NOTICE: [server] #256: support full build and publish workflow on gitlab… - https://gitlab.com/fdroid/fdroidserver/issues/256
      • thezero
        _hc, If I have enought time I think yes, but it's not a promise
      • _hc
        ok, I'm looking through the issues right now
      • thezero: you know jeykll and ruby, right?
      • thezero
        yes
      • Tovok7
        maybe to test this properly, you could also set this up for the fdroid client
      • _hc
        set what up?
      • Tovok7
        sorry I am still at the build and publish on gitlab
      • thezero
        yes Tovok7, my first objective is to make a nightly mirror for fdroidclient
      • _hc
        :-)
      • thezero
        working and easy to deploy
      • _hc
        it'll be really nice to have!
      • thezero: about the fdroid-website, we need to port jekyll-fdroid to use index-v1.json instead of index.xml
      • Tovok7
        maybe even with support for different package_id? applicationIdSuffix .nightly
      • _hc
        seems like there is no issue for it
      • pserwylo: ^^^
      • thezero
        _hc, I will take a look at it
      • _hc
        website#33
      • NOTICE: [website] #33: "Docs" not highlighted when in a Docs page - https://gitlab.com/fdroid/fdroid-website/issues/33
      • oops jekyll-fdroid#33
      • NOTICE: [jekyll-fdroid] #33: generate from index-v1.json instead of index.xml - https://gitlab.com/fdroid/jekyll-fdroid/issues/33
      • I think that's everything for the meeting
      • Tovok7
        another interesting tidbit from io17: google now switched to its own maven repo which should make integrating their support libs into CI and buildserver a lot easier
      • _hc
        oh, for the support libs?
      • Tovok7
        yes, I think only the new stuff ends up there, so v26+
      • Looks like they plan to also add their non-free libraries
      • _hc
        yeah, IO always means newly announced pain points fo rme
      • "look at this new thing that we designed with only the Google point of view in mind!"
      • Tovok7
        Anybody has seen this before?
      • ERROR: JAR signer ANDROID.RSA: JAR signature META-INF/ANDROID.RSA uses digest algorithm 2.16.840.1.101.3.4.2.1 and signature algorithm 1.2.840.113549.1.1.1 which is not supported on API Levels [[17, 17]]
      • _hc
        yeah, it means the signature is using sha256 or sha512. 17 and below only can use MD5 and SHA1 :-/
      • and the APK probably declares minSdk < 18
      • Tovok7
        it is PixelKnot
      • _hc
        or perhaps lterally 17
      • yaeh