If someone would be interested in leading this I think this would be very
valuable for the yt docs.
---------- Forwarded message ---------
From: 'sttaylor' via Google Summer of Code Mentors List <
google-summer-of-code-mentors-list(a)googlegroups.com>
Date: Mon, Mar 11, 2019 at 5:32 PM
Subject: [GSoC Mentors] Announcing Season of Docs 2019
To: Google Summer of Code Mentors List <
google-summer-of-code-mentors-list(a)googlegroups.com>
We’re delighted to announce the inaugural year of Season of Docs, a Google
program that fosters collaboration between open source projects and
technical writers. Season of Docs is similar to Summer of Code, but with a
focus on open source documentation and technical writers. Details are on
our website: g.co/seasonofdocs
<https://developers.google.com/season-of-docs/>.
Would you like to take part as an open source mentor in the inaugural year
of Season of Docs? Open source organizations can start thinking now about
the projects you’d like a technical writer to work on. Take a look at
the examples
of project ideas
<https://developers.google.com/season-of-docs/docs/project-ideas>. Reach
out to your community members to see who’d like to be a mentor for Season
of Docs. As a mentor, you don’t need technical writing skills. Instead,
you're a member of the open source organization who knows the value of good
documentation and who is experienced in open source processes and tools.
See the guidelines on working with a technical writer
<https://developers.google.com/season-of-docs/docs/tech-writer-collaboration>.
Organization applications open on April 2, 2019. See the full timeline
<https://developers.google.com/season-of-docs/docs/timeline> on the Season
of Docs website.
From April 30, Technical writers can explore the list of participating open
source organizations and their project ideas. Technical writers bring their
skills in designing and developing documentation to the open source
organization. Technical writer applications open on April 30. The list of
accepted technical writing projects is announced on July 30.
Please do tweet and blog about Season of Docs if you’d like to share the
news. We want as many people to know about it as possible. We’ve provided
logos that you can download and some example content on the press page
<https://developers.google.com/season-of-docs/docs/press>.
We’re looking forward to an exciting pilot of the Season of Docs program!
If you have any questions about the program, please email us at
season-of-docs-support(a)googlegroups.com.
Best regards
Sarah Maddox, Andrew Chen and the Season of Docs team
--
You received this message because you are subscribed to the Google Groups
"Google Summer of Code Mentors List" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to google-summer-of-code-mentors-list+unsubscribe(a)googlegroups.com.
To post to this group, send email to
google-summer-of-code-mentors-list(a)googlegroups.com.
Visit this group at
https://groups.google.com/group/google-summer-of-code-mentors-list.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/5635...
<https://groups.google.com/d/msgid/google-summer-of-code-mentors-list/5635...>
.
For more options, visit https://groups.google.com/d/optout.
Hi yt-dev!
Over the past few days at the yt development workshop we added some new
bots/features to the yt repository that will hopefully help streamline some
aspects of the maintenance of the project. Here is what we came up with so
far:
- We added a welcome bot that welcomes and thanks new contributors to the
project on their first issue or PR.
- We added a triage bot that adds a "triage" label to all new issues. Once
they have been triaged and relevant labels have been added, the bot
automatically removes the triage label.
- We added a few "projects" to the projects tab of the repo (yt 4.0,
weather data, and frontend refactor). The intent here is to document what
needs to be done and track our progress on projects/milestones that we have
for yt.
- We added new labels for issues and PRs. We've added domains, index, and
coordinates labels to help refine our classifications of different issues.
I also updated the coloring on some of these labels, so
* greens: things that are direct improvements or are related to new
contributors
* browns: related to project infrastructure / tests / docs
* blues: future ideas / aspirations
* yellows: awaiting actions
* everything else is random
If any of you have feedback/concerns/other ideas on how we can improve what
I've mentioned here, ideas on what else can be done to streamline things,
or declaring your love for different color palettes, please chime in! These
are intended to be a helpful starting point, not random
unilaterally-decided additions to the project.
Best,
Madicken
Hi everyone,
Here at the yt developers workshop, we're experimenting with bots that will
help us with some project management. For example, we're about to enable a
bot that will prevent WIP pull requests from being merged. When we're done,
we'll send a summary email of everything we've done. If anyone starts
seeing weird behavior on the github repo or with PRs, either reply to this
email or say something on slack. We'll try to keep the noise down.
Britton
Hi all,
I'd like to publicly announce that I will be leaving my current position at
NCSA at the beginning of May and starting a 12-week batch at the recurse
center in NYC this summer. If you're curious about the recurse center, take
a look at their website for details (https://recurse.com). While I will
still be around and able to participate in the community at a lower level,
I will need to step down from my current role as primary maintainer of yt
when I leave NCSA so I can focus on new projects and opportunities.
Matt has volunteered to take up some of the slack on code review but I'm
hoping that everyone else can also chip in. We also have two postdocs here
at NCSA (Madicken Munk and Jared Coughlin) who have both expressed interest
in stepping up their contributions to yt and helping out with day-to-day
support and maintenance. I also hope we can have a conversation about
updating yt's governance documents and adding rotating members to the
steering committee at the development workshop next week.
I would like to continue maintaining unyt as part of the yt project going
forward as I expect that will take substantially less time than maintaining
yt as a whole. If people are nervous about yt depending on unyt when I'm
not employed to work on yt development that is fair and I'm happy to talk
about the relationship between unyt and yt in light of all of this.
My plan for the next few weeks is to help get yt-4.0 in a state where we
can do a release. That means merging the yt-4.0 branch into master, helping
out with testing and documentation, and triaging and fixing remaining
issues. I don't know if we'll be able to do a yt 4.0 final release by May
but hopefully we'll at least have a much more solid base to work from.
I'm going to try my best to make this transition as smooth as possible. If
you're aware of places where I could take action now to lead off headaches
down the road it would be great to get reminders about those places.
It's been an amazing experience to have so much of my professional life and
achievements influenced by yt and the yt community over the past 8 years or
so. I'm looking forward to seeing all the cool new things you all will
build in the next few years.
With a heavy heart,
Nathan
