From: swedebugia <swedebugia@riseup.net>
To: guix-devel <guix-devel@gnu.org>
Subject: (cuirass) Consistent naming and presentation on the front page.
Date: Mon, 19 Nov 2018 12:37:48 +0100 [thread overview]
Message-ID: <632f9fe4-cf82-ee05-7340-61549bad0594@riseup.net> (raw)
Hi
I propose we stick to one naming scheme and keep it in both urls and the
web-ui.
I propose to completely drop the words "evaluation(s)" and "build(s)" as
this is just confusing and implement the following changes:
Look at http://berlin.guixsd.org/ and see how it looks now.
Specifications:
--------------
Name Inputs
wip-rust wip-rust (on wip-rust)
Jobsets (for specification: wip-rust)
------------------------------------
Jobset ID Input changes Success Status
1321 wip-rust → 4df3e06 4340 active/inactive
...
Jobs in jobset #1231:
----------------------
ID Specification Completion time
(icon) 586752 wip-rust 12 Nov 21:59 +0100
Jobname Packagename
rust-1.24.1.x86_64-linux rust-1.24.1
System Log
x86_64-linux raw
...
I changed:
Jobs renamed /job/jobname/ and /name/packagename/ and removed "builds of
evaluation"
Jobset renamed /#/jobset id/ and removed "evaluations of"
Jobs have status succede/failed/canceled/pending and logs.
Jobsets can be active/inactive
Specifications does not have a status but an input.
Also I would like to propagate the status and links from the jobset-page
to the header of the jobs-page (now with the uri /eval/####) below the
title like this:
"Browse by jobstatus: # succeded # failed # pending" (with textlinks)
Thoughts?
Presentation:
-------------
If somebody really want to mention evaluation and build I suggest to
describe the whole build-server rationale on the frontpage in a paragraph.
There we could also describe the machines, hardware and status of the
whole shabang and a paragraph with thanks to MDC for donating/hosting
the hardware to make this possible.
What do you think?
--
Cheers Swedebugia
next reply other threads:[~2018-11-22 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 11:37 swedebugia [this message]
2018-11-22 9:46 ` (cuirass) Consistent naming and presentation on the front page Clément Lassieur
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=632f9fe4-cf82-ee05-7340-61549bad0594@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
/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).