unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tatiana Sholokhova <tanja201396@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
	"Clément Lassieur" <clement@lassieur.org>
Subject: Re: Web interface pushed
Date: Sun, 05 Aug 2018 00:03:30 +0200	[thread overview]
Message-ID: <877el57psd.fsf@elephly.net> (raw)
In-Reply-To: <CAMSS15AktLBmJGU-85_bg+tbb1daFS3o+1XmCy=t2NaqOo=5=A@mail.gmail.com>


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 given
>    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 to
>    the corresponding build log;

This all sounds very good and manageable.  I think this also matches
some of the open items that Gábor 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://developers.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 document 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.  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 “work product” 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’s really up to you.  The Guix blog is a good way
to make your work known in the community and to people who are following
the project.

--
Ricardo

  reply	other threads:[~2018-08-05 17:50 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 [this message]
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
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=877el57psd.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=clement@lassieur.org \
    --cc=guix-devel@gnu.org \
    --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).