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

[Holger Levsen]

Hi,

On Freitag, 19. Februar 2016, Jérémy Bobbio wrote:
> In the case of reprotest, I would be happy to help someone write it. But
> I don't want to become its primary maintainer after the summer—there's
> already to many things that I feel I should attend to.

well, then (if someone writes it (with your help) and goes away and you dont 
maintain it) we would *have* that tool(!), which needs a new active 
maintainer. that's a nice problem to have, I think! ;-)

unless obviously you say in that case you're not gonna mentor that person…
 
> So either we need an intern that is excited enough and understand that
> they will have to be involved for more than three months, or we find
> someone with some experience that is willing to take that role.

I'd suggest we put exactly this in the description: "Lunar is only willing to 
mentor this if you (or someone else) agrees up front to maintain the tool 
after GSoC/Outreachy." - Would that satisfy your concerns?


cheers,
Holger




signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Jérémy Bobbio]

Holger Levsen:
> > 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.

I am exactly making this distinction. I assume that if you get a large
chunk of code that you are happy to merge, you will take care of its
future with the rest of jenkins.d.n.

In the case of reprotest, I would be happy to help someone write it. But
I don't want to become its primary maintainer after the summer—there's
already to many things that I feel I should attend to.

So either we need an intern that is excited enough and understand that
they will have to be involved for more than three months, or we find
someone with some experience that is willing to take that role.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Nicolas Dandrimont]

[Please Cc: me on replies]

* Holger Levsen  [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


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Holger Levsen]

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. :)

> 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? 

> 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…
 
> 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…


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Holger Levsen]

Hi,

On Mittwoch, 17. Februar 2016, Mattia Rizzolo wrote:
> I do want to reorganize my life once again starting from March (new
> semester at uni), if I manage to get through the next week, so I'll be
> available to co-mentor and help :)

yay & good luck!
 
> > what other ideas do you have?
> I'd add helping to shape the sharable db of issues we designed at the
> meeting.  I really hope that with my life reorg next month I'll able to
> get back to what I loved doing last year [0] and move that thing
> forward.

thanks, I've added some more words about this on 
https://wiki.debian.org/SummerOfCode2016/OutreachyProjects/Reproducible%20builds%20
 
of%20Debian now.
 

cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Jérémy Bobbio]

Holger Levsen:
> On Sonntag, 14. Februar 2016, Nicolas Dandrimont wrote:
> > Some of you have been waiting for it, and it's finally time: we are looking
> > for mentors and project ideas for Debian's next participation in outreach
> > programmes, from May to August 2016.
> […]
> 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. Its still listed as a
single project because I find it easier that way, but it could as well
be split into 5.

> And then I was thinking to add another project, "develop reprotest
> tool", what other ideas do you have?

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.

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.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Reiner Herrmann]

On Wed, Feb 17, 2016 at 11:57:03AM +0100, Holger Levsen wrote:
> deki, Mattia: are you ok to be listed as co-mentors?
> 
> "listed and available" :-)

Yes, I'm okay with that and available.

> And then I was thinking to add another project, "develop reprotest tool", 
> what 
> other ideas do you have?

I recently had the idea of a tool/script which checks the source of a
package for common reproducibility issues (comparable to check-all-the-things),
e.g. search for __DATE__, wrong doxygen configurations, wrong gzip/tar calls,
sorting without normalizing locale, etc...


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Esa Peuha]

On Wed, Feb 17, 2016 at 12:57 PM, Holger Levsen  wrote:
> And then I was thinking to add another project, "develop reprotest tool", what
> other ideas do you have?

Initially I parsed that as "develop a tool to help in the case
where a protest has failed and you need to protest again" :-)
I think it would be best to spell it as "repro-test" to avoid
any further confusion.

___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

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

[Holger Levsen]

Hi,

On Sonntag, 14. Februar 2016, Nicolas Dandrimont wrote:
> Some of you have been waiting for it, and it's finally time: we are looking
> for mentors and project ideas for Debian's next participation in outreach
> programmes, from May to August 2016.

many thanks for doing this once again, Nicolas!
 
> Thanks to our sponsors, we will be participating in the 12th round of
> Outreachy [1], and we have applied as a mentoring organization for the
> 2016 edition of Google Summer of Code [2].
> [1] https://wiki.debian.org/Outreachy/Round12
> [2] https://wiki.debian.org/SummerOfCode2016

I'ved added now a reproducible Builds project to [2], but not to [1], is that 
how it should be?
 
Also, I've mostly copied last years template so far, so I think we should 
update it a bit.

Lunar, are you ok to be listed as mentor (and not co-mentor)?

deki, Mattia: are you ok to be listed as co-mentors?

"listed and available" :-)

And then I was thinking to add another project, "develop reprotest tool", what 
other ideas do you have?


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds