From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Web interface pushed Date: Thu, 09 Aug 2018 22:46:15 +0200 Message-ID: <87a7pvuv3c.fsf@elephly.net> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33254) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fnrpa-0003l8-9j for guix-devel@gnu.org; Thu, 09 Aug 2018 16:46:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fnrpW-00037s-Pq for guix-devel@gnu.org; Thu, 09 Aug 2018 16:46:50 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21130) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fnrpW-00037O-Gv for guix-devel@gnu.org; Thu, 09 Aug 2018 16:46:46 -0400 In-reply-to: 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: Tatiana Sholokhova Cc: guix-devel , =?utf-8?Q?Cl=C3=A9ment?= Lassieur 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. (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 column > of the table with information about builds of an evaluation. What do you > 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. > 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 post.= 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 this = if you don=E2=80=99t want to. It would be sufficient to send the blog post dr= aft to Cl=C3=A9ment, Ludovic, and myself via email. (Please don=E2=80=99t 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