MESSAGE
| DATE | 2020-04-04 |
| FROM | Ruben
|
| SUBJECT | Subject: [Hangout - NYLXS] Fwd: Re: QEMU participation to Google Season of
|
From hangout-bounces-at-nylxs.com Sat Apr 4 03:37:06 2020
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id EDB19163FA7;
Sat, 4 Apr 2020 03:37:03 -0400 (EDT)
X-Original-To: hangout-at-nylxs.com
Delivered-To: hangout-at-nylxs.com
Received: from stat37.mrbrklyn.com (www.mrbrklyn.com [96.57.23.83])
by mrbrklyn.com (Postfix) with ESMTP id 04632163FA0
for ; Sat, 4 Apr 2020 03:36:57 -0400 (EDT)
Date: Sat, 04 Apr 2020 00:38:35 -0400
User-Agent: K-9 Mail for Android
In-Reply-To:
References:
MIME-Version: 1.0
To: hangout-at-nylxs.com
From: Ruben
Message-ID: <05BE27B3-DA3B-4474-ACBD-DFE53D63DC9C-at-mrbrklyn.com>
Subject: [Hangout - NYLXS] Fwd: Re: QEMU participation to Google Season of
Docs
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.30rc1
Precedence: list
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Content-Type: multipart/mixed; boundary="===============0708642081=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"
--===============0708642081==
Content-Type: multipart/alternative; boundary="----EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9"
Content-Transfer-Encoding: 7bit
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
-------- Original Message --------
From: John Snow
Sent: April 3, 2020 9:37:09 PM EDT
To: "Philippe Mathieu-Daud=C3=A9" , Markus Armbruster=
, Peter Maydell , "Alex=
Benn=C3=A9e" , Stefan Hajnoczi t=2Ecom>, Aleksandar Markovic , Stef=
an Weil
Cc: Paolo Bonzini , Vladimir Sementsov-Ogievskiy sementsov-at-virtuozzo=2Ecom>, "Daniel P=2E Berrange" ,=
qemu-devel , qemu-discuss-at-nongnu=2Eorg
Subject: Re: QEMU participation to Google Season of Docs
On 4/1/20 12:37 PM, Philippe Mathieu-Daud=C3=A9 wrote:
> Hi,
>=20
> Google recently announced their 'Season of Docs' project:
> https://developers=2Egoogle=2Ecom/season-of-docs
>=20
> QEMU project seems to fit all the requirements=2E
>=20
> Who is interested in [co-]mentoring?
>=20
> Relevant links:
> https://developers=2Egoogle=2Ecom/season-of-docs/docs/admin-guide
> https://developers=2Egoogle=2Ecom/season-of-docs/docs/timeline
>=20
> [Following is extracted from the previous links:]
>=20
> Example projects:
>=20
> * Build a documentation site on a platform to be decided
> =C2=A0 by the technical writer and open source mentor, and publish
> =C2=A0 an initial set of basic documents on the site=2E Examples of
> =C2=A0 platforms include:
>=20
> =C2=A0 - A static site generator such as Hugo, Jekyll, Sphinx, =2E=2E=2E
>=20
> * Refactor the open source project's existing documentation to
> =C2=A0 provide an improved user experience or a more accessible
> =C2=A0 information architecture=2E
>=20
> * Write a conceptual overview of, or introduction to, a product
> =C2=A0 or feature=2E Often a team creates their technical documentation
> =C2=A0 from the bottom up, with the result that there's a lot of
> =C2=A0 detail but it's hard to understand the product as a whole=2E A
> =C2=A0 technical writer can fix this=2E
>=20
> * Create a tutorial for a high-profile use case=2E
>=20
> * Create a set of focused how-to guides for specific tasks=2E
>=20
> * Create a contributor=E2=80=99s guide that includes basic information
> =C2=A0 about getting started as a contributor to the open source
> =C2=A0 project, as well as any rules around licence agreements,
> =C2=A0 processes for pull requests and reviews, building the project,
> =C2=A0 and so on=2E
>=20
> Previous experience with similar programs, such as Google Summer
> of Code or others: If you or any of your mentors have taken part
> in Google Summer of Code or a similar program, mention this in
> your application=2E Describe your achievements in that program=2E
> Explain how this experience may influence the way you work in
> Season of Docs=2E
>=20
> The 2020 season of Season of Docs is limited to a maximum of
> 50 technical writing projects in total=2E
> As a guideline, we expect to accept a maximum of 2 projects
> per organization, so that we don't end up with too many
> accepted projects=2E However, if the free selection process
> doesn't fill all the slots, the Google program administrators
> may allocate additional slots to some organizations=2E
>=20
This looks like it could be very good for us=2E
My only concern is that the scope and breadth of QEMU is huge and it may
be a lot for a newcomer to tackle appropriately for top-level docs, so I
feel like it requires a mentor who has a good understanding of the broad
picture of QEMU=2E
Like the description says, we often write things bottom-up in areas of
very specific focus=2E The broad picture is sometimes harder to conjure
accurately=2E
I have a lot of opinions and thoughts on python and how docs should be
laid out, but I'm afraid I'm not so good at understanding all of the
options and "use cases" of QEMU to confidently lay out a top-level TOC=2E
Maybe if we collaborated on a TOC we could give a clear project
guideline to a GSoC/GSoD contributor=2E
(Or maybe I'm overthinking it=2E)
--js
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
tent-Type">
oma","sans-serif";padding:3=2E0pt 0in 0in 0in'>
From: John Snow <jsnow-at-redhat=2Ecom> Sent: April 3, 2020 9:37:09 PM EDT To: "Philippe Mathieu-Daud=C3=A9" <philmd-at-redhat=2Ecom>, Mark= us Armbruster <armbru-at-redhat=2Ecom>, Peter Maydell <peter=2Emaydel= l-at-linaro=2Eorg>, "Alex Benn=C3=A9e" <alex=2Ebennee-at-linaro=2Eorg>, = Stefan Hajnoczi <stefanha-at-redhat=2Ecom>, Aleksandar Markovic <alek= sandar=2Eqemu=2Edevel-at-gmail=2Ecom>, Stefan Weil <sw-at-weilnetz=2Ede>= Cc: Paolo Bonzini <pbonzini-at-redhat=2Ecom>, Vladimir Sementsov= -Ogievskiy <vsementsov-at-virtuozzo=2Ecom>, "Daniel P=2E Berrange" <b= errange-at-redhat=2Ecom>, qemu-devel <qemu-devel-at-nongnu=2Eorg>, qemu-= discuss-at-nongnu=2Eorg Subject: Re: QEMU participation to Google Season of Docs
On 4/1/20 12:37 PM, Philippe Mathieu-Daud=C3=
=A9 wrote:
x 0=2E8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi,
G=
oogle recently announced their 'Season of Docs' project:
s://developers=2Egoogle=2Ecom/season-of-docs">https://developers=2Egoogle=
=2Ecom/season-of-docs
QEMU project seems to fit all the requirem=
ents=2E
Who is interested in [co-]mentoring?
Relevant links:<=
br>uide">https://developers=2Egoogle=2Ecom/season-of-docs/docs/admin-guide=
ne">https://developers=2Egoogle=2Ecom/season-of-docs/docs/timeline
<=
br>[Following is extracted from the previous links:]
Example project=
s:
* Build a documentation site on a platform to be decided
=C2=
=A0 by the technical writer and open source mentor, and publish
=C2=A0 a=
n initial set of basic documents on the site=2E Examples of
=C2=A0 platf=
orms include:
=C2=A0 - A static site generator such as Hugo, Jekyll,=
Sphinx, =2E=2E=2E
* Refactor the open source project's existing doc=
umentation to
=C2=A0 provide an improved user experience or a more acces=
sible
=C2=A0 information architecture=2E
* Write a conceptual ove=
rview of, or introduction to, a product
=C2=A0 or feature=2E Often a tea=
m creates their technical documentation
=C2=A0 from the bottom up, with =
the result that there's a lot of
=C2=A0 detail but it's hard to understa=
nd the product as a whole=2E A
=C2=A0 technical writer can fix this=2Er>
* Create a tutorial for a high-profile use case=2E
* Create a =
set of focused how-to guides for specific tasks=2E
* Create a contri=
butor=E2=80=99s guide that includes basic information
=C2=A0 about getti=
ng started as a contributor to the open source
=C2=A0 project, as well a=
s any rules around licence agreements,
=C2=A0 processes for pull request=
s and reviews, building the project,
=C2=A0 and so on=2E
Previous=
experience with similar programs, such as Google Summer
of Code or othe=
rs: If you or any of your mentors have taken part
in Google Summer of Co=
de or a similar program, mention this in
your application=2E Describe yo=
ur achievements in that program=2E
Explain how this experience may influ=
ence the way you work in
Season of Docs=2E
The 2020 season of Sea=
son of Docs is limited to a maximum of
50 technical writing projects in =
total=2E
As a guideline, we expect to accept a maximum of 2 projects
=
per organization, so that we don't end up with too many
accepted project=
s=2E However, if the free selection process
doesn't fill all the slots, =
the Google program administrators
may allocate additional slots to some =
organizations=2E
This looks like it could be very g=
ood for us=2E
My only concern is that the scope and breadth of QEMU =
is huge and it may
be a lot for a newcomer to tackle appropriately for t=
op-level docs, so I
feel like it requires a mentor who has a good unders=
tanding of the broad
picture of QEMU=2E
Like the description says=
, we often write things bottom-up in areas of
very specific focus=2E The=
broad picture is sometimes harder to conjure
accurately=2E
I hav=
e a lot of opinions and thoughts on python and how docs should be
laid o=
ut, but I'm afraid I'm not so good at understanding all of the
options a=
nd "use cases" of QEMU to confidently lay out a top-level TOC=2E
Maybe i=
f we collaborated on a TOC we could give a clear project
guideline to a =
GSoC/GSoD contributor=2E
(Or maybe I'm overthinking it=2E)
--=
js
--
Sent from my Android device with K-9 Mail=2E Ple=
ase excuse my brevity=2E
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9--
--===============0708642081==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============0708642081==--
--===============0708642081==
Content-Type: multipart/alternative; boundary="----EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9"
Content-Transfer-Encoding: 7bit
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
-------- Original Message --------
From: John Snow
Sent: April 3, 2020 9:37:09 PM EDT
To: "Philippe Mathieu-Daud=C3=A9" , Markus Armbruster=
, Peter Maydell , "Alex=
Benn=C3=A9e" , Stefan Hajnoczi t=2Ecom>, Aleksandar Markovic , Stef=
an Weil
Cc: Paolo Bonzini , Vladimir Sementsov-Ogievskiy sementsov-at-virtuozzo=2Ecom>, "Daniel P=2E Berrange" ,=
qemu-devel , qemu-discuss-at-nongnu=2Eorg
Subject: Re: QEMU participation to Google Season of Docs
On 4/1/20 12:37 PM, Philippe Mathieu-Daud=C3=A9 wrote:
> Hi,
>=20
> Google recently announced their 'Season of Docs' project:
> https://developers=2Egoogle=2Ecom/season-of-docs
>=20
> QEMU project seems to fit all the requirements=2E
>=20
> Who is interested in [co-]mentoring?
>=20
> Relevant links:
> https://developers=2Egoogle=2Ecom/season-of-docs/docs/admin-guide
> https://developers=2Egoogle=2Ecom/season-of-docs/docs/timeline
>=20
> [Following is extracted from the previous links:]
>=20
> Example projects:
>=20
> * Build a documentation site on a platform to be decided
> =C2=A0 by the technical writer and open source mentor, and publish
> =C2=A0 an initial set of basic documents on the site=2E Examples of
> =C2=A0 platforms include:
>=20
> =C2=A0 - A static site generator such as Hugo, Jekyll, Sphinx, =2E=2E=2E
>=20
> * Refactor the open source project's existing documentation to
> =C2=A0 provide an improved user experience or a more accessible
> =C2=A0 information architecture=2E
>=20
> * Write a conceptual overview of, or introduction to, a product
> =C2=A0 or feature=2E Often a team creates their technical documentation
> =C2=A0 from the bottom up, with the result that there's a lot of
> =C2=A0 detail but it's hard to understand the product as a whole=2E A
> =C2=A0 technical writer can fix this=2E
>=20
> * Create a tutorial for a high-profile use case=2E
>=20
> * Create a set of focused how-to guides for specific tasks=2E
>=20
> * Create a contributor=E2=80=99s guide that includes basic information
> =C2=A0 about getting started as a contributor to the open source
> =C2=A0 project, as well as any rules around licence agreements,
> =C2=A0 processes for pull requests and reviews, building the project,
> =C2=A0 and so on=2E
>=20
> Previous experience with similar programs, such as Google Summer
> of Code or others: If you or any of your mentors have taken part
> in Google Summer of Code or a similar program, mention this in
> your application=2E Describe your achievements in that program=2E
> Explain how this experience may influence the way you work in
> Season of Docs=2E
>=20
> The 2020 season of Season of Docs is limited to a maximum of
> 50 technical writing projects in total=2E
> As a guideline, we expect to accept a maximum of 2 projects
> per organization, so that we don't end up with too many
> accepted projects=2E However, if the free selection process
> doesn't fill all the slots, the Google program administrators
> may allocate additional slots to some organizations=2E
>=20
This looks like it could be very good for us=2E
My only concern is that the scope and breadth of QEMU is huge and it may
be a lot for a newcomer to tackle appropriately for top-level docs, so I
feel like it requires a mentor who has a good understanding of the broad
picture of QEMU=2E
Like the description says, we often write things bottom-up in areas of
very specific focus=2E The broad picture is sometimes harder to conjure
accurately=2E
I have a lot of opinions and thoughts on python and how docs should be
laid out, but I'm afraid I'm not so good at understanding all of the
options and "use cases" of QEMU to confidently lay out a top-level TOC=2E
Maybe if we collaborated on a TOC we could give a clear project
guideline to a GSoC/GSoD contributor=2E
(Or maybe I'm overthinking it=2E)
--js
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
tent-Type">
oma","sans-serif";padding:3=2E0pt 0in 0in 0in'>
From: John Snow <jsnow-at-redhat=2Ecom> Sent: April 3, 2020 9:37:09 PM EDT To: "Philippe Mathieu-Daud=C3=A9" <philmd-at-redhat=2Ecom>, Mark= us Armbruster <armbru-at-redhat=2Ecom>, Peter Maydell <peter=2Emaydel= l-at-linaro=2Eorg>, "Alex Benn=C3=A9e" <alex=2Ebennee-at-linaro=2Eorg>, = Stefan Hajnoczi <stefanha-at-redhat=2Ecom>, Aleksandar Markovic <alek= sandar=2Eqemu=2Edevel-at-gmail=2Ecom>, Stefan Weil <sw-at-weilnetz=2Ede>= Cc: Paolo Bonzini <pbonzini-at-redhat=2Ecom>, Vladimir Sementsov= -Ogievskiy <vsementsov-at-virtuozzo=2Ecom>, "Daniel P=2E Berrange" <b= errange-at-redhat=2Ecom>, qemu-devel <qemu-devel-at-nongnu=2Eorg>, qemu-= discuss-at-nongnu=2Eorg Subject: Re: QEMU participation to Google Season of Docs
On 4/1/20 12:37 PM, Philippe Mathieu-Daud=C3=
=A9 wrote:
x 0=2E8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Hi,
G=
oogle recently announced their 'Season of Docs' project:
s://developers=2Egoogle=2Ecom/season-of-docs">https://developers=2Egoogle=
=2Ecom/season-of-docs
QEMU project seems to fit all the requirem=
ents=2E
Who is interested in [co-]mentoring?
Relevant links:<=
br>uide">https://developers=2Egoogle=2Ecom/season-of-docs/docs/admin-guide=
ne">https://developers=2Egoogle=2Ecom/season-of-docs/docs/timeline
<=
br>[Following is extracted from the previous links:]
Example project=
s:
* Build a documentation site on a platform to be decided
=C2=
=A0 by the technical writer and open source mentor, and publish
=C2=A0 a=
n initial set of basic documents on the site=2E Examples of
=C2=A0 platf=
orms include:
=C2=A0 - A static site generator such as Hugo, Jekyll,=
Sphinx, =2E=2E=2E
* Refactor the open source project's existing doc=
umentation to
=C2=A0 provide an improved user experience or a more acces=
sible
=C2=A0 information architecture=2E
* Write a conceptual ove=
rview of, or introduction to, a product
=C2=A0 or feature=2E Often a tea=
m creates their technical documentation
=C2=A0 from the bottom up, with =
the result that there's a lot of
=C2=A0 detail but it's hard to understa=
nd the product as a whole=2E A
=C2=A0 technical writer can fix this=2Er>
* Create a tutorial for a high-profile use case=2E
* Create a =
set of focused how-to guides for specific tasks=2E
* Create a contri=
butor=E2=80=99s guide that includes basic information
=C2=A0 about getti=
ng started as a contributor to the open source
=C2=A0 project, as well a=
s any rules around licence agreements,
=C2=A0 processes for pull request=
s and reviews, building the project,
=C2=A0 and so on=2E
Previous=
experience with similar programs, such as Google Summer
of Code or othe=
rs: If you or any of your mentors have taken part
in Google Summer of Co=
de or a similar program, mention this in
your application=2E Describe yo=
ur achievements in that program=2E
Explain how this experience may influ=
ence the way you work in
Season of Docs=2E
The 2020 season of Sea=
son of Docs is limited to a maximum of
50 technical writing projects in =
total=2E
As a guideline, we expect to accept a maximum of 2 projects
=
per organization, so that we don't end up with too many
accepted project=
s=2E However, if the free selection process
doesn't fill all the slots, =
the Google program administrators
may allocate additional slots to some =
organizations=2E
This looks like it could be very g=
ood for us=2E
My only concern is that the scope and breadth of QEMU =
is huge and it may
be a lot for a newcomer to tackle appropriately for t=
op-level docs, so I
feel like it requires a mentor who has a good unders=
tanding of the broad
picture of QEMU=2E
Like the description says=
, we often write things bottom-up in areas of
very specific focus=2E The=
broad picture is sometimes harder to conjure
accurately=2E
I hav=
e a lot of opinions and thoughts on python and how docs should be
laid o=
ut, but I'm afraid I'm not so good at understanding all of the
options a=
nd "use cases" of QEMU to confidently lay out a top-level TOC=2E
Maybe i=
f we collaborated on a TOC we could give a clear project
guideline to a =
GSoC/GSoD contributor=2E
(Or maybe I'm overthinking it=2E)
--=
js
--
Sent from my Android device with K-9 Mail=2E Ple=
ase excuse my brevity=2E
------EJ6Q0ZMMHOA0A6IDXQUQ611O5QA6Z9--
--===============0708642081==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============0708642081==--
|
|
