| 9 Jul 2020 |
 _hc | lol, yeah. test please! I updated three devices, so far so good | 14:41:54 |
| _hc | cdesai: Bubu jochensp izzy uniq Dominik Mathijs meeting day 🎉 | 14:51:01 |
 izzy | Ugh… | 14:51:52 |
 Dominik | Heyho, not much to say from my side. Was working on some features in the whitelabel version. Will get back to the AndroidX pull request next week | 14:52:00 |
| _hc | fdoridclient 1.9 is available, please test so we can mark as current version | 14:52:08 |
| izzy | Short summary from me <<EOF | 14:52:29 |
| izzy | Filing RFPs that build directly as MRs works fine so far, most of my filings have been merged. | 14:53:08 |
| izzy | Still looking for your (packagers) input to my issue on data for what checks you usually apply before doing the final merge, so I can compile a list of must-haves, nice-to-haves, and icings-on-the-cake. | 14:54:13 |
 jochensp | I'm vocation, not sure if I find time to look into the timestamp issue | 14:54:41 |
| izzy | Until that list is compiled, I still refrain from merging. If it's there I need to see what device I can use for testing ;) Don't want to use my two work/personal devices for "all kind of apps". | 14:55:12 |
| izzy | Just installed v1.9 client on my Oreo device. First impression is great, will watch it at least for a week before saying Yay-or-Nay :) | 14:55:54 |
| izzy | EOF | 14:55:56 |
| _hc | IMHO, those must-haves can be implemented as CI checks. I think we're not too far off from having the CI job status and issuebot comment covering the known issues.
otherwise, I'm working with redplanet to overall the issuebot UI, e.g. what it posts to comments. we'd love feedback and ideas. | 14:56:03 |
| izzy | Yeah, the "tech part" is great already! When all the checks are implemented, it will need some "visual polish". But having those was what enabled me to start filing MRs at all, so a big thanks! | 14:57:18 |
| izzy | One "must have" that certainly cannot be automated is a "human check". Not just that the app starts without crashing, does no "weird stuff" in the background, and contains no "interesting strings" – but also whether it does what it advertises, and "makes sense" (not sure how to describe that). | 14:59:20 |
| izzy | So maybe my first sum-up should happen in the issue with a ping to you two, so you can mark check-boxes of what is already covered by CI? | 15:00:06 |
| izzy | _hc: ^^ | 15:00:48 |
| _hc | right. I think that matches our conception of this issuebot workflow. the idea is to present the info to the human to make the human decisions, while letting the bot do the things it can do best | 15:14:53 |
|  apol joined the room. | 17:01:48 |
|  huss_ joined the room. | 17:01:53 |
|  infertux left the room. | 18:08:35 |
|  tjg1 left the room. | 18:08:37 |
| 10 Jul 2020 |
|  grote joined the room. | 13:11:34 |
| 12 Jul 2020 |
| izzy | Anybody else not seeing any emoticons when trying to add a "reaction" on a GitLab comment – or is it just me? They disappeared about 2 days ago for me. | 12:32:53 |
 wb9688 | I see the emojis, but it's using Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, or Noto Color Emoji, so if you're not on Windows or macOS, you need to install the Noto Color Emoji font | 12:42:17 |
| izzy | wb9688: thanks! Did they switch that recently? Funny idea to play against us Linux folks. I always thought websites are not suppost to require specific software to be used (apart from a browser, of course). I see they defined a "fallback", but not even that seems to work. Did they forget to test? :p | 16:59:30 |
| izzy | No chance. None of the Noto Color Emoji TTF I downloaded is accepted by my system. "Cannot be displayed". Cross-checked, works fine for other fonts. Well, that happens when Google gets its fingers in… | 17:41:32 |
| izzy | …one needs to do a dist-upgrade to view a f***ing website. Wow. | 17:44:10 |
 Bubu | izzy: pacman -S noto-fonts-emoji ;-) | 18:00:34 |
| Bubu | though I have the twemoji package installed and get emojis in gitlab just fine | 18:01:08 |
