From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Web interface pushed Date: Fri, 10 Aug 2018 07:01:46 +0200 Message-ID: References: <87r2jlbsq3.fsf@lassieur.org> <87h8khbo71.fsf@gnu.org> <20180730124528.hgkpl2kbxc6fglp5@thebird.nl> <87lg9ssvl7.fsf@elephly.net> <87sh3vpne9.fsf@elephly.net> <877el57psd.fsf@elephly.net> <87a7pvuv3c.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000ad58af05730da407" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fnzYm-0002zV-Te for guix-devel@gnu.org; Fri, 10 Aug 2018 01:02:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fnzYl-0000Tt-PA for guix-devel@gnu.org; Fri, 10 Aug 2018 01:02:00 -0400 In-Reply-To: <87a7pvuv3c.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: Guix-devel , =?UTF-8?Q?Cl=C3=A9ment_Lassieur?= , Tatiana Sholokhova --000000000000ad58af05730da407 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ricardo Wurmus ezt =C3=ADrta (id=C5=91pont: 2018. aug.= 9., Cs, 22:46): > > Hi Tatiana, > > > I pushed commits implementing the features we discussed before. Could y= ou > > please take a look at them? > > I=E2=80=99ll leave the review to Cl=C3=A9ment who volunteered to take a l= ook at your > commits soon. (He=E2=80=99s 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 colu= mn > > of the table with information about builds of an evaluation. What do yo= u > > think about this? > > I think that=E2=80=99s fine for now. > > I=E2=80=99d like to show more information in the future, such as build ti= me, 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=E2=80=99t need to know anything about the blog to prepare the pos= t. The > format is markdown. Amirouche sent instructions on how to build the > website (including the blog), but you don=E2=80=99t need to play with thi= s if > you don=E2=80=99t want to. It would be sufficient to send the blog post = draft > to Cl=C3=A9ment, Ludovic, and myself via email. (Please don=E2=80=99t us= e 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 > > --000000000000ad58af05730da407 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ricardo Wurmus= <rekado@elephly.net> ezt = =C3=ADrta (id=C5=91pont: 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=E2=80=99ll leave the review to Cl=C3=A9ment who volunteered to take a loo= k at your
commits soon.=C2=A0 (He=E2=80=99s 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<= br> > information we can display on this page except the link to the log fil= e.
> So, for now I have added a link to the log file in the newly added col= umn
> of the table with information about builds of an evaluation. What do y= ou
> think about this?

I think that=E2=80=99s fine for now.

I=E2=80=99d 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 th= ings like previous builds, last successful build, last failing build later.=
=C2=A0
> I thought about writing the summary of and sending it to the mailing l= ist,
> 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 somethin= g
> special I need to know about preparing the blog post?

You don=E2=80=99t need to know anything about the blog to prepare the post.= =C2=A0 The
format is markdown.=C2=A0 Amirouche sent instructions on how to build the website (including the blog), but you don=E2=80=99t need to play with this = if
you don=E2=80=99t want to.=C2=A0 It would be sufficient to send the blog po= st draft
to Cl=C3=A9ment, Ludovic, and myself via email.=C2=A0 (Please don=E2=80=99t= use Google
Docs.)=C2=A0 We would comment inline if any changes are needed.

Once approved I would publish it on your behalf.

Does this sound okay?

--
Ricardo

--000000000000ad58af05730da407--