Add GSoC entry from pfg

This commit is contained in:
Benjamin Kaduk 2016-10-16 00:31:39 +00:00
parent d58e796cac
commit 87a68b955d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=49524

View file

@ -145,4 +145,69 @@
</task>
</help>
</project>
<project cat='soc'>
<title>Google Summer of Code 2016</title>
<contact>
<person>
<name>
<given>Gavin</given>
<common>Atkinson</common>
</name>
<email>gavin@FreeBSD.org</email>
</person>
<person>
<name>
<given>Pedro</given>
<common>Giffuni</common>
</name>
<email>pfg@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.FreeBSD.org/SummerOfCode2016Projects">GSoC 2016 Projects</url>
<url href="https://wiki.FreeBSD.org/SummerOfCodeIdeas">GSoC Ideas page</url>
</links>
<body>
<p>As in all previous editions of the Google Summer of Code, &os;
was an accepted organization, and we had the chance to mentor 15
projects. Huge thanks to all our mentors for keeping the high
quality standards that make our community shine.</p>
<p>This year was rather unique in that we accepted for the first
time well-known members of the community that are not src
committers to co-mentor. We also accepted projects that have
a different upstream than &os;. Both are clear signs that &os; is
growing and adapting to the wider community.</p>
<p>This year we are also had administrative issues with Perforce
and have accepted officially the use of external repositories, in
particular github, as requested by students.</p>
<p>12 of 15 projects were successful, which we think is an
excellent result for a Google Summer of Code.</p>
</body>
<sponsor>
Google Inc.
</sponsor>
<sponsor>
The FreeBSD Foundation
</sponsor>
<help>
<task>The world is changing and we need fresh project ideas. We
need to start looking for those ideas <strong>now</strong>.</task>
<task>The project ideas wiki page has been reset and we need to
get it populated before applying for the next Google Summer of
Code. Please help unleash the next stream of projects you want to
see in &os;.</task>
</help>
</project>
</report>