All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: Call for Google Summer of Code 2021 project ideas
Date: Wed, 13 Jan 2021 10:19:34 +0100	[thread overview]
Message-ID: <87pn29kxcp.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <92903d8d-24c4-5177-67c9-1690ea794739@redhat.com> (John Snow's message of "Tue, 12 Jan 2021 16:10:48 -0500")

John Snow <jsnow@redhat.com> writes:

> On 1/11/21 6:47 AM, Stefan Hajnoczi wrote:
>> Dear QEMU, KVM, and rust-vmm community,
>> QEMU will apply for Google Summer of Code
>> (https://summerofcode.withgoogle.com/) again this year.  This internship
>> program offers paid, 10-week, remote work internships for
>> contributing to open source.  QEMU can act as an umbrella organization
>> for KVM kernel and rust-vmm projects too.
>> Please post project ideas on the QEMU wiki before February 14th:
>> https://wiki.qemu.org/Google_Summer_of_Code_2021
>> What's new this year:
>>   * The number of internship hours has been halved to 175 hours over
>>     10 weeks. Project ideas must be smaller to fit and students will have
>>     more flexibility with their working hours.
>>   * Eligibility has been expanded to include "licensed coding school or
>>     similar type of program".
>> Good project ideas are suitable for 175 hours (10 weeks half-day)
>> work by a
>> competent programmer who is not yet familiar with the codebase.  In
>> addition, they are:
>>   * Well-defined - the scope is clear
>>   * Self-contained - there are few dependencies
>>   * Uncontroversial - they are acceptable to the community
>>   * Incremental - they produce deliverables along the way
>> Feel free to post ideas even if you are unable to mentor the
>> project.
>> It doesn't hurt to share the idea!
>> 
>
> I have one that is probably way too ambitious, but requires a
> particular skillset that might be of good interest to a student that
> has some experience in the area already.
>
> The idea is for a TUI qmp-shell (maybe using urwid?) to create an
> irssi-like REPL interface for QMP. The idea would be to mimic the 
> mitmproxy TUI interface (Check it out if you haven't!)
>
> All the ideas below are extremely tentative to give a basic gist of
> what I mean; exact layouts/hotkeys/etc are for the sake of explanation
> only.
>
> Essentially, I want an interface like this:
>
> -----------------------------------------------------------
> | QMP Mode                                                |
> |=========================================================|
> |                                                         |
> | Welcome to the Qemu Machine Protocol shell.             |
> | Please type /help or Ctrl+H to see available commands.  |
> |                                                         |
> |                                                         |
> |                                                         |
> |---------------------------------------------------------|
> | >                                                       |
> -----------------------------------------------------------
>
> commands are entered in the bottom and appear in a log window above,
> appearing most-recent last, like irssi works.
>
> As an example, let's say we issue block-dirty-bitmap-add:
>
> --------------------------------------------------------
> | > block-dirty-bitmap-add node=ide0hd0 name=mybitmap0 |
> --------------------------------------------------------
>
> (...syntax up for debate...! We want something easy to parse, but easy
> to type. For structured data, that's Hard.)

"Hard" is a red flag for such a brief internship.  We need to solve or
somehow exclude this design problem before we hand the task to the
student.

[...]



  parent reply	other threads:[~2021-01-13  9:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 11:47 Call for Google Summer of Code 2021 project ideas Stefan Hajnoczi
2021-01-12 21:10 ` John Snow
2021-01-13  8:53   ` Stefan Hajnoczi
2021-01-13 18:59     ` qmp-shell TUI (was: Re: Call for Google Summer of Code 2021 project ideas) John Snow
2021-01-14 13:52       ` Stefan Hajnoczi
2021-01-14 13:59         ` Daniel P. Berrangé
2021-01-14 15:02           ` Kevin Wolf
2021-01-14 15:22             ` Daniel P. Berrangé
2021-01-14 16:49               ` Stefan Hajnoczi
2021-01-14 16:55                 ` Daniel P. Berrangé
2021-01-14 17:14                   ` Stefan Hajnoczi
2021-01-14 17:24                     ` Daniel P. Berrangé
2021-01-14 16:48             ` Stefan Hajnoczi
2021-01-14 17:48         ` John Snow
2021-01-13  9:19   ` Markus Armbruster [this message]
2021-01-13 19:05     ` Call for Google Summer of Code 2021 project ideas John Snow
2021-01-14 12:29       ` Markus Armbruster
2021-01-14 14:57         ` Kevin Wolf
2021-01-14 16:36         ` John Snow
2021-01-15 16:31           ` Kashyap Chamarthy
2021-02-15 11:05           ` Paolo Bonzini
2021-02-15 21:47             ` John Snow
2021-02-12 13:22 ` [Rust-VMM] " Florescu, Andreea
2021-02-12 13:51   ` Sergio Lopez
2021-02-12 13:51     ` Sergio Lopez
2021-02-17 11:20   ` Stefan Hajnoczi
2021-02-17 11:20     ` Stefan Hajnoczi
2021-02-18 11:49     ` Andreea Florescu
2021-02-18 17:43       ` Stefan Hajnoczi
2021-02-18 17:43         ` Stefan Hajnoczi

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=87pn29kxcp.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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.