From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>,
"Clément Lassieur" <clement@lassieur.org>,
"Tatiana Sholokhova" <tanja201396@gmail.com>
Subject: Re: Web interface pushed
Date: Fri, 10 Aug 2018 07:01:46 +0200 [thread overview]
Message-ID: <CAE4v=phUYBxzD5FA2Y4ief1AfP=cFNG3pRfEUJhV4AcnMKkJEQ@mail.gmail.com> (raw)
In-Reply-To: <87a7pvuv3c.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. aug. 9., Cs,
22:46):
>
> Hi Tatiana,
>
> > I pushed commits implementing the features we discussed before. Could you
> > please take a look at them?
>
> I’ll leave the review to Clément who volunteered to take a look at your
> commits soon. (He’s more familiar with Cuirass than I am.)
>
> > I have reconsidered the idea of having a
> > separate page with build information, as I do not see what additional
> > information we can display on this page except the link to the log file.
> > So, for now I have added a link to the log file in the newly added column
> > of the table with information about builds of an evaluation. What do you
> > think about this?
>
> I think that’s fine for now.
>
> I’d like to show more information in the future, such as build time, git
> change that triggered the build, links to packages that depend on this
> build (and packages that affect this build in case of a propagated
> failure), etc.
>
>
Here we could also find a place for things like previous builds, last
successful build, last failing build later.
> > I thought about writing the summary of and sending it to the mailing
> list,
> > but now I think that a blog post would be more convenient for a reader.
> > What is the source format for guix blog markdown and is where something
> > special I need to know about preparing the blog post?
>
> You don’t need to know anything about the blog to prepare the post. The
> format is markdown. Amirouche sent instructions on how to build the
> website (including the blog), but you don’t need to play with this if
> you don’t want to. It would be sufficient to send the blog post draft
> to Clément, Ludovic, and myself via email. (Please don’t use Google
> Docs.) We would comment inline if any changes are needed.
>
> Once approved I would publish it on your behalf.
>
> Does this sound okay?
>
> --
> Ricardo
>
>
[-- Attachment #2: Type: text/html, Size: 2512 bytes --]
next prev parent reply other threads:[~2018-08-10 5:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 22:08 Web interface pushed Clément Lassieur
2018-07-29 23:46 ` Ludovic Courtès
2018-07-30 12:45 ` Pjotr Prins
2018-07-30 13:26 ` Ricardo Wurmus
2018-08-01 19:47 ` Tatiana Sholokhova
2018-08-02 6:53 ` Clément Lassieur
2018-08-02 16:00 ` Gábor Boskovits
2018-08-02 16:49 ` Clément Lassieur
2018-08-02 18:48 ` Gábor Boskovits
2018-08-02 19:21 ` Amirouche Boubekki
2018-08-02 20:16 ` Clément Lassieur
2018-08-02 18:13 ` Amirouche Boubekki
2018-08-02 20:17 ` Clément Lassieur
2018-08-03 13:53 ` Ricardo Wurmus
2018-08-04 21:53 ` Tatiana Sholokhova
2018-08-04 22:03 ` Ricardo Wurmus
2018-08-07 21:33 ` Tatiana Sholokhova
2018-08-09 9:17 ` Clément Lassieur
2018-08-09 19:59 ` amirouche
2018-08-09 20:46 ` Ricardo Wurmus
2018-08-10 5:01 ` Gábor Boskovits [this message]
2018-08-10 9:10 ` Clément Lassieur
2018-08-11 16:38 ` Ricardo Wurmus
2018-07-30 7:38 ` amirouche
2018-07-30 9:11 ` Clément Lassieur
2018-07-30 9:23 ` Alex Sassmannshausen
2018-07-30 9:41 ` Nils Gillmann
2018-07-30 12:08 ` Ricardo Wurmus
2018-07-30 12:14 ` Gábor Boskovits
2018-07-30 14:10 ` Hartmut Goebel
2018-07-30 16:02 ` Clément Lassieur
2018-07-30 18:43 ` Amirouche Boubekki
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='CAE4v=phUYBxzD5FA2Y4ief1AfP=cFNG3pRfEUJhV4AcnMKkJEQ@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=tanja201396@gmail.com \
/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).