[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-docs-list
Subject: Re: google season of docs
From: Petr Bokoc <pbokoc () redhat ! com>
Date: 2019-03-14 15:17:09
Message-ID: ae642683-dd19-9bd4-a2f2-0d1ba1438ccb () redhat ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 3/12/19 11:54 AM, Brian (bex) Exelbierd wrote:
>
>
> On Tue, Mar 12, 2019 at 9:35 AM Robert Kratky <rkratky@gmail.com
> <mailto:rkratky@gmail.com>> wrote:
>
> On 03/12/2019 03:52 AM, Justin W. Flory wrote:
> > On 3/11/19 5:37 PM, Matthew Miller wrote:
> >> This seems like it has potential!
> >>
> >>
> https://opensource.googleblog.com/2019/03/introducing-season-of-docs.html
> >>
> >
> > My personal suggestion is to wait for the program to mature before
> > volunteering Fedora.
>
>
> My primary concern is having mentoring support and a well identified
> set of tasks. If Petr Bokoc can take charge here then I think we can
> be successful. I suspect that, at a minimum, we could have someone
> come in and do things like refactor the installation guide by edition
> or review and update docs for the current release. We should, imho,
> make sure this person focuses on F30, not F29 as that is what should
> be current for most if not all of the cycle.
>
> I am happy to coordinate our application and work with Petr to get it
> done.
That's my concern as well. Is there anyone here who has experience with
GSoC? I know Fedora participated before and I'm wondering about how much
commitment an internship like that requires - how much coaching, task
tracking, that kind of stuff. Bex, were you involved with that, or do
you know who was?
I'm also concerned that any tech writer will need to interact with the
wider community, not just us here in docs - someone needs to give them
info and preferably do technical reviews as well. We'll need to make
sure any relevant engineering people can (and want to) do that if we go
forward with this. In case of the install guide I'm worried that the
team is basically all Red Hatters and they'll be too busy doing their
normal work, but OTOH getting Red Hat engineers to work with us could be
easier than making sure someone from the community who only contributes
as a hobby will be available for significant amounts of time... I dunno.
>
> regards,
>
> bex
>
>
> >
> > I am skeptical. My first impression is it is a technical writing
> > certification program from Google, and open source projects act as
> > volunteer certificate proctors.
> >
> > There was a long discussion about this on the Google GSoC
> mailing list.
> > A key difference of Season of Docs is technical writers are not
> paid.
> > This excludes a group of people in most need for professional
> experience
> > and mentorship. It also sends an implied message about the value of
> > technical writing; Season of Docs is the only Google open source
> program
> > (to my knowledge) without a stipend or compensation of time
> (GSoC with
> > paid stipend, GCI with sponsored trip to Google HQ).
> >
> > My first impression was not boarding the bandwagon yet and
> observing how
> > the program matures first. I would like equal treatment for
> technical
> > writing and development work before endorsing the program.
> >
> > My intention is not to be pessimistic, but I am disappointed this
> > feedback seems unaccounted for in how Season of Docs is currently
> > described and promoted.
>
> Hi Justin,
>
> Maybe the conditions have changed since you first learned about
> the program. The FAQ [1] says:
>
> "Is Season of Docs considered an internship, a job, or any form of
> employment?"
>
> Season of Docs is an activity that the technical writer performs
> as an independent technical writer for which they are paid a
> stipend. Technical writers may choose to opt out of receiving the
> stipend."
>
> and:
>
> "Will I be paid for participating in Season of Docs?
>
> Yes. Google will provide a stipend to those technical writers who
> successfully complete the program. You can choose to opt out of
> receiving the stipend."
>
> So, maybe we could give it a thought.
>
> Regards,
> Robert
> _______________________________________________
> docs mailing list -- docs@lists.fedoraproject.org
> <mailto:docs@lists.fedoraproject.org>
> To unsubscribe send an email to docs-leave@lists.fedoraproject.org
> <mailto:docs-leave@lists.fedoraproject.org>
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
>
> --
> Brian (bex) Exelbierd | bexelbie@redhat.com
> <mailto:bexelbie@redhat.com> | bex@pobox.com <mailto:bex@pobox.com>
> Fedora Community Action & Impact Coordinator
> @bexelbie | http://www.winglemeyer.org
>
> _______________________________________________
> docs mailing list -- docs@lists.fedoraproject.org
> To unsubscribe send an email to docs-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
--
Petr Bokoc (irc: pbokoc)
Technical Writer
Engineering Content Services
Red Hat Czech, s. r. o.
Purkynova 99
612 45 Brno, Czech Republic
[Attachment #5 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 3/12/19 11:54 AM, Brian (bex)
Exelbierd wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAE6uQMvw=G9H4E7Zp2NgPVFM7f8HbZFNToMGdxSGc-w88d4VeA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Mar 12, 2019 at 9:35
AM Robert Kratky <<a href="mailto:rkratky@gmail.com"
moz-do-not-send="true">rkratky@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
03/12/2019 03:52 AM, Justin W. Flory wrote:<br>
> On 3/11/19 5:37 PM, Matthew Miller wrote:<br>
>> This seems like it has potential!<br>
>><br>
>> <a
href="https://opensource.googleblog.com/2019/03/introducing-season-of-docs.html"
rel="noreferrer" target="_blank" \
moz-do-not-send="true">https://opensource.googleblog.com/2019/03/introducing-season-of-docs.html</a><br>
>><br>
> <br>
> My personal suggestion is to wait for the program to
mature before<br>
> volunteering Fedora.</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">My primary concern is having mentoring support
and a well identified set of tasks. If Petr Bokoc can take
charge here then I think we can be successful. I suspect
that, at a minimum, we could have someone come in and do
things like refactor the installation guide by edition or
review and update docs for the current release. We should,
imho, make sure this person focuses on F30, not F29 as that
is what should be current for most if not all of the cycle.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I am happy to coordinate our application and
work with Petr to get it done.</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>That's my concern as well. Is there anyone here who has
experience with GSoC? I know Fedora participated before and I'm
wondering about how much commitment an internship like that
requires - how much coaching, task tracking, that kind of stuff.
Bex, were you involved with that, or do you know who was?<br>
</p>
<p>I'm also concerned that any tech writer will need to interact
with the wider community, not just us here in docs - someone needs
to give them info and preferably do technical reviews as well.
We'll need to make sure any relevant engineering people can (and
want to) do that if we go forward with this. In case of the
install guide I'm worried that the team is basically all Red
Hatters and they'll be too busy doing their normal work, but OTOH
getting Red Hat engineers to work with us could be easier than
making sure someone from the community who only contributes as a
hobby will be available for significant amounts of time... I
dunno.</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CAE6uQMvw=G9H4E7Zp2NgPVFM7f8HbZFNToMGdxSGc-w88d4VeA@mail.gmail.com">
<div>
<div class="gmail_quote">
<div dir="auto"><br>
</div>
<div dir="auto">regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">bex</div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> <br>
> I am skeptical. My first impression is it is a
technical writing<br>
> certification program from Google, and open source
projects act as<br>
> volunteer certificate proctors.<br>
> <br>
> There was a long discussion about this on the Google
GSoC mailing list.<br>
> A key difference of Season of Docs is technical writers
are not paid.<br>
> This excludes a group of people in most need for
professional experience<br>
> and mentorship. It also sends an implied message about
the value of<br>
> technical writing; Season of Docs is the only Google
open source program<br>
> (to my knowledge) without a stipend or compensation of
time (GSoC with<br>
> paid stipend, GCI with sponsored trip to Google HQ).<br>
> <br>
> My first impression was not boarding the bandwagon yet
and observing how<br>
> the program matures first. I would like equal treatment
for technical<br>
> writing and development work before endorsing the
program.<br>
> <br>
> My intention is not to be pessimistic, but I am
disappointed this<br>
> feedback seems unaccounted for in how Season of Docs is
currently<br>
> described and promoted.<br>
<br>
Hi Justin,<br>
<br>
Maybe the conditions have changed since you first learned
about the program. The FAQ [1] says:<br>
<br>
"Is Season of Docs considered an internship, a job, or any
form of employment?"<br>
<br>
Season of Docs is an activity that the technical writer
performs as an independent technical writer for which they
are paid a stipend. Technical writers may choose to opt out
of receiving the stipend."<br>
<br>
and:<br>
<br>
"Will I be paid for participating in Season of Docs?<br>
<br>
Yes. Google will provide a stipend to those technical
writers who successfully complete the program. You can
choose to opt out of receiving the stipend."<br>
<br>
So, maybe we could give it a thought.<br>
<br>
Regards,<br>
Robert<br>
_______________________________________________<br>
docs mailing list -- <a
href="mailto:docs@lists.fedoraproject.org" target="_blank"
moz-do-not-send="true">docs@lists.fedoraproject.org</a><br>
To unsubscribe send an email to <a
href="mailto:docs-leave@lists.fedoraproject.org"
target="_blank" \
moz-do-not-send="true">docs-leave@lists.fedoraproject.org</a><br> Fedora Code of \
Conduct: <a href="https://getfedora.org/code-of-conduct.html"
rel="noreferrer" target="_blank" \
moz-do-not-send="true">https://getfedora.org/code-of-conduct.html</a><br> List \
Guidelines: <a
href="https://fedoraproject.org/wiki/Mailing_list_guidelines"
rel="noreferrer" target="_blank" \
moz-do-not-send="true">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br> \
List Archives: <a href="https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org"
rel="noreferrer" target="_blank" \
moz-do-not-send="true">https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org</a><br>
</blockquote>
</div>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Brian (bex) Exelbierd | <a
href="mailto:bexelbie@redhat.com" target="_blank"
moz-do-not-send="true">bexelbie@redhat.com</a> | <a
href="mailto:bex@pobox.com" target="_blank"
moz-do-not-send="true">bex@pobox.com</a><br>
Fedora Community Action & Impact Coordinator<br>
@bexelbie | <a href="http://www.winglemeyer.org"
target="_blank" moz-do-not-send="true">http://www.winglemeyer.org</a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" \
wrap="">_______________________________________________ docs mailing list -- <a \
class="moz-txt-link-abbreviated" \
href="mailto:docs@lists.fedoraproject.org">docs@lists.fedoraproject.org</a> To \
unsubscribe send an email to <a class="moz-txt-link-abbreviated" \
href="mailto:docs-leave@lists.fedoraproject.org">docs-leave@lists.fedoraproject.org</a>
Fedora Code of Conduct: <a class="moz-txt-link-freetext" \
href="https://getfedora.org/code-of-conduct.html">https://getfedora.org/code-of-conduct.html</a>
List Guidelines: <a class="moz-txt-link-freetext" \
href="https://fedoraproject.org/wiki/Mailing_list_guidelines">https://fedoraproject.org/wiki/Mailing_list_guidelines</a>
List Archives: <a class="moz-txt-link-freetext" \
href="https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org">https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Petr Bokoc (irc: pbokoc)
Technical Writer
Engineering Content Services
Red Hat Czech, s. r. o.
Purkynova 99
612 45 Brno, Czech Republic</pre>
</body>
</html>
[Attachment #6 (text/plain)]
_______________________________________________
docs mailing list -- docs@lists.fedoraproject.org
To unsubscribe send an email to docs-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic