What did go well with the action bar proposal?

Hello all,

In a previous blog post I asked feedback about adding an always visible action bar to Nautilus that integrated the floating bar info too.

It was very useful, as most of you confirmed our suspicions that it was too heavy, so we researched for a better solution for the goals we had: Make actions more discoverable, have good touch support and better pointer accessibility (not being able to access actions in list view anyone?).

Multiple people participated with constructive, well written and excellent feedback. Even more, they even provided high quality mock ups with ideas, to the point that I’m genuinely surprised.

So the goal of this post is for you to help me figure out what went well to have this constructive interaction! I have several factors in mind, could you share your thoughts?:

  • Was it because of using GitLab and its inline images support?
  • Was it the easy installation and testing of the work in progress with Flatpak?
  • Was it the exposure of the idea by being well written and formalized with goals, possible solutions, relevant art, etc?
  • Was the outreach for feedback early in the cycle with a blog post?
  • Was just the topic? i.e. you won’t feel as engaged with other ideas

Feel free to pick several of them or add more factors if those were the important ones for you (try to write down which one was the most important). I’m looking forward to repeat what was good for you all to participate in our next ideas. You can share your thoughts here in a comment or contacting me on irc.gnome.org in #gnome-hackers or #nautilus as csoriano.


PD: Feel free to try the solution we came up with and share your feedback & ideas in irc or in the issue.


6 thoughts on “What did go well with the action bar proposal?

  1. I would say it’s a mix between the four first points.
    1. Sharing ideas without having to rely on external image hosting services eases the process of sharing such ideas.
    2. Also important, specially in a world where we have such a variety in package distributions; Flatpak plays an essential role allowing anyone to install and test experimental versions of software.
    3. It’s easier to solve something when you know what you need to solve. Communication is key in community-driven projects.
    4. This is quite important in my opinion. In some projects one must dig really deep (mailing lists, whatever) to understand what’s going on in the shadows; transparency is a must.

  2. For me, it’s all of the things you mentioned. It was a textbook example of how to introduce and iterate on a major change – helped by the new supporting technology!

    1. Nice, good to know! Also, I’m interested about the “following up” part for feedback. For example in your case, what would be the best to follow up on your concerns & motivations?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: