We should have a sprint for this goal in the next 12 months. Let's figure out the following:
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Wontfix | adam | T11790 goal sprints | ||
| Wontfix | lydia | T11792 Goal sprint: Wayland |
My two sense about it :
Sprint topic :
Meetings, trainings and teaching each other, work planning, experience sharing, bug triaging/firefighting eventually
Meets and discussion are far more efficient than remote/asynchronous.
When:
My guess would be during Q1 or Q2 2020 during late Plasma 5.18 cycle early 5.19 cycle
Collocation Sprint:
Definitely makes sense, since this is a cross-team effort.
Collocated with Plasma and KWin Sprint would make the most sense but App Sprint such as Krita or KdeEnlive might make sense.
People needed:
KWin people, Plasma people.
Maybe Some app maintainers, in particular the ones that feel more work is needed to complete their Wayland support (krita).
Maybe invite some non-KDE people, like Qt people and QtWayland maintainer, libinput maintainer/contributor if possible.
Any opinion regarding this @davidedmundson @romangg ?
I wouldn't be so sure that co-locating with Plasma makes unequivocally sense. Both @davidedmundson @romangg as well as other people like me have several responsibilities within the project that will definitely be a distraction to the goal. Co-locating with Krita, if they need need ad-hoc work would make sense. Doing it around an upstream conference (QtCS, XDC) would also make a lot of sense.