Gergely Nagy | 16 Feb 2012 13:57
Gravatar

Call for Projects & Mentors for Google Summer of Code 2012

Hi!

Debian is applying as mentoring organization to the Google Summer of
Code (GSoC) this year, as we have done previous years [0][1]. In the
next few weeks we should have the full list of possible projects ready.

This year, we're not just calling for projects and mentors, but try to
approach various teams that we think could benefit greatly from the
summer of code. We believe that Lintian, with it's ever growing requests
for new checks, the desire to have a more complete test suite, could
offer a good project or two for perl-sawwy students this year.

The benefits include (but are not limited to) recruiting helping hands
to work on Lintian, a very important part of the Debian ecosystem, which
will, in the long run, make the lives of the lintian maintainers
easier. Furthermore, this would also help Debian as a whole, and improve
the quality of our packaging (of which we're famous of) even more.

Of course, all this comes with a price: for each project, we need a good
description, that will attract students, and a mentor (or more!) who can
respond to students in a timely manner during the summer. Since this is
a hard task to accomplish, we, as admins are more than happy to help you
develop a stunning project for the summer.

Even if your time is limited, please do not feel discouraged, as every
idea counts, and mentoring is not *that* a time consuming job. Do let
us know if you have anything in mind, anything that needs doing, and
which students could work on!

In case we stirred your interest, please have a look at the proposal
(Continue reading)

Stefano Zacchiroli | 16 Feb 2012 16:58
Picon
Favicon

Re: Call for Projects & Mentors for Google Summer of Code 2012

On Thu, Feb 16, 2012 at 01:57:04PM +0100, Gergely Nagy wrote:
> This year, we're not just calling for projects and mentors, but try to
> approach various teams that we think could benefit greatly from the
> summer of code.

Awesome idea, thanks for pushing it forward!

Not sure if it'd be a good idea or not, but we've never really managed
to collect and maintain a list of "easy hacks" that could be useful for
Google Code-In and, more generally, to ease the access path to Debian.

We've some technical support for it
http://wiki.debian.org/qa.debian.org/GiftTag , but we never managed to
encourage people to tag bugs and then to use the list of tagged bugs in
any useful way. (And possibly the name "gift" is not really appropriate
either...)

Given that you're thinking anyhow to teams who might have GSoC-like
tasks, it *might* make sense to also point them to the gift thingy and
encourage them to tags bug accordingly.  But it could also have the
disadvantage of diverting attention to two conflicting initiatives: GSoC
planning and "easy hacks" tagging.

I just wanted to mention this here, as a possibility, but I leave it to
you whether it'd be a good idea to mention both things when contacting
teams or not.

Cheers.
--

-- 
Stefano Zacchiroli     zack <at> {upsilon.cc,pps.jussieu.fr,debian.org} . o .
(Continue reading)

Gergely Nagy | 20 Feb 2012 10:18
Picon
Gravatar

Re: Call for Projects & Mentors for Google Summer of Code 2012

Stefano Zacchiroli <zack@...> writes:

xx> Not sure if it'd be a good idea or not, but we've never really managed
> to collect and maintain a list of "easy hacks" that could be useful for
> Google Code-In and, more generally, to ease the access path to Debian.
>
> We've some technical support for it
> http://wiki.debian.org/qa.debian.org/GiftTag , but we never managed to
> encourage people to tag bugs and then to use the list of tagged bugs in
> any useful way. (And possibly the name "gift" is not really appropriate
> either...)
>
> Given that you're thinking anyhow to teams who might have GSoC-like
> tasks, it *might* make sense to also point them to the gift thingy and
> encourage them to tags bug accordingly.  But it could also have the
> disadvantage of diverting attention to two conflicting initiatives: GSoC
> planning and "easy hacks" tagging.
>
> I just wanted to mention this here, as a possibility, but I leave it to
> you whether it'd be a good idea to mention both things when contacting
> teams or not.

This is a good idea, perhaps it would be worth an easy GSoC project to
make it more visible: modify the BTS, the PTS and whatever else we can
think of, to show gift tagged bugs more visibly. Also writing a few
guidelines on what kind of bugs are appropriate for the tag would also
help, something a bit more elaborate than what's on the wiki at the
moment.

What do you think?
(Continue reading)

Stefano Zacchiroli | 22 Feb 2012 13:50
Picon
Favicon

Re: Call for Projects & Mentors for Google Summer of Code 2012

On Mon, Feb 20, 2012 at 10:18:45AM +0100, Gergely Nagy wrote:
> This is a good idea, perhaps it would be worth an easy GSoC project to
> make it more visible: modify the BTS, the PTS and whatever else we can
> think of, to show gift tagged bugs more visibly. Also writing a few
> guidelines on what kind of bugs are appropriate for the tag would also
> help, something a bit more elaborate than what's on the wiki at the
> moment.
> 
> What do you think?

I think it'd be totally worth to invest some time on making "easy hacks"
like approaches work for us. I'm not sure what that would mean in
practice, though. I've had for sometime on my TODO list to study the
experiences of other projects on how they maintain and advertise such
lists, to try copy in Debian best practices that work for others.

Haven't done so yet, I'm a bit at loss at defining the boundaries of the
GSoC project you suggest.  I still think it's a great idea, but I'm
unable to determine if it'd be something a GSoC student would be able to
work upon or not...

Any taker for trying to better define the scope of such a project?

Cheers.
--

-- 
Stefano Zacchiroli     zack <at> {upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences   ......   http://upsilon.cc/zack   ......   . . o
Debian Project Leader    .......    <at> zack on identi.ca   .......    o o o
« the first rule of tautology club is the first rule of tautology club »
(Continue reading)

Stefano Zacchiroli | 7 Mar 2012 17:20
Picon
Favicon

Re: Call for Projects & Mentors for Google Summer of Code 2012

On Mon, Feb 20, 2012 at 10:18:45AM +0100, Gergely Nagy wrote:
> xx> Not sure if it'd be a good idea or not, but we've never really managed
> > to collect and maintain a list of "easy hacks" that could be useful for
> > Google Code-In and, more generally, to ease the access path to Debian.
> >
> > We've some technical support for it
> > http://wiki.debian.org/qa.debian.org/GiftTag , but we never managed to
> > encourage people to tag bugs and then to use the list of tagged bugs in
> > any useful way. (And possibly the name "gift" is not really appropriate
> > either...)
> >
> > Given that you're thinking anyhow to teams who might have GSoC-like
> > tasks, it *might* make sense to also point them to the gift thingy and
> > encourage them to tags bug accordingly.  But it could also have the
> > disadvantage of diverting attention to two conflicting initiatives: GSoC
> > planning and "easy hacks" tagging.
> >
> > I just wanted to mention this here, as a possibility, but I leave it to
> > you whether it'd be a good idea to mention both things when contacting
> > teams or not.
> 
> This is a good idea, perhaps it would be worth an easy GSoC project to
> make it more visible: modify the BTS, the PTS and whatever else we can
> think of, to show gift tagged bugs more visibly. Also writing a few
> guidelines on what kind of bugs are appropriate for the tag would also
> help, something a bit more elaborate than what's on the wiki at the
> moment.

Actually, I thought a bit more about it, and it might be the case that
what we actually want is getting in touch with people who already know
(Continue reading)

Asheesh Laroia | 26 Apr 2012 23:02

Re: Call for Projects & Mentors for Google Summer of Code 2012

On Wed, 7 Mar 2012, Stefano Zacchiroli wrote:

> On Mon, Feb 20, 2012 at 10:18:45AM +0100, Gergely Nagy wrote:
>> xx> Not sure if it'd be a good idea or not, but we've never really managed
>>> to collect and maintain a list of "easy hacks" that could be useful for
>>> Google Code-In and, more generally, to ease the access path to Debian.
>>>
>>> We've some technical support for it
>>> http://wiki.debian.org/qa.debian.org/GiftTag , but we never managed to
>>> encourage people to tag bugs and then to use the list of tagged bugs in
>>> any useful way. (And possibly the name "gift" is not really appropriate
>>> either...)
>>>
>>> Given that you're thinking anyhow to teams who might have GSoC-like
>>> tasks, it *might* make sense to also point them to the gift thingy and
>>> encourage them to tags bug accordingly.  But it could also have the
>>> disadvantage of diverting attention to two conflicting initiatives: GSoC
>>> planning and "easy hacks" tagging.
>>>
>>> I just wanted to mention this here, as a possibility, but I leave it to
>>> you whether it'd be a good idea to mention both things when contacting
>>> teams or not.
>>
>> This is a good idea, perhaps it would be worth an easy GSoC project to
>> make it more visible: modify the BTS, the PTS and whatever else we can
>> think of, to show gift tagged bugs more visibly. Also writing a few
>> guidelines on what kind of bugs are appropriate for the tag would also
>> help, something a bit more elaborate than what's on the wiki at the
>> moment.
>
(Continue reading)

Niels Thykier | 19 Feb 2012 16:38

Re: Call for Projects & Mentors for Google Summer of Code 2012

On 2012-02-16 13:57, Gergely Nagy wrote:
> Hi!
> 
> [...]
> 

Hi,

> This year, we're not just calling for projects and mentors, but try to
> approach various teams that we think could benefit greatly from the
> summer of code. We believe that Lintian, with it's ever growing requests
> for new checks, the desire to have a more complete test suite, could
> offer a good project or two for perl-sawwy students this year.
> 

I think we can dig out a project or two.   Actually, I already did...
Some of you may remember I suggested that we created the
"lintian-harness" frontend[1]. :)

As I understood Ana on IRC, it could be useful to divide the project
into two parts.  A small "get started" part and a larger "the real deal"
part.  I was thinking something like:

 1. part harness test-suite ("get started")
    - I got some sample scripts that might be useful for the student
      get started.
 2. part rewritten harness frontend ("the real deal")
    - Based on the spec in [1], but possible with some changes to it.

Do people think this is a reasonable size for a project?
(Continue reading)

Russ Allbery | 19 Feb 2012 17:45
Picon
Favicon

Re: Call for Projects & Mentors for Google Summer of Code 2012

Niels Thykier <niels@...> writes:

> I think we can dig out a project or two.  Actually, I already did...
> Some of you may remember I suggested that we created the
> "lintian-harness" frontend[1]. :)

> As I understood Ana on IRC, it could be useful to divide the project
> into two parts.  A small "get started" part and a larger "the real deal"
> part.  I was thinking something like:

>  1. part harness test-suite ("get started")
>     - I got some sample scripts that might be useful for the student
>       get started.
>  2. part rewritten harness frontend ("the real deal")
>     - Based on the spec in [1], but possible with some changes to it.

> Do people think this is a reasonable size for a project?

Yeah, I think that's a reasonably-sized project.  (And it would be great
to have that done!)

--

-- 
Russ Allbery (rra@...)               <http://www.eyrie.org/~eagle/>

Niels Thykier | 20 Feb 2012 10:14

Re: Call for Projects & Mentors for Google Summer of Code 2012

On 2012-02-19 17:45, Russ Allbery wrote:
> Niels Thykier <niels@...> writes:
> 
>> I think we can dig out a project or two.  Actually, I already did...
>> Some of you may remember I suggested that we created the
>> "lintian-harness" frontend[1]. :)
> 
>> As I understood Ana on IRC, it could be useful to divide the project
>> into two parts.  A small "get started" part and a larger "the real deal"
>> part.  I was thinking something like:
> 
>>  1. part harness test-suite ("get started")
>>     - I got some sample scripts that might be useful for the student
>>       get started.
>>  2. part rewritten harness frontend ("the real deal")
>>     - Based on the spec in [1], but possible with some changes to it.
> 
>> Do people think this is a reasonable size for a project?
> 
> Yeah, I think that's a reasonably-sized project.  (And it would be great
> to have that done!)
> 

