On Thu, Mar 14, 2019 at 4:18 PM Petr Bokoc <pbokoc@xxxxxxxxxx> wrote: > > On 3/12/19 11:54 AM, Brian (bex) Exelbierd wrote: > > > > On Tue, Mar 12, 2019 at 9:35 AM Robert Kratky <rkratky@xxxxxxxxx> 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 am happy to serve as the coordinator, as I do (with help) for GSoC and GCI. The part I think we need an owner for is tracking tasks and mentoring. I haven't reviewed the details, but I presume 2-4 hours a week at the beginning and less near the end. > 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. This needs to be defined by scope. I wonder if maybe we should focus on modularity or another initiative area first. We could also ask for docs on contributing to docs and translations to help us build a bootstrap. regards, bex > > > > 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@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx >> 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@xxxxxxxxxxxxxxxxxxxxxxx > > -- > Brian (bex) Exelbierd | bexelbie@xxxxxxxxxx | bex@xxxxxxxxx > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > > _______________________________________________ > docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx > > -- > Petr Bokoc (irc: pbokoc) > Technical Writer > Engineering Content Services > > Red Hat Czech, s. r. o. > Purkynova 99 > 612 45 Brno, Czech Republic > > _______________________________________________ > docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx -- Brian (bex) Exelbierd | bexelbie@xxxxxxxxxx | bex@xxxxxxxxx Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org _______________________________________________ docs mailing list -- docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to docs-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
