Update our GSOC page for 2019

[ericholscher]

This adds a new idea for PR building.

We should also add other ideas that we've had,
especially if they are ~3-6 months out on the roadmap

[stsewd]

There is a link at the end to a label that we don't use anymore, it has this text Looking through these issues is a

[davidfischer]

Here's some thoughts:

• Should we remove APIv3 since @humitos is working on it actively?
• I don't know if it is a great project but if we can attract any designers, I'd love to commission a Sphinx2 theme. Sphinx2 is going to be all HTML5 so a modern web framework could be used.
• This is not well thought through, but getting more different types of docs (on top of Sphinx/MkDocs) would be very cool

[stsewd]

What about improving the mkdocs integration? #4588 #4924

Not sure if we want to focus on mkdocs for GSoC

[humitos]

I like the changes.

Also, as @davidfischer said APIv3 could be listed here and I could mentor a student on that if you consider that we want to go in that path. Although, this probably means that we won't have this feature working before September...

👍 on adding a Sphinx2 theme and 👎 on spending time adding another type of docs (I suppose that this will be replaced/done via "Upload built docs")

[humitos]

Long term storage for docs from a PR?

[ericholscher]

Yea, we really don't want them on our web servers which are already space limited.

[ericholscher]

I've removed apiv3 and added a Sphinx v2 theme section, but it isn't great. Will merge this today because of the application deadline, but if people have concrete additions, please propose them in new PR's

[ericholscher]

@rtfd/core Would love a 👍 today if folks think this is ready.

[stsewd]

These links should go in the pull requests project

[stsewd]

LGTM