From: Christopher Baines <mail@cbaines.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Data Services: use cases
Date: Mon, 16 Nov 2020 19:20:29 +0000 [thread overview]
Message-ID: <87pn4dm7lu.fsf@cbaines.net> (raw)
In-Reply-To: <87d01m3475.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Sorry if I'm stating the obvious, but ideally it'd be nice if the
> interface would be so straightforward it didn't need any instructions to
> use :)
>
> In particular, the "Version From To" table is hard to grasp to a
> newcomer.
>
> During the Guix Days we talked about how to make it a bit more
> approachable. From what I recall:
>
> - Maybe make the timeline bars more visible.
I've finally got around to looking at this now. I've changed them to a
slightly darker grey.
> - The timeline is not usable and does not convey much information beside
> an approximate lifespan of versions, which I'm not sure many users
> need. Consider removing it, or displaying it in a separate graph?
>
> Ultimately, we need a list of versions with their Guix builds.
Personally, that what I designed that page to convey, at least the grey
bars, they're just to give a sense of how the
versions/derivations/outputs have changed over time.
> - "From" and "To" should probably be renamed "From Guix build" and "To
> Guix build" respectively.
I've made the commit hash more prominent now, which might help with
this.
> - (More information) should be renamed to something like "Package
> information".
I've made this change now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-11-16 19:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 13:26 Data Services: use cases zimoun
2020-10-13 8:44 ` Pierre Neidhardt
2020-10-21 9:27 ` Ludovic Courtès
2020-10-21 9:39 ` Pierre Neidhardt
2020-10-21 10:19 ` zimoun
2020-11-16 19:28 ` Christopher Baines
2020-11-16 20:24 ` zimoun
2020-11-16 20:54 ` Christopher Baines
2020-11-16 21:12 ` zimoun
2020-11-16 21:50 ` Christopher Baines
2020-11-16 22:38 ` zimoun
2020-11-17 21:43 ` zimoun
2020-11-17 21:57 ` Fix incorrect date and commit in Data Service zimoun
2020-11-17 22:44 ` zimoun
2020-11-16 19:26 ` Data Services: use cases Christopher Baines
2020-11-16 19:20 ` Christopher Baines [this message]
2020-11-17 7:48 ` Pierre Neidhardt
2020-11-17 8:04 ` Christopher Baines
2020-11-17 8:49 ` Pierre Neidhardt
2020-11-17 19:34 ` Christopher Baines
2020-11-17 19:42 ` Pierre Neidhardt
2020-11-16 19:17 ` Christopher Baines
2020-11-16 20:34 ` zimoun
2020-11-16 21:08 ` Christopher Baines
2020-11-17 13:19 ` Linking to the data service Ludovic Courtès
2020-11-17 16:26 ` zimoun
2020-11-17 16:18 ` Data Services: use cases zimoun
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn4dm7lu.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).