[05:26] <didrocks> good morning
[05:38] <jibel> Good morning
[05:38] <jibel> salut didrocks
[05:38] <didrocks> salut jibel, ça va ?
[05:39] <jibel> didrocks, ça va bien et toi?
[05:41] <didrocks> à la fraiche, ça va :)
[05:42] <jibel> didrocks, ça va pas durer, apparemment il va faire chaud chez toi
[05:44] <didrocks> ouais, "à la fraiche" est relatif, j'ai ouvert à 6h20 et il fait encore 27.6°C à l'intérieur…
[05:45] <didrocks> en plus, vu qu'on fait refaire toute la toiture, le revêtement en dessous est noir sur les toits terrasses
[05:45] <didrocks> ça ne doit pas aider
[05:46] <duflu> Morning didrocks, jibel, pitti
[05:47] <jibel> Morning duflu
[05:50] <jibel> didrocks, I installed yaru-theme-gnome-shell but the theme of the shell didn't change, is there anything else to update?
[05:52] <didrocks> hey duflu
[05:52] <didrocks> jibel: yeah, you need all those changes: bug #1783571
[05:52] <didrocks> but for them to be done, we need the MIR to be acked
[05:53] <didrocks> (I'm running all those branches locally to test them, works)
[06:00] <didrocks> jibel: if you want to temper your system, just modify /usr/share/gnome-shell/modes/ubuntu.json and change to "stylesheetName": "Yaru/gnome-shell.css"
[06:01] <didrocks> jibel: then, alt + f2 and "rt"
[06:01] <didrocks> and for gdm: change the gdm3.css alternative manually to point to: /etc/alternatives/gdm3.css -> /usr/share/gnome-shell/theme/Yaru/gnome-shell.css
[06:06] <jibel> didrocks, new theme \o/ Thanks!
[06:11] <didrocks> jibel: yw! :-)
[06:15] <oSoMoN> good morning desktoppers
[06:18] <didrocks> salut oSoMoN, ça va ?
[06:22] <oSoMoN> salut didrocks, ça va bien, et toi?
[06:27] <didrocks> oSoMoN: chaudement, mais ça va :)
[07:16] <seb128> good morning desktopers
[07:19] <didrocks> salut seb128
[07:19] <seb128> lut didrocks
[07:19] <seb128> didrocks, Trevinho, jibel, you still have cards on the bionic trello board, could you review them and move to the cosmic board/archive/wontfix as fit?
[07:20] <didrocks> seb128: sure
[07:20] <seb128> thx
[07:22] <seb128> didrocks, the one you have in review about the volume cna probably archived since I think the new board already has a card for that
[07:22] <didrocks> yeah, will have a look
[07:24] <seb128> thx
[07:31] <jibel> seb128, done
[07:33] <duflu> Morning seb128
[07:33] <duflu> Oh I was just thinking about those cards this morning
[07:33] <seb128> hey duflu, how are you?
[07:34] <seb128> duflu, how so? why do you still care about the old board? ;)
[07:34] <duflu> seb128, I'm well. Got some artistic therapy today (https://gitlab.gnome.org/GNOME/mutter/merge_requests/168). You?
[07:34] <gitlab-bot> GNOME issue (Merge request) 168 in mutter "clutter: Disable event throttling and deferral [performance]" (comments: 27) [Performance, Opened]
[07:34] <duflu> I care because the project plan never leaves my brain. It's always there even away from work
[07:35] <duflu> Same goes for source code
[07:36] <seb128> I'm good!
[07:38] <duflu> Also, no rain today (unless you count pre-dawn)
[07:39] <didrocks> now that we have Yaru, a reminder to everyone (unsure how we can do that) to whoever update GNOME Shell with styles changes that they need to take care about Yaru as well (3 way merge, we have an upstream/ directory)
[07:44] <seb128> didrocks, I'm not sure what that means but I'm also not likely to be updating gnome-shell ... might be worth documenting somewhere though? (maybe debian/README.Ubuntu?)
[07:44] <seb128> Laney, Trevinho, ^ you are probably the ones likely to update gnome-shell
[07:44] <seb128> oSoMoN, ^ or maybe you
[07:44] <seb128> (since you signed up once for that ;)
[07:45]  * duflu can't quite figure out what "styles changes" in gnome-shell would be
[07:46] <seb128> I guess changes to their css
[07:46] <seb128> which would need to be carried over to our custom shell css
[07:46] <seb128> like new widgets theming or such
[07:47] <duflu> I thought of that but would think many/some CSS changes would not require downstream theme changes
[07:47] <duflu> New widgets, yes
[07:48] <seb128> bottom line is that having what is needed documented is useful :)
[07:48] <duflu> Hopefully people would notice quickly if something looked too Adwaita
[07:49] <didrocks> seb128: does people really red debian/README.Ubuntu or any wiki page when updating? :)
[07:49] <didrocks> can still push some procedure, we'll see
[07:50] <seb128> well, I would expect Treinvh_o or Lane_y do so if they know that something needs to be taken care of
[07:50] <seb128> unless they know what you mean without needing it written down
[07:50] <didrocks> it means that for any GNOME Shell theme breakage, both pacakges to be released in sync
[07:50] <seb128> (I don't, but I'm neither a theme master nor likely to do the update)
[07:50] <didrocks> I guess they know how to do a 3 way merge, but better to document
[07:51] <seb128> it means gnome-shell needs to be updated by someone who understands css enough to know what is a "breakage" in the theme and what is not
[07:51] <seb128> or understand how our theming/override are done enough
[07:52] <didrocks> well, everytime you remove a class or rename one, it's a breakage
[07:52] <didrocks> as easy :)
[07:52] <seb128> what if they add color definition?
[07:52] <didrocks> as yaru will theme that class
[07:52] <seb128> or change a color?
[07:52] <seb128> do we need to check if we need a color tweak on our side as well?
[07:52] <didrocks> addition isn't a breakage, but still needs to be reported
[07:52] <didrocks> basically, any changes they do in their sass should be reported (at least diffed against)
[07:53] <seb128> also can whoever update the shell fix yaru?
[07:53] <didrocks> they should MP, it's the process
[07:53] <didrocks> and anyone can MP
[07:53] <seb128> or do we need to go through the communitheme team?
[07:53] <didrocks> I guess we could get our team having write powers
[07:53] <didrocks> but still, better to MP for having a reread
[07:53] <seb128> the community is active enough that it shouldn't be problematic atm
[07:54]  * duflu has only ever tried fixing the sass once... https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/90 ... I hope upstream eventually fixes that
[07:54] <gitlab-bot> GNOME issue (Merge request) 90 in gnome-shell "Display full application names under their icons" (comments: 9) [Closed]
[07:54] <didrocks> yeah, I don't see right now that being an issue
[07:54] <didrocks> but still, having more people with commit rights to the repo would be good
[07:54] <seb128> right
[07:54] <didrocks> pushing release tags and such
[07:54] <seb128> let's hope gnome-shell doesn't change their css too often :p
[07:55] <didrocks> yeah…
[07:55] <duflu> Hmm, maybe we want that patch in Ubuntu
[07:57] <seb128> duflu, they said https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/58 was a better way to go
[07:57] <gitlab-bot> GNOME issue (Merge request) 58 in gnome-shell "WIP: Fix long application names being truncated" (comments: 4) [Opened]
[07:57] <duflu> seb128, also it got put on hold for months. Meanwhile my tiny patch works perfectly and is finished
[07:59] <seb128> Trevinho, ^ do you have an opinion on that?
[08:06] <Laney> oops moin
[08:06] <duflu> Morning Laney
[08:06] <Laney> seb128: I'm not going to be doing a theme update inside the shell I don't think
[08:06] <Laney> Trevinho: It would be good not to wait weeks before getting on a new series
[08:07] <Laney> we are starting to do 3.29 now
[08:07] <Laney> hey duflu
[08:09] <andyrock> seb128: how can I help with the 3.29 update?
[08:14] <seb128> hey Laney
[08:15] <duflu> 18.04 emptied
[08:15] <seb128> andyrock, look on http://people.canonical.com/~platform/desktop/versions.html for something you think you could update and work on updating the packaging (https://wiki.ubuntu.com/DesktopTeam/git is worth reading for GNOME components, they mostly use that workflow now)
[08:16] <seb128> Laney, well, the point is that whoever does a gnome-shell update should make sure it doesn't regress our theming or we ship something buggy to our users
[08:16] <Laney> I understand
[08:17] <seb128> so if it's buggy whoever is doing the update should update the theme shell css to reflect the upstream changes
[08:17] <Laney> Firstly I'm not confident that I wouldn't make it more buggy by trying to do an update with poor knowledge of the procedure.
[08:17] <Laney> Secondly I think the procedure itself is not ideal.
[08:17] <andyrock> kk thanks
[08:17] <Laney> I thought we had a line of work to try to improve this situation
[08:17] <seb128> Didier is documenting it
[08:18] <seb128> that should address your first point
[08:18] <Laney> I know that the second one is a bit tangential
[08:19] <Laney> but it exiting makes updating gnome-shell to be burdensome
[08:20] <seb128> on improving the procedure itself, I think we are doing what we think is best/easier now with the new theme (using a scss derivated from the upstream one)
[08:21] <seb128> (out of not having a custom theme)
[08:22] <seb128> but yeah, it makes updating gnome-shell less trivial :/
[08:22] <seb128> I don't have a good answer to that today
[08:23] <seb128> andyrock, those in sync with Debian it makes sense to update in Debian/salsa with a merge request there
[08:24] <seb128> Laney, I looked at version for unstable, took me a bit to remember what we were doing but we don't usually track unstable GNOME as a common target
[08:25] <seb128> Laney, there is a light green section between yellow and green which is "New unstable version available" which lists components that are uptodate on the stable serie but have an unstable update available
[08:25] <Laney> ok
[08:26] <didrocks> seb128: Laney: tell me if that makes sense: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-shell/tree/debian/README.Ubuntu
[08:26] <Laney> you have to look in the yellow section too, those are "needs merge" ones that might have a version to update for
[08:27]  * duflu is guessing Trevinho is delayed now, since the all nighter on Tuesday
[08:27] <duflu> Or maybe that's just normal, from what I hear about Spanish life
[08:28] <seb128> Laney, if you want to track a component on 3.29 specifically (e.g gnome-shell) we usually update the line for that one, e.g https://bazaar.launchpad.net/~ubuntu-desktop/ubuntu-desktop-versions/trunk/revision/1642
[08:29] <Laney> didrocks: reading
[08:29] <Laney> "is the source of Yaru GNOME Shell theme" is a confusing statement to me
[08:29] <Laney> s/source/upstream/?
[08:30] <didrocks> Laney: feel free to ammend/MP :)
[08:30] <Laney> :/
[08:30] <didrocks> ?
[08:30]  * Laney feels trapped
[08:31] <seb128> don't
[08:31] <seb128> it's probably easier to direct edit/commit your changes that proxy through Didier
[08:31] <Laney> I thought I was being asked for feedback now I have to go make changes myself
[08:31] <didrocks> shrugh
[08:31] <Laney> sorry, it's all new to me
[08:31] <didrocks> not that different with what you always do for wiki pages when asking for rereading…
[08:31] <didrocks> anyway
[08:31] <seb128> if it's just english/wording it's probably easier to just fix
[08:32] <seb128> if that's the content which is not clear that's probably worth asking
[08:32] <didrocks> right
[08:33]  * Laney thought that was the second case
[08:33] <seb128> My understanding of that sentence is that the yaru shell theme is derivated from that directory
[08:33] <Laney> it made me think that there is a directory inside gnome-shell called data/theme which contains yaru's gnome shell theme
[08:33] <seb128> so any change to the master should be reflected to the copy
[08:33] <seb128> right, wording can probably be improved
[08:34] <didrocks> what seb128 told is correct, indeed.
[08:34] <seb128> "The upstream GNOME Shell `data/theme/` directory is used as a based for our Yaru GNOME Shell theme so any change made upstream needs to be reflected in our derivated version"
[08:34] <seb128> or something around those lines?
[08:35] <didrocks> sounds good to me
[08:36] <Laney> basis* derivative* ;-)
[08:36] <Laney> yes that makes sense, thx!
[08:36] <seb128> Laney, ^ sounds better to you? I'm happy to commit those changes (unless you want to de-frenglish and write an improved version, which is fine too)
[08:36] <seb128> yw
[08:37] <seb128> k, let me commit with your fixes
[08:37] <Laney> and then the rest is three way merge these things, then update upstream/
[08:38] <seb128> right
[08:39] <didrocks> right
[08:39] <didrocks> I prefer that we keep the upstream/ directory as it's easier to do the 3 way merge
[08:40] <didrocks> rather than writing down "this is the last version we merged with", and have to download the old source pacakages in addition to the new one
[08:40] <seb128> it's also nice to be able to diff the base and derivative version locally
[08:40] <seb128> or to know what base has been used
[08:40] <seb128> didrocks, Laney, wording tweaks commited/pushed
[08:40] <Laney> thx
[08:41] <Laney> well done for using git :P
[08:41] <seb128> np!
[08:41] <seb128> haha
[08:41] <didrocks> thanks!
[08:41] <seb128> I got tricked :p
[08:48] <seb128> andyrock, if you want to look at some easy updates, file-roller totem totem-pl-parser gnome-calculator are probably in that category, also click on the "Open Bug..." and file a bug to record you are working on an update so we don't dup work
[08:48] <seb128> (that opens a normal bug but with the tag "upgrade-software-version" which is used to list the bug is the "status" column of http://people.canonical.com/~platform/desktop/versions.html)
[08:50] <Laney> I'm going to change the GNOME_STABLE_SERIES to GNOME_UNSTABLE_SERIES for a lot of things I think
[08:50] <Laney> sound good?
[08:52] <Laney> some of them have a regex matching stable things though
[08:53] <Laney> oh right you should just delete the version bit I think
[08:54] <seb128> yeah, I'm a bit unsure if we shouldn't just change the GNOME_STABLE_SERIES to 3.29 if we plan to track 3.29 for most component
[08:54] <seb128> I guess there is no best/right way
[08:54] <seb128> both get the job done and have some small drawbacks
[08:54] <seb128> so yeah, just change the ones you want :)
[08:55] <Laney> guess it's easy to revert later on
[08:56] <seb128> right
[08:57] <seb128> Laney, pull before commiting changes, I did a trivial commit to fix the boost version
[09:03] <Laney> k
[09:03] <Laney> why is totem pinned to 3.26?
[09:09]  * duflu should know but cannot remember
[09:10] <duflu> Laney, possibly because until recently we wanted SSDs. Now we use CSD I see no reason
[09:12] <duflu> Also LIM, maybe
[09:12] <duflu> Also people forget sometimes
[09:31] <seb128> Laney, that's the newest?
[09:31] <seb128> I don't remember :/
[09:32] <Laney> yeah I think it's probably that they just didn't do a 3.28 and all the 3.26 stuff got that version
[09:56] <Trevinho> Morning
[09:57] <oSoMoN> good morning Trevinho
[10:05] <duflu> Morning Trevinho, willcooke
[10:07] <Trevinho> Hi duflu and oSoMoN
[10:08]  * Trevinho noted all the gnome shell changes... 
[10:08] <Trevinho> For theme I mean.
[10:09] <Trevinho> seb128: nautilus on cosmic, what want to do?
[10:11] <Trevinho> andyrock: most of branches, updating salsa merging the tag version and pq rebase is normally enough... I Hadded something in the wiki for that some weeks ago. But is easy.
[10:11] <willcooke> ahoy duflu Trevinho
[10:20] <Laney> hi Trevinho willcooke
[10:21] <Laney> Trevinho: need to resolve the desktop icon situation still afaik
[10:22] <andyrock> Trevinho: kk
[11:00] <Trevinho> Laney: ah, right... If want me to look into the proposition for shell let me know
[11:06] <Laney> probably one for seb128
[11:19] <seb128> Trevinho, what do you mean nautilus on cosmic? I though Didier uploaded your update on friday?
[11:20] <Trevinho> seb128: version...
[11:20] <seb128> Trevinho, we stay on what we have
[11:20] <Trevinho> seb128: also I've pushed a cosmic fix while bionic is waiting
[11:20] <seb128> k
[11:21] <Laney> being stuck on 3.26 I thought was the question
[11:21] <Trevinho> Laney: yes... And answered we do :-)
[11:21] <Laney> staying
[11:21] <Laney> ?
[11:22] <Trevinho> So it seems, no?
[11:22] <Laney> dunno, I missed that discussion but ok
[11:22] <Trevinho> 13:20:41 <seb-128> Trevinho, we stay on what we have
[11:22] <Trevinho> Not much discussion
[11:22] <Laney> yeah I saw the line but it sounds like a decision that I didn't know about
[11:22] <seb128> well the situation from previous cycle didn't change
[11:23] <seb128> there is some resumed interest for the desktop icon extension and Didier is going to help a bit upstream on that
[11:23] <seb128> so hopefully it unblocks us
[11:23] <seb128> but it's not today
[11:23] <seb128> maybe still this cycle, let's see
[11:24] <Laney> Trevinho just offered to help so I'm a bit confused about let's see
[11:24] <Laney> but ok
[11:25] <seb128> did he? when/where?
[11:25] <Laney> 26/07 12:00:50 <Trevinho> Laney: ah, right... If want me to look into the proposition for shell let me know
[11:25] <Laney> at least that's what that says to me
[11:25] <seb128> " the proposition for shell"?
[11:25] <seb128> I couldn't parse what that meant
[11:26] <Laney> thought it meant an extension
[11:26] <Laney> but still, we can ask...
[11:26] <seb128> yeah
[11:26] <seb128> Trevinho, what do you mean by "proposition for shell"?
[11:26] <seb128> also Trevinho is way behind on the work he commited to do this cycle
[11:27] <seb128> Trevinho, you signed up for getting us gs-connect by default, feature freeze is coming and it looks like you didn't even started looking at that so please don't commit for more work
[11:27] <Laney> that is more like what I meant by asking you
[11:27] <seb128> right
[11:28] <seb128> I think that at this point Trevinho has overcommited himself for the cycle already, so no more things on his list :)
[11:28] <seb128> and Didier is helping upstream on the desktop icons thing
[11:28] <seb128> so hopefully that's on its way to resolution
[11:29] <seb128> meanwhile there are enough other updates to do :)
[11:29] <Laney> I'm aware
[11:29] <Laney> this is one of the few that is blocked on some work happening
[11:29] <seb128> also Carlos was planning to port to GTK4 this cycle
[11:29] <Trevinho> seb128: I was looking at it, but I saw didier started. And you know I wish I could have avoided all this maintenance work on packaging itself, but as nobody else does it I had to do it
[11:30] <seb128> but I think they might have rolled back from that plan
[11:30] <seb128> Trevinho, what maintenance/packaging work?
[11:31] <Trevinho> seb128: well all the mutter, shell and nautilus releases...
[11:31] <seb128> you do a good maintainer for those, don't be shy :)
[11:32] <seb128> what did cost you time is the month you spent on the git import script...
[11:32] <seb128> not those 3 updates
[11:33] <Trevinho> Naaa that was over in a week or so. But all the rest of the time has been spent in back and forth with upstream reviews, backport and such.. Context switch make me loose time also
[11:34] <seb128> you are the one deciding of how you organize your time and when/how you context switch, the items you worked on had been on your list since the start of the cycle
[11:34] <Laney> is there a card for the extension thing?
[11:34] <Laney> would like to spy on that one ;-)
[11:35] <seb128> Laney, https://trello.com/c/oD8wcMJO/97-desktop-icons-next-generation
[11:35] <Laney> thx!
[11:35] <seb128> yw!
[11:35] <Laney> ah, proposed, I didn't look in that lane
[12:31] <Laney> I was like "oh cool we can drop all this -schemas stuff" for g-s-d
[12:31] <Laney> except we can't eh :(
[12:41] <seb128> u-s-d still using them?
[12:41] <Laney> guess so
[12:41] <Laney> didn't actually check tbh
[12:42] <Laney> don't see any bigger updates in the changelog at least
[12:42] <seb128> andyrock, sounds like smcv is waking up to do some updates as well today and did update file-roller there, probably makes our update easier
[12:43] <andyrock> seb128: yeah but not 3.29.1
[12:43] <seb128> ah right
[12:43] <Laney> if we decided to drop those desktop files we can probably get that syncable
[12:43] <seb128> good point :)
[12:43] <Laney> I'll sponsor things like that to experimental
[12:43] <Laney> if you want
[12:43] <seb128> Laney, is Debian doing 3.29 yet?
[12:43] <seb128> andyrock, ^
[12:43] <Laney> if debian is me
[12:43] <Laney> then yes
[12:43] <Laney> mutter and gnome-shell are in already
[12:44] <Laney> and gtk
[12:44] <Laney> was harassing people for a glib release
[12:44] <Laney> still some kinks there to work out
[12:47] <Laney> trying to do the bigger bits first
[12:47] <Laney> but I'm not sure what to upload to cosmic before gnome-shell itself is ready
[12:50] <seb128> well maybe g-s-d needs to go together if some of dbus api between them changed but otherwise the other components should be pretty independant
[12:50] <seb128> unless systemd user session bits land and create depends with gdm/gnome-session? I didn't check what was happening on that front
[12:50] <Laney> nope
[12:50] <Laney> apps are probably OK, speaking of core session components
[12:53] <seb128> right
[13:04] <andyrock> Laney, seb128: I'm still confused. Should I try to work on salsa or not for file-roller?
[13:04] <andyrock> if yes in debian unstable or experimental?
[13:05] <seb128> L_aney said he would sponsor the 3.29 version to debian experimental, so probably makes sense to do the update there
[13:06] <andyrock> kk
[13:06] <seb128> we can drop the compat .desktop so maybe that one can even by synced in Ubuntu then
[13:12] <Laney> andyrock: you need a commit like https://salsa.debian.org/gnome-team/mutter/commit/3bf7b25a4f2e2fd3cfc1c2f0f3725a86835f2573 and https://salsa.debian.org/gnome-team/mutter/commit/46dc4564dd1e41f24149089b860359f86ea5b96c to move unstable to experimental
[13:13] <Laney> ignore the commit message on the last one, I messed that up 😐
[13:14] <Laney> ah you might want to join #debian-gnome too
[14:39] <Laney> OMG RAIN
[14:41] <ogra> send it over !!!
[14:42] <chrisccoulson> Laney, you have rain?
[14:42] <Laney> yep
[14:42] <chrisccoulson> Laney, i hate you
[14:42] <chrisccoulson> :P
[14:42] <chrisccoulson> I hope you're dancing in it
[14:42] <Laney> probably not going to last
[14:47] <Laney> finished
[14:47] <ogra> pfft
[15:06] <Laney> all dry again now
[15:23] <seb128> no rain here today and it's > 31°C now at my desk :/
[15:23] <seb128> I'm melting and so is my laptop
[15:23] <seb128> time for some gelatto, bbiab
[15:36] <Laney> what blocked d-conf -> dconf last cycle?
[15:36] <Laney> anybody remember?
[16:34] <chrisccoulson_> Laney, according to the openweather extension, there is a thunderstorm and heavy rain outside here
[16:34] <chrisccoulson_> but it's lying :(
[16:35] <Laney> :(((((((((((((
[16:35] <Laney> https://www.bbc.co.uk/weather/ng5
[16:35] <Laney> this is looking good
[16:53] <andyrock> Laney: I guess that I need to open MP in salsa right?
[16:54] <andyrock> the problem is that I cannot open an MP against an existent branch
[16:54] <andyrock> e.g. file-roller has no debian/experimental branch
[16:54] <andyrock> how does it work in this case?
[16:59] <Laney> not sure what gitlab does in this case
[16:59] <Laney> maybe you could go to #debian-gnome and put it in RFS: in the topic
[17:00] <willcooke> chrisccoulson, same here.  Supposed to be thunder, but it's just hot and sunny
[18:12] <seb128> Laney, dconf we never sorted out the armhf autopkgtest issue (that's in the trello board still if you are interested)
[19:36] <willcooke> night all