More active dev work is slowly starting again and Nick’s looking for the best small coding tasks. Those can be found both on Gihub and here in the forum, so in our last weekly meeting we had some reflections and questions about our workflow.
It seemed reasonable that a bug would end up directly on Github, since it’s quite straightforward already how something is supposed to work, without the need of further exploration or feedback other than actual testing and reproducing the bug.
On the other, small improvements and ideas for new features are important things to try to engage the community in, by means of feedback, discussion, sketches, etc. That’s what the forum and Karrot group is for. Small improvements can be quite significant to how people experience Karrot, how they think it is easy and pleasurable to use. New features require quite a lot of exploration most of the times…
Let’s try to explore Kanban boards here, review our tags on Github and try to integrate the guidelines for contributors and whatever kind of onboarding we have into this new workflow that is taking shape. We can think of something along these line:
Interested in coding only?: take a look at our github issues for bugs and anything else that is ready for development, or dive deeper into our community forum for more complex tasks
Want to give feedback, suggest ideas for new features, (re-)design something?: look at our community forum
Now let’s see how we can organise things with a Kanban board, if we use some categories, sub-categories or tags. My guess now is to use categories view for the level of progress, and using tags for the type of feature.
Still a work in progress, but one main question I have right now is:
How do we sort things out?
There many important variables to consider, and here are the ones I thought about so far…
- level of complexity (from a coding perspective only?)
- level of progress
- needs one or more dedicated design sessions, needs more discussion/feedback, or ready for development
- what type of feature is it related to (e.g. about activities, or applications, chats, etc)
- maybe the three categories we used before: dreaming, conceptualizing and getting things done