- Name/IRC nick: nephros
- Topic: Community Tasks Board
- Approx. time needed: 10min, plus maybe general discussion
- Substitute (optional): n/a
- Some details about the topic:
With Jolla staff (as has been repeatedly said) being busy with both admin things like fulfilling/managing orders, as well as development and adaptation work, all while Sailfish OS is an open platform with an active open source contribution model. We develop it together with our customers and developer community.
How about you guys publish a list of things that the community can pick up and submit contributions about.
The idea would be something akin to a (or maybe actual) “Kanban” board Backlog column published by Jolla, that aspiring community contributors can look at and pick up tasks from.
Kind of a “reverse channel” from Jolla to the community (as opposed to bug reports, feature requests etc. whic go the other way)
A possibility for the Jolla team to potentially get work done externally, with some control over what is deemed “important”, or “important, but not now”, or “meh, one-banana-problem, lets find some monkey”.
Things that come to mind:
- “Janitorial” work on the Sailfish OS · GitHub repos: cleaning up .spec files, fixing packaging things, retiring old repos/packages that may not be used any more
- updating base open source packages
- other things which are on the Jolla Team’s backlog but do not necessarily need to be performed by the Jolla team
Also important: It should be understood that nothing about publishing such a list would be interpreted as a commitment or non-commitment of Jolla to anything, not as a road map, or anything else that reflects internal workings at Jolla.
It is simply a list of things staff thinks community could help with.
Personal note: in the discussion about this, please do not focus on potential tools, or actual tasks - instead focus on the “process” - on the how, not the what.
Be aware of how bikeshedding works.