From f1ac7928983d1981e505fdd27af7e947a5b2027e Mon Sep 17 00:00:00 2001 From: Brooks Davis Date: Fri, 8 Mar 2019 17:48:37 +0000 Subject: [PATCH] Update to GSoC 2019. Drop mention of SVN and Perforce in favor of using github. If students are familiar with anything it's going to be git. Comment out text on gsoc flyers until someone makes an updated one. Reported by: bz Reviewed by: mmokhi Differential Revision: https://reviews.freebsd.org/D19505 --- .../htdocs/projects/summerofcode.xml | 37 ++++++++++--------- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/en_US.ISO8859-1/htdocs/projects/summerofcode.xml b/en_US.ISO8859-1/htdocs/projects/summerofcode.xml index b19441c43b..7167458da3 100644 --- a/en_US.ISO8859-1/htdocs/projects/summerofcode.xml +++ b/en_US.ISO8859-1/htdocs/projects/summerofcode.xml @@ -17,7 +17,7 @@

The FreeBSD Project is looking forward to participating as a mentoring organization in Google - Summer of Code 2018. + Summer of Code 2019. This program offers students a stipend of up to $6,600 USD to contribute to an open source project over @@ -25,7 +25,9 @@ the summer break. We have had over 210 successful students working on FreeBSD as part of this program since 2005.

-

This page and the ideas lists will be updated throughout the application period +

This page and the ideas +lists will be updated throughout the application period to include new information, such as project ideas, proposal information, and potential mentor contact information. If you don't see an idea that interests you, visit again in a couple of days! Additionally, we welcome @@ -39,7 +41,9 @@ proposals unrelated to the ideas listed here.

  • Proposal Guidelines
  • Infrastructure Provided to Students
  • Frequently Asked Questions
    • + @@ -237,19 +241,15 @@ href="https://wiki.FreeBSD.org/SummerOfCode2005">2005].

    Infrastructure Provided to Students

    -

    In previous years, the FreeBSD Project provided access to FreeBSD - Subversion and - Perforce revision control infrastructure in order to facilitate - student collaboration, provide public access and archiving for the - on-going student projects, and to help mentors and the community - monitor on-going work. It is expected that students participating - in future programs will be offered the same facilities. Students - will also be asked to maintain wiki pages on their on-going - projects. In the past, e-mail, IRC, and instant messaging have - proven popular among students and mentors, and students - participating in the FreeBSD summer program are encouraged to use - these and other electronic communication mechanisms to become active - in the community.

    +

    We expect project work to be done in GitHub repositories in order + to facilitate student collaboration, provide public access and + archiving for the on-going student projects, and to help mentors and + the community monitor on-going work. Students will also be asked to + maintain wiki pages on their on-going projects. In the past, e-mail, + IRC, and instant messaging have proven popular among students and + mentors, and students participating in the FreeBSD summer program are + encouraged to use these and other electronic communication mechanisms + to become active in the community.

    Frequently Asked Questions

    @@ -335,8 +335,9 @@ href="https://wiki.FreeBSD.org/SummerOfCode2005">2005].

    in previous summers?

    Please see the 2017 FreeBSD + href="https://wiki.FreeBSD.org/SummerOfCode2018Projects">2018 FreeBSD Summer of Code page, as well as older project pages from + 2017, 2016, 2015, 2014, @@ -375,6 +376,7 @@ href="https://wiki.FreeBSD.org/SummerOfCode2005">2005].

    +

    +-->