From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: [outreachy] Further steps Date: Sun, 28 Oct 2018 09:36:45 +0100 Message-ID: References: <20181024071635.29543fcf@alma-ubu> <875zxp56un.fsf@elephly.net> <87sh0s4gn2.fsf@mdc-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGgZB-00044k-3d for guix-devel@gnu.org; Sun, 28 Oct 2018 04:37:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gGgZ9-0002dr-Fc for guix-devel@gnu.org; Sun, 28 Oct 2018 04:37:01 -0400 Received: from mail-oi1-x22e.google.com ([2607:f8b0:4864:20::22e]:38136) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gGgZ9-0002dN-5z for guix-devel@gnu.org; Sun, 28 Oct 2018 04:36:59 -0400 Received: by mail-oi1-x22e.google.com with SMTP id k19-v6so4502920oiw.5 for ; Sun, 28 Oct 2018 01:36:58 -0700 (PDT) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Laura Lazzati Cc: Guix-devel , Ricardo Wurmus Hello Laura, Laura Lazzati ezt =C3=ADrta (id=C5=91pont: 201= 8. okt. 28., V, 2:52): > > On Fri, Oct 26, 2018 at 5:06 PM Ricardo Wurmus > wrote: > > > > > > Hi Laura, > > > > >> > > I would like you to come up with an initial proposal, and then i= terate 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 task= s? > > > > 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 s= ee 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 timelin= e initially, but it would be nice if you could point out what your time estim= ates 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? > Regards! > > > > -- > > Ricardo > Laura Best regards, g_bor