[Reproducible-builds] Projects and mentors wanted for our participation in upcoming outreach programmes

Nicolas Dandrimont olasd at debian.org
Fri Feb 19 14:51:28 UTC 2016


[Please Cc: me on replies]

* Holger Levsen <holger at layer-acht.org> [2016-02-19 15:35:06 +0100]:

> Hi,
> 
> On Donnerstag, 18. Februar 2016, Jérémy Bobbio wrote:
> > > Also, I've mostly copied last years template so far, so I think we should
> > > update it a bit.
> > I just did that, tried to capture the different things that people can
> > do and ideas that were submitted to the list.
> 
> cool, much nicer now! thank you. :)

I agree, and your proposals look pretty exciting.

> > Its still listed as a
> > single project because I find it easier that way, but it could as well
> > be split into 5.
> 
> Nicolas, do you think it's ok as it is? 

I think it's fine as-is, and we'll always have time to split things up if the
task descriptions increase in size.

You will want to make explicit that you're willing to take more than one intern
(I suppose you'd have the bandwidth for at least 3), and that all the "What can
be worked on" tasks are not supposed to be taken on by one single intern, but
rather as independent projects for several interns.

> > My main concern about making reprotest a GSoC project is “who is going
> > to take care of the code after the summer?”  I've seen way too many
> > GSoC projects deliver something quite usable which is not followed up
> > properly and then quickly rot. So the project gets an applicant excited,
> > I really would want to lay down a proper plan for “after GSoC” as part
> > of the application process.
> 
> I'm undecided on this. I see with your point, but OTOH I would be happy if 
> $someone pops up, contributes a hunge working code chunk to jenkins.d.n.git 
> and goes away. As long as there is documentation… and in the reprotest case I 
> think finishing up the documentation could actually be an outreachy (part) 
> task…

I'm really glad that you're setting expectations properly here :)

> > All other projects currently on the list are either because they already
> > have primary maintainers that will be able to review, merge and
> > follow-up on contributions.
> 
> Yup, there are definitly better. reprotest still needs a driver…

Thanks for all you're doing, this summer is going to be great!

Cheers,
-- 
Nicolas Dandrimont
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20160219/0ce1759d/attachment.sig>


More information about the Reproducible-builds mailing list