qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Joseph Jezak <josejx@gentoo.org>, Alexander Graf <agraf@suse.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: Summer of Code 2010
Date: Wed, 10 Mar 2010 09:12:44 +0100	[thread overview]
Message-ID: <4B97547C.4050003@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1003091935510.18499@intel-tinevez-2-302>

On 03/09/2010 07:36 PM, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 9 Mar 2010, Paolo Bonzini wrote:
>
>> On 03/09/2010 05:01 PM, Natalia Portillo wrote:
>>> Documenting QEMU's hardware model may be also a good idea for GSoC2010,
>>> as most complains about contributing QEMU are precisely that, having to
>>> study the whole code to know how to make anything new.
>>
>> Unfortunately, documentation-only projects are outside the scope of GSoC
>> (though of course it's fine if the project includes a documentation step).
>
> No, they are not. I personally know mentors (cute ones) for documentation
> projects.

http://code.google.com/opensource/gsoc/2008/faqs.html

12. Are proposals for documentation work eligible for Google Summer of Code?

While we greatly appreciate the value of documentation, this program is 
an exercise in developing code; we can't accept proposals for 
documentation-only work at this time.

Paolo

  reply	other threads:[~2010-03-10  8:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 20:20 [Qemu-devel] Summer of Code 2010 Luiz Capitulino
2010-03-08 22:53 ` Alexander Graf
2010-03-09 13:19   ` Luiz Capitulino
2010-03-09 15:44   ` Natalia Portillo
2010-03-09 15:46     ` Alexander Graf
2010-03-09 15:50       ` Natalia Portillo
2010-03-09 15:56         ` Alexander Graf
2010-03-09 16:01           ` Natalia Portillo
2010-03-09 18:07             ` [Qemu-devel] " Paolo Bonzini
2010-03-09 18:36               ` Johannes Schindelin
2010-03-10  8:12                 ` Paolo Bonzini [this message]
2010-03-10 18:31                   ` Johannes Schindelin
2010-03-11  9:37                     ` Paolo Bonzini
2010-03-09 16:48           ` [Qemu-devel] " malc
2010-03-09 16:50             ` Alexander Graf
2010-03-10 11:23           ` Jes Sorensen
2010-03-10 11:26             ` Alexander Graf
2010-03-09  9:31 ` Johannes Schindelin
2010-03-09 10:58   ` Stefan Hajnoczi
2010-03-09 13:33   ` Luiz Capitulino
2010-03-09 14:53     ` Johannes Schindelin
2010-03-09 18:51       ` Jamie Lokier
2010-03-10 20:08       ` Luiz Capitulino
2010-03-09 14:14 ` Anthony Liguori
2010-03-09 15:55   ` Natalia Portillo
2010-03-09 16:48     ` Brian Jackson
2010-03-10 20:11     ` Luiz Capitulino
2010-03-10 20:33       ` 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=4B97547C.4050003@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=josejx@gentoo.org \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).