14:02:59 <alebastr[m]> #startmeeting Fedora Sway SIG (2022-09-21)
14:02:59 <zodbot> Meeting started Wed Sep 21 14:02:59 2022 UTC.
14:02:59 <zodbot> This meeting is logged and archived in a public location.
14:02:59 <zodbot> The chair is alebastr[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
14:03:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:03:00 <zodbot> The meeting name has been set to 'fedora_sway_sig_(2022-09-21)'
14:03:16 <alebastr[m]> .hello alebastr
14:03:17 <zodbot> alebastr[m]: alebastr 'Aleksei Bavshin' <alebastr89@gmail.com>
14:03:35 <jkonecny[m]> .hello jkonecny
14:03:36 <zodbot> jkonecny[m]: jkonecny 'Jiří Konečný' <jkonecny@redhat.com>
14:03:58 <jkonecny[m]> and hi to everyone else 🙂
14:04:06 <anthr76[m]> .hello anthr76
14:04:07 <zodbot> anthr76[m]: anthr76 'Anthony Rabbito' <hello@anthonyrabbito.com>
14:06:38 <alebastr[m]> I guess Fale is not here today :)
14:07:15 <alebastr[m]> #topic Planning
14:08:12 <alebastr[m]> let's fill the issue tracker to make sure people always have tasks to grab :)
14:10:53 <alebastr[m]> I wanted to suggest figuring out the consistent theming, but then... GTK4, GTK4+libadwaita, GTK3, Qt6, Qt5, a dozen more toolkits. And none of those could be visually compatible with the other ones.
14:11:34 <alebastr[m]> it's not solved even for workstation
14:12:06 <anthr76[m]> Agreed,I've been lacking on issues.
14:12:49 <anthr76[m]> I don't have a great eye for themeing, but perhaps we can borrow some ideas from i3?
14:13:23 <alebastr[m]> I don't think they do anything in regards to that. Which is fine
14:14:00 <anthr76[m]> I did some lurking not so long ago they seemed to follow of convention of using blue for Fedora which I liked. This was in specific to i3. Are you looking to having themes for possibly at least the major desktop toolkits?
14:14:33 <jkonecny[m]> We can start with sharing our configuration and just decide on what we like the most for the significant parts (like dunst)
14:15:34 * jkonecny[m] uploaded an image: (6KiB) < https://libera.ems.host/_matrix/media/r0/download/fedora.im/8331c6bdd07898cc3306d65f6b71547a82f508dd/2022-09-21T16%3A15%3A15%2C640550202%2B02%3A00.png >
14:16:10 <jkonecny[m]> this is mine
14:16:12 <alebastr[m]> I'm hesitant about blue. What I saw in i3 is panel and borders being significantly different from the window content
14:16:41 <jkonecny[m]> but in general - having an issue in GitLab where we would share our configurations could lead to something
14:16:50 <alebastr[m]> well, pristine sway config doesn't do much better. just a different shade of blue
14:17:56 <alebastr[m]> and btw, i3 sig worked with design sig to get their colorscheme
14:19:13 <anthr76[m]> ah interesting :)
14:19:33 <alebastr[m]> so if we don't feel like pro designers, there's that option. but I haven't considered custom dunst theme so far
14:19:48 <anthr76[m]> I do agree a level of consistency is good
14:20:20 <jkonecny[m]> yes, I was thinking about asking designers around Fedora
14:24:06 <alebastr[m]> The least we can do is to apply qt adwaita theme and do something about waybar style
14:24:29 <anthr76[m]> Agreed
14:24:45 <anthr76[m]> waybar stock config/theme is quite rough around the edges
14:26:39 <jkonecny[m]> honestly, I think we should first create a list of what needs theming and create our own first version
14:26:47 <jkonecny[m]> then ask for help the designers
14:27:45 <anthr76[m]> I'm not opposed. Seems like a tall order to me (off the top of my head) to think of what needs attention and what should be prioritized
14:32:42 <alebastr[m]> ok, so I'll file a general visual style discussion, a ticket for waybar config and stop at that right now
14:32:59 <alebastr[m]> maybe we'll also want to figure out how much we need to customize by default :)
14:34:38 <alebastr[m]> i.e. finding a way to apply Qt/GTK3 themes is nice but do people expect that from us by default? should we ship a settings utility instead?
14:35:03 * alebastr[m] looks at <https://github.com/nwg-piotr/nwg-look>
14:38:31 <anthr76[m]> alebastr[m]: > do people expect that from us by default?
14:38:31 <anthr76[m]> I generally consider it a really nice to have especially showcasing a “fully baked product”, but I must imagine it’s time consuming and there’s possibly? Bigger items to focus on first.
14:38:32 <anthr76[m]> It is something however releasing with the sig instead of adding later is a nice to have as well for the good first impression
14:44:32 <alebastr[m]> ok. let's not block on one topic. I'll finish processing that into an issue text later
14:45:44 <alebastr[m]> Any suggestions for a higher priority tasks?
14:46:11 <pxl_sg[m]> how about the default apps (file manager, audio mixer, ...)
14:49:15 <alebastr[m]> yep, it seems a good idea to ask someone to do a research on that. I mean with trying various options and preparing a write up with pros/cons/general impressions.
14:51:12 <alebastr[m]> I'd say we should do that for all the software, but then we'll never be able to finish :)
14:52:54 <pxl_sg[m]> are there candidates to vote for?
14:53:14 <anthr76[m]> pxl_sg[m]: https://gitlab.com/fedora/sigs/sway/SIG/-/issues/1
14:53:33 <anthr76[m]> I think that issue is our general basis
14:53:38 <alebastr[m]> AFAIK, nobody did a serious analysis on the individual list items :)
14:54:47 <alebastr[m]> so we can pick a template (pros/cons/impressions/what we can do to improve the software) and make it a weekly or bi-weekly task - someone picks an item from the list and does the research
14:55:18 <anthr76[m]> Sure
14:55:54 <anthr76[m]> Overall I think we're pretty solid with software list. It may be able to be improved but it's workable at this stage
14:57:14 <alebastr[m]> ok, so who is going to take the file managers topic and do that to provide an example? :)
14:57:53 <anthr76[m]> I can if no one would like it more then me
14:58:01 <anthr76[m]> s/like/likes/
15:01:13 <alebastr[m]> #action anthr76 to review options for file managers and provide a doc by the next meeting
15:02:59 <alebastr[m]> thanks for agreeing to take that. I was really struggling to come up with a way to move forward software selection ticket without making arbitrary choices.
15:03:38 <anthr76[m]> It is quite tough, but I think this is a good plan
15:06:08 <alebastr[m]> anthr76: by the way, have you seen https://gitlab.com/fedora/ostree/ci-test/-/blob/main/justfile? I'd love to see it merged as it gives us a template for CI with installer images and stuff
15:07:54 <anthr76[m]> I have not. That is interesting
15:08:19 <jkonecny[m]> interesting
15:08:37 <anthr76[m]> Has workstation-ostree-config moved from pagure?
15:08:54 <anthr76[m]> So you would like a similar "justfile" alebastr ?
15:10:12 <alebastr[m]> anthr76[m]: Not yet, but it's being considered. You can ping Timothée for the status.
15:11:16 <alebastr[m]> anthr76: if it's done in the main repo, we'll just need to add Sericea to the list of variants in the justfile
15:12:29 <anthr76[m]> This is the good stuff :) https://gitlab.com/fedora/ostree/ci-test/-/blob/main/justfile#L192-305
15:13:12 <anthr76[m]> Sounds good though I will get with him this week. Happy to see some modern devops-y adoption to that process and adopting ostree-native-containers
15:13:26 <anthr76[m]> Never heard of just but seems like a decent tool
15:13:50 <anthr76[m]> Is there a conversation being had about https://gitlab.com/fedora/ostree somewhere?
15:14:20 <alebastr[m]> https://github.com/fedora-silverblue/issue-tracker/issues/334
15:15:34 <anthr76[m]> Thanks
15:16:48 <anthr76[m]> It looks like https://github.com/nwg-piotr/nwg-look `github.com/visualfc/*` will need to packaged if we want to package nwg-look, but doesn't look too bad FWIW
15:21:24 * alebastr[m] looks at the time
15:24:18 <alebastr[m]> I'm not doing this efficiently enough :(
15:24:18 <alebastr[m]> So I have to suggest to make a brainstorming part continue outside of the meeting slot. Feel free to suggest important action items after the meeting or file directly to the task tracker.
15:24:55 <anthr76[m]> It does go by quite quick.
15:25:35 <anthr76[m]> There was some things I wanted to bring up but my mind is slipping me. waybar config and themeing was one so that was at least covered
15:25:38 <anthr76[m]> Will do though
15:25:51 * anthr76[m] impatiently waits for a new rofi-wayland release
15:27:29 <alebastr[m]> ah. I need to try an improvement for the icon lookup suggested in the comments. and see if I can fix or at least identify a couple of wayland-specific issues I noticed
15:29:04 <alebastr[m]> wanted to do that last week but spent most of the week feeling ill after the booster shot :(
15:29:18 <anthr76[m]> I was quite the same way
15:33:11 <alebastr[m]> #action everyone to suggest tasks they consider important, either in chat or in the issue tracker directly
15:34:10 <alebastr[m]> #topic Open Floor
15:34:57 <alebastr[m]> we've been doing open discussion for last 30 minutes, but I'll still have to ask: anyone have anything important or interesting to discuss?
15:35:38 <anthr76[m]> I haven't figured out what is at fault yet with screen sharing with chrome on Fedora 37. Firefox still works
15:36:15 <anthr76[m]> alebastr[m]: We possible should set some deadlines for ourselves this week to not let Fedora 38 slip past?
15:37:13 <alebastr[m]> milestones for preview builds and for submitting the change?
15:37:25 <anthr76[m]> Yes
15:37:34 <alebastr[m]> s/preview builds/call for public testing of preview builds/
15:38:08 <anthr76[m]> yep submission of kickstart/ostree and sway-config-fedora
15:38:40 <anthr76[m]> I want to write a bit more context about sway-config-fedora in the spin change proposal
15:43:50 * alebastr[m] looks at the draft doc and wishes for another 8 hours in a day
15:44:05 <anthr76[m]> :D
15:44:08 <Fale[m]> what's the best way to collaborate to the change proposal?
15:44:55 <anthr76[m]> I think it should be editable directly?
15:45:18 <anthr76[m]> If not suggestions are welcome on how to deal with it in a user friendly manner
15:45:29 <Fale[m]> yes, should we inline change or do we want to go through a PR-kind of approach?
15:46:26 <anthr76[m]> I think in this state and in-line change with awareness of the change is sufficient to not over complicate things. Though I’m open to ideas
15:46:44 <Fale[m]> oki, I'll work that way then :-)
15:47:15 <anthr76[m]> Thanks :)
15:47:28 <Fale[m]> thank you
15:51:26 <alebastr[m]> I set the change proposal milestone due date to 2 months before the deadline. But we can move it as necessary.
15:53:37 <anthr76[m]> Sounds good.
15:56:24 <jkonecny[m]> sorry for not being so active today. I have my daughter back after 2 weeks so I have my attention elsewhere
16:00:44 <alebastr[m]> that is fine. I think we agreed to continue planning stuff outside of the meeting, because all the good ideas come up way after you needed these :)
16:01:08 <alebastr[m]> so I'm going to close the meeting in 1 min.
16:04:24 <alebastr[m]> #endmeeting