unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: We need your feedback of the documentation videos!
Date: Fri, 25 Oct 2019 23:58:04 +0200	[thread overview]
Message-ID: <20191025215804.mevbuyvffpunyhbi@pelzflorian.localdomain> (raw)
In-Reply-To: <87imoco9bb.fsf@gnu.org>

Thank you for all your reviews!  Feel free to change some things later on:

I will push tomorrow morning with a clear mind. :)


On Tue, Oct 22, 2019 at 11:25:27AM -0500, sirgazil wrote:
> Now, personally, if I had the time, I would have designed the videos page in a similar way to the blog page,

I have *not* done this, only the link is no longer yellow.

> and also done something like this:
> 
> […]
> * Add a "media" app that would hold the definitions for videos and screenshots (the latter would move from the base app).

I have done this, but most of the screenshot-related CSS remains in
website/static/base/css/index.css.

> […]
> * Add a new entry to the Help page, next to "GNU Guix Manual", with the same "Instructional videos" title.

I have *not* done this yet, as I am bad at drawing icons for the help
page.  I could ask a friend of mine or have you do it.

>  > P.S. I would like to request a review of this functions I would like 
>  > to add to website/apps/aux/lists.scm: 
> 
> 
> Or maybe you could factor out the "sample" procedure defined in the
> "index-builder" of "(apps packages builder)". I think Wurmus added
> that one for the Packages home page.
> 
> 

Thank you for the suggestion!  However, I believe it would sample the
same element twice.  That is unlikely to happen for packages but a
problem for screenshots.  I will probably retain my take-random
procedure, even though it is not as concise as it should be.

>  > Also I want to ask, the “license” header says: 
>  >  
>  > ;;; GNU Guix web site 
>  > ;;; Initially written by sirgazil who waves all 
>  > ;;; copyright interest on this file. 
>  >  
>  > sirgazil, shall I replace “waves” by “waives”?  I believe this is a 
>  > typo. 
> 
> 
> That's a typo, yes. Although, if I didn't do anything in that file,
> I think that line should not be there, but I'm not a lawyer.
>

IANAL, but I copied code from the files you worked on, so you have
copyright.  I will fix the typo in all files then.

On Fri, Oct 25, 2019 at 10:32:24PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> > Ludo, shall I push this evening
> > with videos coming from the Internet Archive (archive.org)?
> 
> Sure!  I haven’t tried building the web site with the patches (do check
> “guix build -f .guix.scm” before pushing), but the changes LGTM
> overall, and long overdue!
> 
> We can keep the videos on archive.org for now, I guess they won’t
> disappear overnight, and eventually we can move them to guix.gnu.org
> when one of us can allocate time for that.
> 
> Thank you for moving forward on this topic!
> 

OK, thank you!

Regards,
Florian

  reply	other threads:[~2019-10-25 21:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 15:11 We need your feedback of the documentation videos! Laura Lazzati
2019-07-16 17:40 ` pelzflorian (Florian Pelz)
2019-07-17  6:31 ` Dimakakos Dimos
2019-07-17  7:55   ` pelzflorian (Florian Pelz)
2019-07-30 14:37     ` pelzflorian (Florian Pelz)
2019-07-17  7:11 ` Tanguy Le Carrour
2019-07-17  9:44 ` Ricardo Wurmus
2019-07-30 13:26   ` Laura Lazzati
2019-07-30 15:03     ` Tobias Geerinckx-Rice
2019-07-30 17:12       ` Tobias Geerinckx-Rice
2019-07-30 14:06   ` pelzflorian (Florian Pelz)
2019-08-08 15:04   ` Laura Lazzati
2019-08-08 15:48     ` Ricardo Wurmus
2019-08-13 18:03       ` Laura Lazzati
2019-08-25 18:55         ` Laura Lazzati
2019-10-17  4:34           ` pelzflorian (Florian Pelz)
2019-10-19 20:13             ` Ludovic Courtès
2019-10-19 21:00               ` pelzflorian (Florian Pelz)
2019-10-22 12:05                 ` pelzflorian (Florian Pelz)
2019-10-22 16:25                   ` sirgazil
2019-10-22 18:59                     ` pelzflorian (Florian Pelz)
2019-10-23 11:49                       ` pelzflorian (Florian Pelz)
2019-10-23 14:33                         ` sirgazil
2019-10-25  6:35                       ` pelzflorian (Florian Pelz)
2019-10-25  8:12                         ` pelzflorian (Florian Pelz)
2019-10-25 14:25                           ` sirgazil
2019-10-25 20:32                         ` Ludovic Courtès
2019-10-25 21:58                           ` pelzflorian (Florian Pelz) [this message]
2019-10-26 14:29                             ` pelzflorian (Florian Pelz)
2019-10-27 19:47                               ` sirgazil
2019-10-28  7:41                                 ` pelzflorian (Florian Pelz)

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=20191025215804.mevbuyvffpunyhbi@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).