all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel <guix-devel@gnu.org>,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Video documentation repository
Date: Thu, 07 Feb 2019 20:31:30 +0100	[thread overview]
Message-ID: <877eeb2y5p.fsf@gnu.org> (raw)
In-Reply-To: <20190205110415.296cf031@alma-ubu> ("Björn Höfling"'s message of "Tue, 5 Feb 2019 11:04:15 +0100")

[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]

Hello!

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:

> On Tue, 05 Feb 2019 00:02:20 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Great initiative!  I can’t create it myself but I’ve filed a support
>> request: <https://savannah.nongnu.org/support/?109642> (the Savannah
>> hackers usually respond within a couple of days.)
>
> Thank you for filing the request. There you wrote:
>
>> This repository will *not* contain any video.  Instead, it will
>> contains scripts and tools developed as part of an ongoing Outreachy
>> internship to create internationalized videos presenting Guix.
>
> In the current video-repository we at least save the input binaries
> (i.e speech recordings in several languages for several videos). From
> your comment it sounds like that is not intended for the
> savannah-repos, right?

True.  I mostly wanted to reassure them that this would not be a huge
repo containing only binary files.  So I guess it’s OK to save audio
tracks as long as it doesn’t grow too much.

If/when it happens to grow quickly than expected, we’ll ask the Savannah
folks whether it’s still fine with them.

> If so, we need to somehow externalize those. What would be a reliable
> way of doing so? Uploading to some (which?) server? MediaGoblin? Storing
> in IPFS as we do currently with the output videos for distribution among
> us? Is there any stable IPFS node where we can stick them to?

I’d say we can think about that later if it becomes a problem.

>> I guess we could give Laura access to the repo (that gives access to
>> all the project repos so one has to be cautious, but that’s probably
>> OK.) Thoughts?
>
> I think we gave permissions to all former GSoC/Outreachy students,
> right? So I'm fine with it.

Alright!

Laura, could you please upload the OpenPGP key that you will be using to
sign commits to <https://savannah.gnu.org/users/lsl88>, and then reply
to this message signed with that same key?  (If you need help setting
that up, we can discuss it off-list.)

Please read the ‘HACKING’ file as well.  Technically you’ll have access
to all the Guix repositories, but for now I’d prefer you to restrict
pushes to the video repo (once it has been created, that is :-)).  That
said, you’re of course welcome to contribute to the other repos, but
please email guix-devel or guix-patches beforehand.

Thanks!

Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2019-02-07 19:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 11:53 Video documentation repository Björn Höfling
2019-02-04 21:01 ` Laura Lazzati
2019-02-04 23:02 ` Ludovic Courtès
2019-02-05 10:04   ` Björn Höfling
2019-02-07 19:31     ` Ludovic Courtès [this message]
2019-02-08  8:54       ` Björn Höfling

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=877eeb2y5p.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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.