all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
	Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: [outreachy] Further steps
Date: Sun, 28 Oct 2018 16:01:32 -0300	[thread overview]
Message-ID: <CAPNLzUPDdscsFQkcbHNR-K3qenHJOakNyCG=yhhyn-8wxBGi3w@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pjEhG7-VomRRuYYUxO3KJC1rpNNB9gkwQCc6s+_uadxFA@mail.gmail.com>

Hi!
On Sun, Oct 28, 2018 at 5:36 AM Gábor Boskovits <boskovits@gmail.com> wrote:
>
> Hello Laura,
>
> Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018.
> okt. 28., V, 2:52):
> >
> > On Fri, Oct 26, 2018 at 5:06 PM Ricardo Wurmus
> > <ricardo.wurmus@mdc-berlin.de> wrote:
> > >
> > >
> > > Hi Laura,
> > >
> > > >> > > I would like you to come up with an initial proposal, and then iterate on that.
> > > >> > Ok, I have the initial Outreachy project next to me. I will take a
> > > >> > look at everything there, and write down a proposal, during the
> > > >> > following days, WDYT?
> > > >>
> > > >> Ok, that would be great.
> > > > I have one last question: do I need to follow a specific format?
> > > > ie: a  template or just writing down in plain text:
> > > > From date/week number up to date/week number: and a TODO list of tasks?
> > >
> > > Plain text is fine.  It only needs to clearly communicate your intent.
> > Sorry, I wrote some ideas in the discussion thread about the videos.
> > I have one last question about the timeline:
> > How much in depth I need to detail what I am thinking of doing each
> > week/s? Is it ok writing a general idea,
> > For example:
> > Week 1: learn the necessary concepts about video creation, and tools I
> > will be using
> > Week 2: work on the video/s about packaging (for example, as it is one
> > mentioned on the Oureachy website)
> > Or does it have to be more detailed?
>
> I prefer to see an outline first, not very much detalied, and when the need
> arises some parts can be refined. When there is a timeline, it is good to see
> what the time estimates are based on. One way to do that is to break down
> a task, as time requirements of smaller tasks are easier to estimate, but
> there are other ways. So I don't think we need a much more detailed timeline
> initially, but it would be nice if you could point out what your time estimates
> are based on. If anyone is confused about a point in the outline, or would like
> to see more details, then that can be refined. WDYT?
I think that is OK, I am answering the mail with the discussion about
the videos to see how to go on with my timeline, since it is my first
proposal and I guess it will have to be modified. For example, there
are some details about how to group tasks according to which videos
are needed. But I will come up with an initial version at least to
know if i am on the right track.

>
>
> > Regards!
> > >
> > > --
> > > Ricardo
> > Laura
>
> Best regards,
> g_bor
Regards!
Laura

      reply	other threads:[~2018-10-28 19:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  1:48 [outreachy] Further steps Laura Lazzati
2018-10-24  5:16 ` Björn Höfling
2018-10-24  7:00   ` Gábor Boskovits
2018-10-24 22:16     ` Laura Lazzati
2018-10-25  3:08       ` Ricardo Wurmus
2018-10-25 14:16         ` Laura Lazzati
2018-10-25 14:37           ` Gábor Boskovits
2018-10-25 14:55             ` Laura Lazzati
2018-10-25 17:29               ` guix pull: error: symlink: File exists (was: Re: [outreachy] Further steps) Thorsten Wilms
2018-10-25 19:08                 ` Gábor Boskovits
2018-10-30 18:16                   ` Laura Lazzati
2018-10-30 20:02                     ` guix pull: error: symlink: File exists Thorsten Wilms
2018-10-30 22:43                       ` Laura Lazzati
2018-10-31 10:06                         ` Laura Lazzati
2018-10-31 10:27                           ` Gábor Boskovits
2018-10-31 10:31                             ` Laura Lazzati
2018-10-31 11:07                               ` Gábor Boskovits
2018-10-31 11:15                                 ` Laura Lazzati
2018-10-31 11:52                                   ` Gábor Boskovits
2018-10-31 12:29                                     ` Catonano
2018-10-31 16:02                                     ` Laura Lazzati
2018-10-31 16:25                                       ` Gábor Boskovits
2018-10-31 18:09                                         ` Laura Lazzati
2018-10-31 19:03                                           ` Gábor Boskovits
2018-11-01  2:09                                             ` Laura Lazzati
2018-11-01  8:49                                               ` Gábor Boskovits
2018-11-01 11:37                                                 ` Laura Lazzati
2018-11-01 11:48                                                   ` Gábor Boskovits
2018-11-01 17:51                                                     ` Laura Lazzati
2018-10-26  5:58           ` [outreachy] Further steps Ricardo Wurmus
2018-10-26 10:00             ` Laura Lazzati
2018-10-26 10:31               ` Laura Lazzati
2018-10-26 19:21                 ` Laura Lazzati
2018-10-25 10:57       ` Gábor Boskovits
2018-10-25 14:36         ` Laura Lazzati
2018-10-26 10:40           ` Ricardo Wurmus
2018-10-26 15:00             ` Laura Lazzati
2018-10-26 17:21               ` Gábor Boskovits
2018-10-26 18:46                 ` Laura Lazzati
2018-10-26 19:06                   ` Gábor Boskovits
2018-10-26 19:36                     ` Laura Lazzati
2018-10-26 20:06                       ` Ricardo Wurmus
2018-10-28  1:51                         ` Laura Lazzati
2018-10-28  8:36                           ` Gábor Boskovits
2018-10-28 19:01                             ` Laura Lazzati [this message]

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='CAPNLzUPDdscsFQkcbHNR-K3qenHJOakNyCG=yhhyn-8wxBGi3w@mail.gmail.com' \
    --to=laura.lazzati.15@gmail.com \
    --cc=boskovits@gmail.com \
    --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.