Strive to keep that problem statement small, focused on the highest ROI problem.
Break the project down into milestones. That will tell you what to work on, and what not to work on. Set achievable deadlines to keep yourself accountable and laser focused on forward progress.
If a bikeshed question arises, ask whether it can be deferred and easily changed later. If so, defe9r it.
If the bikeshed question cannot be deferred, build consensus with the _key_ stakeholders. Try to keep that set of people small (just those with relevant expertise, and those with authority) and don't worry about pleasing everyone, trying that will be wasteful. Don't worry about the outcome, if its a small part of the overall ROI.
Projects don't have to solve all problems, just effectively improve the status quo.
I like how "I’m not sure if they realize it yet, but Tailscale seems to work extremely well for polycules." is thrown in, as if its usual for any company to know what a "polycule" is.
* someone reacting strongly to this slight difference is "acting like a baby", at least colloquially, but I'm not sure if it meets the author's definition of "active".
* the author using the term "acting like a baby" might get through to people who are sensitive to the difference
I'm glad for the consistency provided by libadwaita and the GNOME HIG.
I don't theme. I hear GNOME are open to theming support being introduced, the right way.
Support for mobile Linux means I can use the same programs on my Librem 5 too!