Okay, so I have tried to come up with a project description for [1].
This is what I got so far (including "inline wiki markup"):

<project>
Create Lintian reports frontend
===============================

(Continue reading)

Ana Guerrero | 20 Feb 2012 10:52
Picon
Favicon

Re: Call for Projects & Mentors for Google Summer of Code 2012

On Mon, Feb 20, 2012 at 10:14:31AM +0100, Niels Thykier wrote:

[...]
> 
> Okay, so I have tried to come up with a project description for [1].
> This is what I got so far (including "inline wiki markup"):
> 
> <project>
> Create Lintian reports frontend
> ===============================
> 
> The static package analysis tool, Lintian, is currently being run on
> all packages in Debian.  It has a tool called "harness" to publish the
> results of its quality checks on lintian.debian.org.
> 
> Currently, "harness" is an "internal" tool to generate these reports,
> but we believe it would be useful to Debian as well as its many derivatives
> to have a propper tool for generating these reports.
> 
> The project will consist of two parts.  Part 1 will be to create a
> black box test suite to test the current harness tool.  Part 2 will be
> to rewrite "harness" into a proper tool.
> 
> 
>  * Confirmed Mentor: Niels Thykier
>  * How to contact the mentor:
>    * mail: niels@...,
>    * IRC nick: nthykier
>  * Co-mentors:  Any takers? :)
>  * Deliverables of the project:
(Continue reading)

