From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: packaging
Date: Thu, 14 Feb 2019 11:55:34 -0300 [thread overview]
Message-ID: <CAPNLzUO5i584YVghnoEVtLreNU80HaEv3vU8fPZ6OXCA1W=pRQ@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=phHQN9EWQEkXByjxU8HPZDtog9U5Wj-xtBw1_hoWzxO2w@mail.gmail.com>
Hi!
was planning to add my point of view a little later, after finishing
my draft of everyday use, which I am also finding that only with
concepts and showing the basic commands lasts three minutes up to now,
and I still have a lot to show/mention.
> Yes, I agree to this outline. One possibility if it turns out to be
> too much for a single video, is to spilt it up.
I agree, it is a LOT for a single video, but don't you think we are
kind of turning the whole documentation into videos? I don't mind
making as many videos as possible, but I am getting that sense.
Specially if a 5 min video is too long. That is why I thought of
packaging an R package, explaining maybe what "each line of the
package" means, and then people can read the documentation to create
their owns. But again, I don't mind. I create the videos that you find
more useful.
> 4. follow up activities:
> creating the patch
> sending the patch
> following it on the issue tracker
> incorporating feedback and resending...
> WDYT?
This could be included in the R package video.
next prev parent reply other threads:[~2019-02-14 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:38 New topic: packaging Laura Lazzati
2019-02-11 15:49 ` znavko
2019-02-13 3:03 ` Laura Lazzati
2019-02-13 9:13 ` Björn Höfling
2019-02-14 14:41 ` Gábor Boskovits
2019-02-14 14:55 ` Laura Lazzati [this message]
2019-02-17 9:02 ` swedebugia
2019-02-18 21:16 ` 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='CAPNLzUO5i584YVghnoEVtLreNU80HaEv3vU8fPZ6OXCA1W=pRQ@mail.gmail.com' \
--to=laura.lazzati.15@gmail.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@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.