From: Ingo Schwarze <schwarze@usta.de>
To: Stephen Gregoratto <dev@sgregoratto.me>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Google Season of Docs
Date: Wed, 17 Apr 2019 02:01:50 +0200 [thread overview]
Message-ID: <20190417000150.GF88430@athene.usta.de> (raw)
In-Reply-To: <20190416233120.xpejittxfbt743o7@BlackBox>
Hi Stephen,
Stephen Gregoratto wrote on Wed, Apr 17, 2019 at 09:31:20AM +1000:
> Much like the Summer of Code,
If i remember correctly, OpenBSD participated one time in the GSoC -
and rued it. The administrative overhead vastly exceeded the benefit.
> Google is now sponsoring a Season of
> Docs[1] to improve Open Source documentation. There's still time for
> organisations to submit applications for entry (until April 23 20:00
> UTC).
>
> The application details for projects are available here[2], but the gist
> is as follows:
> - Get at least two "administrators" to oversee your projects
That's far beyond the means of the mandoc project.
I think it would even exceed the capacity of the OpenBSD project.
> - Create a list of writing projects and then assign at least two
> mentors for each of them. There's a couple of project ideas that
> Google suggest here[3], but I'm sure you have your own.
> - When you have finalised your list, publish them online.
> - Submit your application and sign up your admins, mentors before the
> 23rd.
>
> After this, technical writers apply and get in contact with orgs.
> There's too much info here for me to summarise, so I'll just link the
> timeline[4]. Note that the actual writing period is Sep 2-Nov 22.
>
> Since I'm singing up
Singing up? Do you mean "signing up"? But even then, i'm not sure i
understand. How can you sign up? Individuals can only start signing
up after April 30 if i understand the timeline correctly.
> I thought I'd let you'd know, seems like something
> you might be interested in.
Thanks for the pointer, i hadn't heard about it before. Sure, it
no doubt feels even less valuable than GSoC itself for reaping any
actual benefit - but all the same, hearing about what kind of
bureaucracy large corporations are erecting in the vicinity of our
project is no doubt interesting and entertaining. :-)
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2019-04-17 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 23:31 Stephen Gregoratto
2019-04-17 0:01 ` Ingo Schwarze [this message]
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=20190417000150.GF88430@athene.usta.de \
--to=schwarze@usta.de \
--cc=dev@sgregoratto.me \
--cc=discuss@mandoc.bsd.lv \
/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).