Re: Getting into shape for GSOC 2013

Re: Getting into shape for GSOC 2013

[Konrad Rzeszutek Wilk]

On Thu, Nov 15, 2012 at 02:12:13PM +0000, Lars Kurth wrote:
> Hi everybody,
> 
> this is a gentle reminder to update
> http://wiki.xen.org/wiki/Xen_Development_Projects and to start

Let me put some extra items on the list.

> thinking about projects that are suitable for GSoC. The template to
> add items to the project page is below...
> 
> {{project
> |Project=Project description
> |Date=date of insert
> |Contact=Owner name
> |Desc=Description of
> |GSoC=Yes or No, or any other GSoC related comment
> }}
> 
> In 2012, we didn't make it into GSoC because we didn't have a good
> enough project list. We need to have a list of about 10 good project
> proposals for GSoC and present these nicely. It would be a real
> shame, if we didn't make it in 2013, in particular with some of the
> exciting work which is going on at the moment.
> 
> In 2011, when we made it our project list was at
> http://wiki.xen.org/wiki/Archived/GSoc_2011_Ideas ... Google has
> raised the bar, so we need to have
> a) Really good descriptions for our GSoC projects
> b) Pre-assign mentors to each project
> c) Ideally I would like to add biography and interest section for
> all our mentors. I can create a wiki template for mentors if it
> helps

Please do.
> 
> All this needs to be in place when we apply for GSoC as a mentoring
> organisation. The application deadline is likely in early February
> 2013, so starting on this now should leave us in good shape! If we

Aye. Feb.
> get a good list of projects together this year, we can tidy it up,
> iterate and improve in January!
> 
> Best Regards
> Lars
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

Re: Getting into shape for GSOC 2013

[Dario Faggioli]

[-- Attachment #1.1: Type: text/plain, Size: 672 bytes --]

On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
> > c) Ideally I would like to add biography and interest section for
> > all our mentors. I can create a wiki template for mentors if it
> > helps
> 
> Please do.
>
Yep, I also think this would help. Perhaps we can put something like
that in each one's user page on the Wiki
(http://wiki.xen.org/wiki/User:Dariof)

Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)



[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Getting into shape for GSOC 2013

[Konrad Rzeszutek Wilk]

On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
> > > c) Ideally I would like to add biography and interest section for
> > > all our mentors. I can create a wiki template for mentors if it
> > > helps

Ideas for GSOC:

- Support microcode update bundled in with the initrd in Xen.
  Here is the Linux side of it comes out looking:
  http://markmail.org/thread/ewrs7fa66knfwzbo

- Write Xen PV Architecture Book/Manual/whatever. We have been
  slowly going through the PV architecture and documenting it.
  It would nice to have somebody full-time doing it and asking
  questions. And then the answers would be written in this book.

Re: Getting into shape for GSOC 2013

[Wei Liu]

On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote:
> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
> > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
> > > > c) Ideally I would like to add biography and interest section for
> > > > all our mentors. I can create a wiki template for mentors if it
> > > > helps
> 
> Ideas for GSOC:
> 
> - Support microcode update bundled in with the initrd in Xen.
>   Here is the Linux side of it comes out looking:
>   http://markmail.org/thread/ewrs7fa66knfwzbo
> 
> - Write Xen PV Architecture Book/Manual/whatever. We have been
>   slowly going through the PV architecture and documenting it.
>   It would nice to have somebody full-time doing it and asking
>   questions. And then the answers would be written in this book.
> 

IIRC the documentation-only project will not be accepted.


Wei.

> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Getting into shape for GSOC 2013

[Konrad Rzeszutek Wilk]

On Mon, Jan 07, 2013 at 04:39:14PM +0000, Wei Liu wrote:
> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote:
> > On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
> > > On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
> > > > > c) Ideally I would like to add biography and interest section for
> > > > > all our mentors. I can create a wiki template for mentors if it
> > > > > helps
> > 
> > Ideas for GSOC:
> > 
> > - Support microcode update bundled in with the initrd in Xen.
> >   Here is the Linux side of it comes out looking:
> >   http://markmail.org/thread/ewrs7fa66knfwzbo
> > 
> > - Write Xen PV Architecture Book/Manual/whatever. We have been
> >   slowly going through the PV architecture and documenting it.
> >   It would nice to have somebody full-time doing it and asking
> >   questions. And then the answers would be written in this book.
> > 
> 
> IIRC the documentation-only project will not be accepted.

Good to know. Thx.

Re: [Xen-API] Getting into shape for GSOC 2013

[Anil Madhavapeddy]

On 7 Jan 2013, at 16:39, Wei Liu <wei.liu2@citrix.com> wrote:

> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote:
>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
>>>>> c) Ideally I would like to add biography and interest section for
>>>>> all our mentors. I can create a wiki template for mentors if it
>>>>> helps
>> 
>> Ideas for GSOC:
>> 
>> - Support microcode update bundled in with the initrd in Xen.
>>  Here is the Linux side of it comes out looking:
>>  http://markmail.org/thread/ewrs7fa66knfwzbo
>> 
>> - Write Xen PV Architecture Book/Manual/whatever. We have been
>>  slowly going through the PV architecture and documenting it.
>>  It would nice to have somebody full-time doing it and asking
>>  questions. And then the answers would be written in this book.
>> 
> 
> IIRC the documentation-only project will not be accepted.

So turn it into an executable specification and use that to generate
fuzz tests as well as documentation.

