From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tatiana Sholokhova Subject: Re: Web interface pushed Date: Tue, 7 Aug 2018 23:33:52 +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> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000003508a40572df27d1" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35641) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fn9cF-0006b4-L3 for guix-devel@gnu.org; Tue, 07 Aug 2018 17:34:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fn9cD-0008UF-VV for guix-devel@gnu.org; Tue, 07 Aug 2018 17:34:07 -0400 In-Reply-To: <877el57psd.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?= --0000000000003508a40572df27d1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Ricardo, I pushed commits implementing the features we discussed before. Could you please take a look at them? 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 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? Also, I would like to create a draft version of the final document and share it with you in order to discuss it before publishing. What do you think is the best way to maintain this draft? I would suggest google doc, but it may be not compatible with the blog post format. Best regards, Tatiana On Sun, 5 Aug 2018 at 00:03, Ricardo Wurmus wrote: > > Hi Tatiana, > > > The next features I am thinking of are > > > > - make red, green and grey links on the evaluations page actually > > working and usable for filtering builds of the evaluation with a giv= en > > status; > > - add some navigation tools to improve usability, especially for the > > case when a user wants to go back to the previous level of the > interface > > (e.g. from evaluation page to specifications list); > > - add a page with some basic info about a build, containing a link t= o > > the corresponding build log; > > This all sounds very good and manageable. I think this also matches > some of the open items that G=C3=A1bor identified earlier. > > > I am going to make a new branch and push these changes in a few days, s= o > > you could try them. > > Excellent! > > > I have a question regarding the link for the final GSOC evaluation. > > According to the GSOC requirements > > < > https://developers.google.com/open-source/gsoc/help/work-product#requirem= ent > >, > > from the provided URL it should demonstrate the result of the project. = I > > suppose that it would be nice to include the example of the working > > interface running on https://berlin.guixsd.org/ to the final document > which > > I will prepare for the evaluation (and which also will contain a link t= o > > the list of changes made to the codebase). Would it be appropriate to d= o > > so? > > Yes, this would be fine, but note that the document should really stand > on its own. Whatever is shown on https://berlin.guixsd.org/ will change > over time. You can add a link to it as an example, but make sure that > your =E2=80=9Cwork product=E2=80=9D page would not feel incomplete withou= t it. > (E.g. take screenshots if you want to show specific features instead of > linking to pages on https://berlin.guixsd.org/) > > If you want to we could also aim to publish this as a blog post on the > Guix website, but that=E2=80=99s really up to you. The Guix blog is a go= od way > to make your work known in the community and to people who are following > the project. > > -- > Ricardo > > --0000000000003508a40572df27d1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Ricardo,

I pushed commits implementing the featu= res we discussed before. Could you please take a look at them? I have recon= sidered 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 th= e newly added column of the table with information about builds of an evalu= ation. What do you think about this?

I thought about writing the sum= mary of and sending it to the mailing list, but now I think that a blog pos= t 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 preparin= g the blog post? Also, I would like to create a draft version of the final = document and share it with you in order to discuss it before publishing. Wh= at do you think is the best way to maintain this draft? I would suggest goo= gle doc, but it may be not compatible with the blog post format.

Bes= t regards,
Tatiana

On Sun, 5 Aug 2018 at 00:03, Ricardo Wurmus <rekado@elephly.net> wrote:

Hi Tatiana,

> The next features I am thinking of are
>
>=C2=A0 =C2=A0 - make red, green and grey links on the evaluations page = actually
>=C2=A0 =C2=A0 working and usable for filtering builds of the evaluation= with a given
>=C2=A0 =C2=A0 status;
>=C2=A0 =C2=A0 - add some navigation tools to improve usability, especia= lly for the
>=C2=A0 =C2=A0 case when a user wants to go back to the previous level o= f the interface
>=C2=A0 =C2=A0 (e.g. from evaluation page to specifications list);
>=C2=A0 =C2=A0 - add a page with some basic info about a build, containi= ng a link to
>=C2=A0 =C2=A0 the corresponding build log;

This all sounds very good and manageable.=C2=A0 I think this also matches some of the open items that G=C3=A1bor identified earlier.

> I am going to make a new branch and push these changes in a few days, = so
> you could try them.

Excellent!

> I have a question regarding the link for the final GSOC evaluation. > According to the GSOC requirements
> <https://develop= ers.google.com/open-source/gsoc/help/work-product#requirement>,
> from the provided URL it should demonstrate the result of the project.= I
> suppose that it would be nice to include the example of the working > interface running on https://berlin.guixsd.org/ to the final docu= ment which
> I will prepare for the evaluation (and which also will contain a link = to
> the list of changes made to the codebase). Would it be appropriate to = do
> so?

Yes, this would be fine, but note that the document should really stand
on its own.=C2=A0 Whatever is shown on https://berlin.guixsd.org/ will= change
over time.=C2=A0 You can add a link to it as an example, but make sure that=
your =E2=80=9Cwork product=E2=80=9D page would not feel incomplete without = it.
(E.g. take screenshots if you want to show specific features instead of
linking to pages on https://berlin.guixsd.org/)

If you want to we could also aim to publish this as a blog post on the
Guix website, but that=E2=80=99s really up to you.=C2=A0 The Guix blog is a= good way
to make your work known in the community and to people who are following the project.

--
Ricardo

--0000000000003508a40572df27d1--