About the Feedback and ideas category

Feedback and ideas
1

This is a place to try and keep organised all the feedback we get on Karrot for fixing and improving features, as well as the suggestions and ideas for new features :bulb:.

If you want to give a feedback and suggestion you’re welcome to do it here, but you’ll probably get a bigger response in our Karrot group :karrot: and then later we try to find a place (and maybe some level of priority) for your feedback in this category.

If you want to report bugs :bug: you can also do it there on the group, on Github or on another category of this forum: Issues - Karrot Community

2 Likes
2

So how to start?! We’ve got tons of feedback and many overlapping or about the same thing.

here’s a suggestion by @nicksellen on a Karrot thread:

@tomek sent a nice list of changes that would be very useful for them, I wonder if we can collect this kind of thing from other groups, then somehow prioritise the work? Maybe even people in the different groups can talk to each other too … and with some karrot people to guide the process?

Even though I don’t have much dev capacity, if it’s possible to work out really useful small changes, with well specified detail, that makes it much more possible. Maybe we need a template/process for this…

So perhaps have different categories of size… And details about who is impacted, the user story part. That kind of thing. Would be lovely!

I like the suggestion and that is what the category on this forum can be used for. Let’s try to figure out a nice template… Maybe having a topic to dump all the feedback in its orginal raw format, then creating new topics - maybe two or more groups come up with a feedback on the same feature - with a better presentation of the information, like the following:

  • user story: who requested something, which groups get impacted and how
  • level of complexity: is it well-detailed and simple, or is it a more complex idea that requires further thought, mockups and maybe even a design process?
  • actionable outcomes: is it ready for implementation? Or do we need more information from other groups for example? Do we book a session to discuss it more and figure out other details? What’s next?
2 Likes
3

I just started slowly looking at some of the feedback and try to write posts to organise them. My first question was whether we should lump together some of the ideas on the same topic, or whether we should create different posts for each even if they’re slightly different. Hard to tell! I took the place feature as an example and put two ideas together in one topic: Improve places page and favorite places

But there are other topics created by @hwojcik , also about places, which seemed not worth mixing together with others. Maybe we can start working better with tags or subcategories in the future where we can see the connection between these posts.

In the upcoming weeks I’ll have more time to start working on organising all these topics! :slight_smile:

4

More active dev work is slowly starting again :tada: 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 :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