Re: GitLab minor-reorganization to Community group

2018-09-22 Thread Petr Kovar
On Fri, 14 Sep 2018 10:58:30 +0200
Andre Klapper  wrote:

> [CC'ing gnome-i18n@]
> 
> On Mon, 2018-09-10 at 11:46 -0600, Britt Yazel wrote:
> > There's been an ongoing discussion about reorganizing the "community"
> > top level group from containing both our community partner repos
> > (purism, ubuntu, fedora) as well as a myriad of other repositories.
> > As of right now, the Community top level is somewhat of a catch-all,
> > and we have proposed a fix to split Community into both 'Community'
> > and 'Teams' repositories, with the new 'Teams' top level being where
> > we will organize all of our Foundation teams, i.e. Engagement,
> > Design, Translation, Events, etc.
> [...]
> > https://gitlab.gnome.org/Infrastructure/GitLab/issues/294#note_280162
> 
> Re Translation:
> 
> It's unclear to me where in Gitlab people are supposed to file bug
> reports against a translation in a specific language, which would allow
> translators of a language to get aware of bugs in their translations.
> 
> There is a "8. Translation" label at
> https://gitlab.gnome.org/groups/GNOME/-/labels which allows subscribing
> but does not allow differentiating per language. It should probably be
> renamed to "8. Internationalization" and only be about code which does
> not allow proper translation; the label description could link to
> https://wiki.gnome.org/TranslationProject/DevGuidelines .
> 
> Currently there is an "L10N" product in GNOME Bugzilla with
> subcomponents for each language. Each subcomponent can be watched
> separately by folks interested in that subcomponent (=language).
> 
> Maybe some Gitlab setup / ideas already exists that I'm not aware of?

Can we use https://gitlab.gnome.org/Community/Translation and set up
translation teams as issue labels there?

Alternatively, we could make Community/Translation a group and set up
languages as individual projects within that team. That could give teams
a better control over where and how to submit issues against their language.

My 5¢.

Cheers,
pk
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Retiring app menus - planning for 3.32.0

2018-09-22 Thread Alexandre Franke
On Fri, Sep 21, 2018 at 9:47 PM Bastien Nocera  wrote:
> On Fri, 2018-09-21 at 21:08 +0200, Tomasz Torcz wrote:
> 
> >   Going extra mile to “find” shortcut is never gonna fly.  Years ago,
> > we
> > had a perfect solution for discovering shortcuts  – relevant letters
> > were underlined in the menus.  In some cases underlining appeared
> > only
> > after Alt was pressed, which was less discoverable, but still many
> > times more easy to find than shortcuts popup easter egg.
> >   Please bring back underlined menu items.
>
> Those are not keyboard shortcuts, they're mnemonics, used for
> navigating menus using the keyboard, not launching keyboard shortcuts
> without opening the menu.
>
> Feel free to start a new discussion about those, but they're really not
> the topic.

And also they are actually not gone, so there is no discussion to even
have. Open Nautilus, press F10 for the menu to open, press Alt,
mnemonics are underlined as expected.

-- 
Alexandre Franke
GNOME Hacker
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list