all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: good overview presentation?
Date: Fri, 10 May 2019 07:57:06 -0500	[thread overview]
Message-ID: <16aa1d18e2b.ffba141c18140.4843251965222243804@zoho.com> (raw)
In-Reply-To: <87k1eyhiak.fsf@roquette.mug.biscuolo.net>

---- On Fri, 10 May 2019 02:37:07 -0500 Giovanni Biscuolo <g@xelera.eu> wrote ----

 > Hello Miles, 
 >  
 > Miles Fidelman <mfidelman@meetinghouse.net> writes: 
 >  
 > > Thanks Chris, 
 > > 
 > > A couple of follow-ups: 
 > > 
 > > On 5/9/19 12:39 PM, Christopher Baines wrote: 
 > >> 
 > >> 1: http://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/talks 
 > >> 
 > >> There's also two talks [2] which I've given in the past on Guix, they're 
 > >> a few years old, but I think most of the material is still correct. 
 > >> 
 > > Silly me, but how does one view these things?  The ones labeled with 
 > > .pdf extensions come across as ascii files, that can't be read as pdf, 
 >  
 > maintenance.git and its cgit interface is not it's not intended as a 
 > "site substitute", it's an anchive where Guix developers share common 
 > work in the community 
 >  
 > ...anyway, for each media-like file there is a "plain" labelled link 
 > near the blob code, right above the table with hex and ascii code of the 
 > git object: that link will download the file 
 >  
 > > and others look like they have to be assembled. 
 >  
 > yes, the rationale to include or ignore media artifacts is not clear to 
 > me: I'd include only sources, publishing artifacts on a dedicated static 
 > web page... or move talks out from maintenance.git to a dedicated git 
 > repo like guix/talks.git (like the existing guix/videos.git), publishing 
 > them to the web 

Using the topic list in the blog is currently the easiest way to find videos, papers, etc. For example:

    https://www.gnu.org/software/guix/blog/tags/talks/
    https://www.gnu.org/software/guix/blog/tags/papers/

Also, Laura and Paul are working in some introductory videos right now (https://git.savannah.gnu.org/git/guix/videos.git), and there are some ideas already about how to make the multimedia material about Guix more visible (https://lists.gnu.org/archive/html/guix-devel/2017-12/msg00260.html). This things will be available sooner or later. I haven't found some free time myself to help in that area :)

  reply	other threads:[~2019-05-10 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 15:04 good overview presentation? Miles Fidelman
2019-05-09 16:39 ` Christopher Baines
2019-05-09 21:42   ` Miles Fidelman
2019-05-10  7:15     ` Christopher Baines
2019-05-10  7:37     ` Giovanni Biscuolo
2019-05-10 12:57       ` sirgazil [this message]
2019-05-10 16:15         ` thanks all - for answers to recent questions Miles Fidelman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16aa1d18e2b.ffba141c18140.4843251965222243804@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=g@xelera.eu \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.