In particular, doing this for more than just hypercalls, but also for
the ring protocols (to find bugs in the backend drivers) would be a
useful regression harness.  Throw in all the latest additions like
multipage rings and various frontend options, and you will certainly
shake out a few bugs (I just accidentally found a netback crash that
I'm reporting separately).

-anil

Re: [Xen-API] Getting into shape for GSOC 2013

[Wei Liu]

On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote:
> On 7 Jan 2013, at 16:39, Wei Liu <wei.liu2@citrix.com> wrote:
> 
> > On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote:
> >> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
> >>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
> >>>>> c) Ideally I would like to add biography and interest section for
> >>>>> all our mentors. I can create a wiki template for mentors if it
> >>>>> helps
> >> 
> >> Ideas for GSOC:
> >> 
> >> - Support microcode update bundled in with the initrd in Xen.
> >>  Here is the Linux side of it comes out looking:
> >>  http://markmail.org/thread/ewrs7fa66knfwzbo
> >> 
> >> - Write Xen PV Architecture Book/Manual/whatever. We have been
> >>  slowly going through the PV architecture and documenting it.
> >>  It would nice to have somebody full-time doing it and asking
> >>  questions. And then the answers would be written in this book.
> >> 
> > 
> > IIRC the documentation-only project will not be accepted.
> 
> So turn it into an executable specification and use that to generate
> fuzz tests as well as documentation.
> 
> In particular, doing this for more than just hypercalls, but also for
> the ring protocols (to find bugs in the backend drivers) would be a
> useful regression harness.  Throw in all the latest additions like
> multipage rings and various frontend options, and you will certainly
> shake out a few bugs (I just accidentally found a netback crash that
> I'm reporting separately).
> 

Anil could you put this idea on the project list if you're interested. 

http://wiki.xen.org/wiki/Xen_Development_Projects

We will start polishing the list for GSoC soon.


Wei.

Re: [Xen-API] Getting into shape for GSOC 2013

[Anil Madhavapeddy]

On 9 Jan 2013, at 16:12, Wei Liu <Wei.Liu2@citrix.com> wrote:

> On Wed, 2013-01-09 at 15:44 +0000, Anil Madhavapeddy wrote:
>> On 7 Jan 2013, at 16:39, Wei Liu <wei.liu2@citrix.com> wrote:
>> 
>>> On Mon, 2013-01-07 at 16:27 +0000, Konrad Rzeszutek Wilk wrote:
>>>> On Thu, Dec 20, 2012 at 12:31:23AM +0100, Dario Faggioli wrote:
>>>>> On Wed, 2012-12-19 at 16:44 -0500, Konrad Rzeszutek Wilk wrote: 
>>>>>>> c) Ideally I would like to add biography and interest section for
>>>>>>> all our mentors. I can create a wiki template for mentors if it
>>>>>>> helps
>>>> 
>>>> Ideas for GSOC:
>>>> 
>>>> - Support microcode update bundled in with the initrd in Xen.
>>>> Here is the Linux side of it comes out looking:
>>>> http://markmail.org/thread/ewrs7fa66knfwzbo
>>>> 
>>>> - Write Xen PV Architecture Book/Manual/whatever. We have been
>>>> slowly going through the PV architecture and documenting it.
>>>> It would nice to have somebody full-time doing it and asking
>>>> questions. And then the answers would be written in this book.
>>>> 
>>> 
>>> IIRC the documentation-only project will not be accepted.
>> 
>> So turn it into an executable specification and use that to generate
>> fuzz tests as well as documentation.
>> 
>> In particular, doing this for more than just hypercalls, but also for
>> the ring protocols (to find bugs in the backend drivers) would be a
>> useful regression harness.  Throw in all the latest additions like
>> multipage rings and various frontend options, and you will certainly
>> shake out a few bugs (I just accidentally found a netback crash that
>> I'm reporting separately).
>> 
> 
> Anil could you put this idea on the project list if you're interested. 
> 
> http://wiki.xen.org/wiki/Xen_Development_Projects
> 
> We will start polishing the list for GSoC soon.

I put a similar one up a few months ago ("Fuzz testing Xen with Mirage").

-anil

Getting into shape for GSOC 2013

[Lars Kurth]

Hi everybody,

this is a gentle reminder to update 
http://wiki.xen.org/wiki/Xen_Development_Projects and to start thinking 
about projects that are suitable for GSoC. The template to add items to 
the project page is below...

{{project
|Project=Project description
|Date=date of insert
|Contact=Owner name
|Desc=Description of
|GSoC=Yes or No, or any other GSoC related comment
}}

In 2012, we didn't make it into GSoC because we didn't have a good 
enough project list. We need to have a list of about 10 good project 
proposals for GSoC and present these nicely. It would be a real shame, 
if we didn't make it in 2013, in particular with some of the exciting 
work which is going on at the moment.

In 2011, when we made it our project list was at 
http://wiki.xen.org/wiki/Archived/GSoc_2011_Ideas ... Google has raised 
the bar, so we need to have
a) Really good descriptions for our GSoC projects
b) Pre-assign mentors to each project
c) Ideally I would like to add biography and interest section for all 
our mentors. I can create a wiki template for mentors if it helps

All this needs to be in place when we apply for GSoC as a mentoring 
organisation. The application deadline is likely in early February 2013, 
so starting on this now should leave us in good shape! If we get a good 
list of projects together this year, we can tidy it up, iterate and 
improve in January!

Best Regards
Lars