unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Seeking Outreachy internship project proposals
Date: Wed, 11 Sep 2019 12:44:41 +0200	[thread overview]
Message-ID: <CAE4v=pgH+CJ4m7RXMQMsvgLv5Zv9tnOVGVdAaif8Ekziod2A=g@mail.gmail.com> (raw)
In-Reply-To: <875zm3b1jd.fsf@cbaines.net>

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

Hello,


>> > I would like to ask Ludo to file a request for a sub-repository to
> >> > savannah-hackers, so that
> >> > we could move the code there. Wdyt?
> >>
> >> That works for me :)
> >>
>

This is now done.


> >> I guess this kind of thing relates to the "Project Contribution
> >> Information" part of the proposal. I think there's some other bits of
> >> preparation to do for this, like:
>

I believe you could adopt some of the contribution information from Guix
now,
that this is officially associated with the community. You could also modify
the community information to match with Guix. Does that make sense?


> >>
> >>  - Making sure the service is actually running publicly somewhere (maybe
> >>    milano-guix-1 if that's back working, maybe somewhere else if not)
> >>
>

This is also done.


> >>  - Generating a small sample database that can be used for local
> >>    development
> >>
>

This is still needed.


> >>  - Writing some step-by-step instructions for running the service
> >>    locally
> >>
>

Did you have time to do this?


> > The proposal is just a rough project outline, which can be refined later,
> > but should be in its final form by the 24, so that applicants reading it
> > can have a rough estimate of the timeline, and of the milestones.
>
> Ok, that sounds fine.
>
> > Having starter tasks defined is actually outside the scope of Outreachy,
> but
> > an applicant must have a valid contribution to the project by the time of
> > intern
> > selection. These are also very helpful for you to know what it would be
> > like to with
> > a given intern. I would say there is no strict timeline on this, but very
> > much reduces
> > the communication overhead at the beginning, thus it is easier for you,
> and
> > more
> > attractive to the applicants. Wdyt?
>


>
> That all sounds fine to me, I've updated the application with some tasks
> which I think would make good initial contributions. I'm not sure how
> relevant I can make them to the project (without making them too
> complicated), so I've just been looking for small improvements to the
> exisiting functionality (mostly specifying JSON responses, where I
> haven't).
>

I have seen the initial tasks, and they look good to me.


> >> > Also, Ricardo brought to my attention the following things, that could
>
> ...
>
> >> Some beginning, and sub-tasks need outlining, and once that is more
> >> understood, hopefully we'll be in a better place to check if the above
> >> is a reasonable goal. I think it would be also good to add some stretch
> >> goals as well.
> >>
>

From the main body of intern tasks, it would be nice to have the goals
stated
a bit more exlicitly, and to divide the work into stages a bit.


> >
> > Yes, stretch tasks also make sense. Later the applicants will also be
> asked
> > to
> > a timeline. It is nice if they plan some spare time in their schedule, so
> > that they
> > can stay on deadline, and be less stressed about it.
>
> Sounds good :)
>

Otherwise the proposal now looks to be in really good shape, so I wiil
approve it
once we have this few points sorted out.

Best regards,
g_bor

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

[-- Attachment #2: Type: text/html, Size: 5408 bytes --]

  reply	other threads:[~2019-09-11 10:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 11:18 Seeking Outreachy internship project proposals Gábor Boskovits
2019-08-27 15:20 ` Ricardo Wurmus
2019-09-03 12:30 ` Ludovic Courtès
2019-09-03 12:32   ` Gábor Boskovits
2019-09-03 20:01   ` Laura Lazzati
2019-09-04 11:45 ` Christopher Baines
2019-09-04 12:03   ` Gábor Boskovits
2019-09-04 14:08     ` Christopher Baines
2019-09-04 20:06       ` Gábor Boskovits
2019-09-05 19:01         ` Gábor Boskovits
2019-09-06  6:55           ` Christopher Baines
2019-09-08  8:28             ` Gábor Boskovits
2019-09-08  9:05               ` Christopher Baines
2019-09-11 10:44                 ` Gábor Boskovits [this message]
2019-09-17 15:10                   ` Gábor Boskovits
2019-09-18  7:33                     ` Christopher Baines
2019-09-20  8:19                       ` Gábor Boskovits
2019-09-21 12:38                         ` Christopher Baines
2019-09-21 15:55                   ` Christopher Baines
2019-09-21 17:47                     ` Gábor Boskovits
2019-09-08  8:32             ` Gábor Boskovits
2019-09-08  9:01               ` Christopher Baines
2019-09-08 21:15               ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to='CAE4v=pgH+CJ4m7RXMQMsvgLv5Zv9tnOVGVdAaif8Ekziod2A=g@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).