All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Privoznik <mprivozn@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	libvir-list@redhat.com, kvm <kvm@vger.kernel.org>
Subject: Re: [libvirt] Add GSoC project ideas to the wiki!
Date: Fri, 24 Feb 2012 11:38:33 +0100	[thread overview]
Message-ID: <4F4768A9.1090908@redhat.com> (raw)
In-Reply-To: <CAJSP0QUb5tB9uOz+_v2pnZWhLyjQnzHyotqxwy-BrUXU5O9dvA@mail.gmail.com>

On 24.02.2012 10:19, Stefan Hajnoczi wrote:
> This is a reminder that QEMU will apply for Google Summer of Code 2012 and we
> need project ideas and mentors.  Libvirt and kvm.ko projects are also welcome!
> 
> http://wiki.qemu.org/Google_Summer_of_Code_2012
> 
> Please add yourself to the wiki now if you want to mentor a project
> this summer.  I will file our application next week.
> 
> Thanks,
> Stefan

Hi Stefan,

Thank you for the opportunity. I was personally thinking about something
libvirt-snmp related. Nowdays, it is difficult to add new elements to
MIB, as some parts of code were generated by mib2c. Any change to MIB
requires regeneration of such source files and thus leads to loss of all
previous changes. So one thing that is coming to my mind is drop this
dependency and use libsnmp directly. But I am not sure it is worth of GSoC.

Michal

WARNING: multiple messages have this Message-ID (diff)
From: Michal Privoznik <mprivozn@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: libvir-list@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
	kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [libvirt] Add GSoC project ideas to the wiki!
Date: Fri, 24 Feb 2012 11:38:33 +0100	[thread overview]
Message-ID: <4F4768A9.1090908@redhat.com> (raw)
In-Reply-To: <CAJSP0QUb5tB9uOz+_v2pnZWhLyjQnzHyotqxwy-BrUXU5O9dvA@mail.gmail.com>

On 24.02.2012 10:19, Stefan Hajnoczi wrote:
> This is a reminder that QEMU will apply for Google Summer of Code 2012 and we
> need project ideas and mentors.  Libvirt and kvm.ko projects are also welcome!
> 
> http://wiki.qemu.org/Google_Summer_of_Code_2012
> 
> Please add yourself to the wiki now if you want to mentor a project
> this summer.  I will file our application next week.
> 
> Thanks,
> Stefan

Hi Stefan,

Thank you for the opportunity. I was personally thinking about something
libvirt-snmp related. Nowdays, it is difficult to add new elements to
MIB, as some parts of code were generated by mib2c. Any change to MIB
requires regeneration of such source files and thus leads to loss of all
previous changes. So one thing that is coming to my mind is drop this
dependency and use libsnmp directly. But I am not sure it is worth of GSoC.

Michal

  reply	other threads:[~2012-02-24 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24  9:19 Add GSoC project ideas to the wiki! Stefan Hajnoczi
2012-02-24  9:19 ` [Qemu-devel] " Stefan Hajnoczi
2012-02-24 10:38 ` Michal Privoznik [this message]
2012-02-24 10:38   ` [Qemu-devel] [libvirt] " Michal Privoznik
2012-02-24 12:07   ` Stefan Hajnoczi
2012-02-24 12:07     ` [Qemu-devel] " Stefan Hajnoczi
2012-03-12 11:36 ` [Qemu-devel] " Kevin Wolf
2012-03-16 18:43   ` Natalia Portillo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F4768A9.1090908@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.