From: Eric Wong <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: Son Luong Ngoc <email@example.com>, Jonathan Nieder <firstname.lastname@example.org>, email@example.com, Raxel Gutierrez <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Junio C Hamano <email@example.com>, Taylor Blau <firstname.lastname@example.org>, Emily Shaffer <email@example.com> Subject: Re: Pain points in Git's patch flow Date: Wed, 28 Apr 2021 07:21:38 +0000 [thread overview] Message-ID: <20210428072138.GB13114@dcvr> (raw) In-Reply-To: <firstname.lastname@example.org> Ævar Arnfjörð Bjarmason <email@example.com> wrote: > On Mon, Apr 19 2021, Eric Wong wrote: > > Son Luong Ngoc <firstname.lastname@example.org> wrote: > >> [...] > >> 3. Isssue with archive: > >> > >> - I don't find the ML archive trivial for new comers. It took me a bit > >> of time to realize: 'Oh if I scroll to bottom and find the "Thread > >> overview" then I can navigate a mailing thread a lot easier'. > > > > (I'm the maintainer of public-inbox, the archival software you > > seem to be referring to). > > > > I'm not sure how to make "Thread overview" easier to find > > without cluttering the display near the top. Maybe I'll try > > aria labels in the Subject: link... > > I'd say the bare-bones style of it is probably jarring to most users > today. I had to check if the site even had any CSS at all. > > I.e. I think a more intuitive UI to users today would probably be some > collapsible side-bar on the left of the screen, which would have a > threaded view. The "Archives are clonable" would probably belong in some > "help" tab in such a UI. The plan is to support read-only JMAP, so it's a stable API that users can build their own displays on top of (of course, NNTP and IMAP support already exists). I can't make drastic UI changes such as a sidebar without breaking things for users who like the current UI. I only know about GNOME3 and Digg because they made drastic UI changes that angered their existing userbase. The current UI is designed to for a terminal with w3m|lynx since it's the lowest common denominator. Graphics drivers/stacks seem to be most frequently broken thing on GNU/Linux systems, so it's important users can find patches/configs/help easily with a text-only browser in order to get graphics working.
next prev parent reply other threads:[~2021-04-28 7:21 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-14 6:13 Jonathan Nieder 2021-04-14 7:22 ` Bagas Sanjaya 2021-04-14 8:02 ` Junio C Hamano 2021-04-14 21:42 ` Junio C Hamano 2021-04-15 8:49 ` Denton Liu 2021-04-15 6:06 ` Junio C Hamano 2021-04-15 15:45 ` Son Luong Ngoc 2021-04-19 2:57 ` Eric Wong 2021-04-19 13:35 ` Theodore Ts'o 2021-04-21 10:19 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:21 ` Eric Wong [this message] 2021-04-28 7:05 ` Eric Wong 2021-04-15 18:25 ` Atharva Raykar 2021-04-16 19:50 ` Junio C Hamano 2021-04-16 20:25 ` Junio C Hamano 2021-05-02 5:35 ` ZheNing Hu 2021-04-18 8:29 ` Sebastian Schuberth 2021-04-18 20:54 ` Ævar Arnfjörð Bjarmason 2021-04-19 2:58 ` Eric Wong 2021-04-19 5:54 ` Sebastian Schuberth 2021-04-19 6:04 ` Sebastian Schuberth 2021-04-19 8:26 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:23 ` Sebastian Schuberth 2021-04-19 22:34 ` Theodore Ts'o 2021-04-20 6:30 ` Sebastian Schuberth 2021-04-20 16:37 ` Theodore Ts'o 2021-04-30 20:45 ` Felipe Contreras 2021-04-20 10:34 ` Ævar Arnfjörð Bjarmason 2021-04-19 19:36 ` Eric Wong 2021-04-19 19:49 ` Sebastian Schuberth 2021-04-19 22:00 ` Konstantin Ryabitsev 2021-05-08 2:10 ` dwh 2021-04-19 21:49 ` Konstantin Ryabitsev 2021-04-19 23:03 ` Stephen Smith 2021-05-08 2:08 ` dwh 2021-05-08 4:41 ` Bagas Sanjaya 2021-04-30 20:58 ` Felipe Contreras 2021-04-21 4:46 ` Daniel Axtens 2021-04-26 2:04 ` brian m. carlson 2021-04-26 14:24 ` Theodore Ts'o 2021-04-26 14:36 ` Ævar Arnfjörð Bjarmason 2021-04-28 7:59 ` Eric Wong 2021-04-28 22:44 ` brian m. carlson 2021-04-30 20:16 ` Felipe Contreras 2021-04-30 20:35 ` Felipe Contreras 2021-04-30 21:09 ` Felipe Contreras
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210428072138.GB13114@dcvr \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Pain points in Git'\''s patch flow' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).