[Buildbot-devel] Google Summer of Code

Dustin J. Mitchell dustin at v.igoro.us
Thu Mar 10 18:11:44 UTC 2011

2011/3/10 Benoît Allard <benoit at aeteurope.nl>:
> I for one would love to see some development with regards to the "multiple
> repository support" stuff ... I constantly fail to get an intern for that
> task here at work. (See [1] in case you know someone ...)
> On the other hand, I'm not sure how it looks big for a GSoC project. We
> should keep in mind that the main goal of this is to attract people to open
> source software. The accent should be made in the integration of GSoC intern
> inside the open source community. If we get some sensible coding out of it,
> can to my understanding be seen as a bonus. The real benefit of GSoC can
> however be seen in the long term when the intern stay around after GSoC and
> begin producing more interesting stuff.

I agree, and certainly the choice of project should reflect an
interest in integrating the student into the community, but that will
mean different things for different students.  For some, it might mean
that they build a user-visible feature and the thrill of "I did that!"
keeps them loyal to the project.  For others, a partially-finished
project may be best, as they will feel empowered to keep chipping away
at it after GSoC ends.  Still others may get "hooked" by learning the
internals of Buildbot and sharing that knowledge with others on the
mailing list.

If you wouldn't mind outlining "multiple repository stuff" in a bit
more detail on the FutureIdeas page, that would be great.  If I
recall, it means SourceStamps that cover multiple repositories, and
Source steps that can check out code from one such repository, among
other things?


More information about the devel mailing list