Minutes from the UX/design meeting 2019-OCT-09

[htietze]

Present: Heiko

Tickets

* UI: Typeface and style names are not fully readable in GTK3
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127406
   + enlarge the control by the length of a toolbar button approx.
   => go for it

* Please rename "Show formatting marks" to something correct!
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127954
   + was changed as the function also affects fields
   + not much benefit of renaming anyway
   => WFM

* Font Awesome
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127983
   + out of scope and limited use
   => WFM

* AutoCalculation status is not reported clearly to user
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127937#
   => add on/off icon to the status bar

* HIG AutoCorrect Dialog update
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127773
* Make Border dialog HIG conform
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127807
* HIG Columns Dialog update
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127880
* Make Character Dialog HIG conform
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127927
* Make Cell Format dialog HIG conform
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127934
* Paragraph Dialog reduce tabs
   + https://bugs.documentfoundation.org/show_bug.cgi?id=127947
  => comments at the tickets; in general: go for it

[floeff]

Hello Heiko,

Heiko Tietze wrote:

Present: Heiko

I wonder if that makes so much sense...

Did you ever evaluate having another time/interval/form of these meetings? Were there more participants in the past we can activate?

Florian

[htietze]

The meeting is an offer to the community, work is done on BZ (actually all of the mentioned tickets were discussed in advance of the meeting so my decision was finally covered by the team). The meeting happens bi-weekly on Wednesday or Thursday with a time for people from east and west. Asked repeatedly people in the team and got positive feedback to this way of dealing with UX related topics.
Nevertheless, I'm open for any suggestion.

[floeff]

Hi,

Heiko Tietze wrote:

The meeting is an offer to the community, work is done on BZ (actually all of the mentioned tickets were discussed in advance of the meeting so my decision was finally covered by the team). The meeting happens bi-weekly on Wednesday or Thursday with a time for people from east and west. Asked repeatedly people in the team and got positive feedback to this way of dealing with UX related topics.
Nevertheless, I'm open for any suggestion.

how's the participation rate usually? If it's mostly you, it IMHO doesn't make sense to continue that model. Then either suspend the calls until further notice, or let's collect feedback and ideas how to improve the participation rate.

Reading call minutes with just one participant doesn't look too attractive for people who might want to participate.

All IMHO, so other thoughts welcome, of course

Florian

[franklin]

Hi,

Florian Effenberger 於 2019/10/14 下午8:58 寫道:

Hi,

Heiko Tietze wrote:

The meeting is an offer to the community, work is done on BZ
(actually all of the mentioned tickets were discussed in advance of
the meeting so my decision was finally covered by the team). The
meeting happens bi-weekly on Wednesday or Thursday with a time for
people from east and west. Asked repeatedly people in the team and
got positive feedback to this way of dealing with UX related topics.
Nevertheless, I'm open for any suggestion.

how's the participation rate usually? If it's mostly you, it IMHO
doesn't make sense to continue that model. Then either suspend the
calls until further notice, or let's collect feedback and ideas how to
improve the participation rate.

Reading call minutes with just one participant doesn't look too
attractive for people who might want to participate.

All IMHO, so other thoughts welcome, of course

Florian

I used to talk with Heiko about this meeting.  In my imagination if this
call is open to the community, the topic may ought to be around the
UI/UX instead of bugzilla bugs.  For example I used to collect some
opinions from Taiwanese users and lecturers and discussed with Heiko in
this meeting.  That time was more close to what I think the meeting
should be.  In such meeting Heiko can also explain why we design UI in
that way, not necessary to accept everything users want.

The problem might be how to attract more users coming to share their
experiences and how to avoid same problems being mentioned again and
again.  Time is another issue too.

Same to QA -- maybe we can have a meeting asking users to attend,
talking about bugs they think important and why.

[ilmari]

Franklin Weng kirjoitti 15.10.2019 klo 8.36:

I used to talk with Heiko about this meeting.  In my imagination if this
call is open to the community, the topic may ought to be around the
UI/UX instead of bugzilla bugs.  For example I used to collect some
opinions from Taiwanese users and lecturers and discussed with Heiko in
this meeting.  That time was more close to what I think the meeting
should be.  In such meeting Heiko can also explain why we design UI in
that way, not necessary to accept everything users want.

In the end, if those opinions from Taiwanese users will be taken seriously, they will be turned into Bugzilla reports. Likewise, the Bugzilla reports discussed in the meetings are always the opinions of users from country X.

From what you say, I get the feeling that Heiko should be acting like a secretary for user ideas thrown around. I thought the idea of any team meeting is that contributors coordinate their work.

Same to QA -- maybe we can have a meeting asking users to attend,
talking about bugs they think important and why.

Because TDF does not have a bug fixing budget, there isn't much unrealised potential in focusing on the theoretical importance of specific bugs. I think any experienced QA team member can assess the priority and severity of an issue and they also have the right to change these fields in Bugzilla.

There is no added value in having users explain why their pet bug should be higher priority. Indeed, these types of interactions tend to be a huge waste of time and cause of frustration.

Ilmari

[floeff]

Hi,

I think a meeting with just one person doesn't make much sense, it rather distracts potential contributors, it's not very inviting.

We do have a similar issue with other calls too - the German community call is not really frequented a lot. Infra seems to be getting better, so does marketing, but I remember also for these it was a big struggle.

I wonder what we can do to improve the situation. For the UX calls, did we ever reach out to potential contributors, asking for feedback on the calls, like timing and focus? Did we try different approaches?

Florian