Gergely Nagy | 20 Feb 2012 10:58
Picon
Gravatar

Re: Call for Projects & Mentors for Google Summer of Code 2012

Niels Thykier <niels@...> writes:

>> Yeah, I think that's a reasonably-sized project.  (And it would be great
>> to have that done!)

Seconded!

> Create Lintian reports frontend
> ===============================
>
> The static package analysis tool, Lintian, is currently being run on
> all packages in Debian.  It has a tool called "harness" to publish the
> results of its quality checks on lintian.debian.org.
>
> Currently, "harness" is an "internal" tool to generate these reports,
> but we believe it would be useful to Debian as well as its many derivatives
> to have a propper tool for generating these reports.

s/propper/proper/

> The project will consist of two parts.  Part 1 will be to create a
> black box test suite to test the current harness tool.  Part 2 will be
> to rewrite "harness" into a proper tool.

I'd rewrite the above like this:

,----
| The project is made up of two parts: the first part is to create a black
| box test suite to test the current harness tool, the second is to
| rewrite "harness" into a proper tool that is usable without a pilot
(Continue reading)

Niels Thykier | 20 Feb 2012 11:59

Re: Call for Projects & Mentors for Google Summer of Code 2012

On 2012-02-20 10:58, Gergely Nagy wrote:
> [...]
> 
>> Create Lintian reports frontend
>> ===============================
>>
>> The static package analysis tool, Lintian, is currently being run on
>> all packages in Debian.  It has a tool called "harness" to publish the
>> results of its quality checks on lintian.debian.org.
>>
>> Currently, "harness" is an "internal" tool to generate these reports,
>> but we believe it would be useful to Debian as well as its many derivatives
>> to have a propper tool for generating these reports.
> 
> s/propper/proper/
> 

Fixed.

>> The project will consist of two parts.  Part 1 will be to create a
>> black box test suite to test the current harness tool.  Part 2 will be
>> to rewrite "harness" into a proper tool.
> 
> I'd rewrite the above like this:
> 
> ,----
> | The project is made up of two parts: the first part is to create a black
> | box test suite to test the current harness tool, the second is to
> | rewrite "harness" into a proper tool that is usable without a pilot
> | license.
(Continue reading)

Gergely Nagy | 20 Feb 2012 12:33
Picon
Gravatar

Re: Call for Projects & Mentors for Google Summer of Code 2012

Niels Thykier <niels@...> writes:

>>> The project will consist of two parts.  Part 1 will be to create a
>>> black box test suite to test the current harness tool.  Part 2 will be
>>> to rewrite "harness" into a proper tool.
>> 
>> I'd rewrite the above like this:
>> 
>> ,----
>> | The project is made up of two parts: the first part is to create a black
>> | box test suite to test the current harness tool, the second is to
>> | rewrite "harness" into a proper tool that is usable without a pilot
>> | license.
>> `----
>> 
>> This means pretty much the same thing, but is more catchy, and easier to
>> read, in my opinion. O:)
>> 
>
> Did that, still have to incorporate Ana's suggestion on the "expected
> length" of these parts.  Maybe, "We expect the new harness frontend will
> be most time consuming part."?

How about: "The first (shorter, introductory) part is to ..., the
second, most time consuming part is to ..." ?

This both says that the first is a short getting yourself wet kind of
thing, while the second part is The Real Deal.

>>>  * Co-mentors:  Any takers? :)
(Continue reading)


Gmane