From 649497dcaddc8e00ddaceced4aeaf5f8c743d693 Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Sat, 10 Mar 2007 04:46:52 +0000 Subject: [PATCH] Move the Summer of Code page to an XSLT file. Use an XPATH query to extract ideas from the ideas list which include the class='soc' attribute. Display the title of those projects which are deemed suitable for summer of code projects and then link to the ideas page for the full description, technical contacts, requirements, etc. --- en/projects/Makefile | 8 +- en/projects/summerofcode.sgml | 5 +- en/projects/summerofcode.xsl | 260 ++++++++++++++++++++++++++++++++++ 3 files changed, 270 insertions(+), 3 deletions(-) create mode 100644 en/projects/summerofcode.xsl diff --git a/en/projects/Makefile b/en/projects/Makefile index 0f985505f1..7de651f67e 100644 --- a/en/projects/Makefile +++ b/en/projects/Makefile @@ -1,4 +1,4 @@ -# $FreeBSD: www/en/projects/Makefile,v 1.28 2006/10/04 22:01:50 murray Exp $ +# $FreeBSD: www/en/projects/Makefile,v 1.29 2007/02/12 20:43:06 joel Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" @@ -10,10 +10,14 @@ DOCS= projects.sgml DOCS+= newbies.sgml DOCS+= cvsweb.sgml -DOCS+= summerofcode.sgml DOCS+= summerofcode-2005.sgml DOCS+= summerofcode-2006.sgml +XML_IDEAS= ${WEB_PREFIX}/en/projects/ideas/ideas.xml +XSL_SOC= ${WEB_PREFIX}/en/projects/summerofcode.xsl + +XMLDOCS= summerofcode:${XSL_SOC}:${XML_IDEAS}: + INDEXLINK= projects.html SUBDIR= acpi busdma c99 ideas mips bigdisk netperf diff --git a/en/projects/summerofcode.sgml b/en/projects/summerofcode.sgml index 1b070f76ab..69bb68e3f0 100644 --- a/en/projects/summerofcode.sgml +++ b/en/projects/summerofcode.sgml @@ -1,6 +1,6 @@ - + %developers; @@ -98,6 +98,9 @@ SoC2006 Wiki and the Google
  • &a.phk; <phk@FreeBSD.org>
    • +
  • &a.dds; <dds@FreeBSD.org> + +
    • diff --git a/en/projects/summerofcode.xsl b/en/projects/summerofcode.xsl new file mode 100644 index 0000000000..e7d574c1e6 --- /dev/null +++ b/en/projects/summerofcode.xsl @@ -0,0 +1,260 @@ + + + + + %developers; +]> + + + + + + + + + + + + + + + + + &header1; + + +
    +
    + &header2; + +
    +
    + &nav; +
    + +
    + &header3; + +

    The FreeBSD Project is pleased to participate as a mentoring organization in the + Google Summer of + Code 2007. This program funds students to contribute to an open + source project over the summer break. We had dozens of successful + students working on FreeBSD as part of this program in 2005 and 2006.

    + + + + +

    Past Student Projects

    + +

    For a complete list of student projects from previous years, +visit:

    + + +

    See also our FreeBSD +SoC2006 Wiki and the Google +FreeBSD SoC 2006 pages.

    + + +

    Example Proposal Ideas

    + +

    The following example project ideas are a subset of the general + FreeBSD Project Ideas + list that we think are the most suitable for Summer of Code + projects.

    + + +

    + +
      + +
    • + + ./ideas/index.html#p- + + + +
      • +       +
    +     + +

    For additional ideas about upcoming development projects in + FreeBSD, take a look at recent Developer Status Reports.

    + + +

    Mentors

    + +

    A number of FreeBSD committers are willing to mentor students this + year. A good place to start is the 'Technical contacts' listed with + the example projects on the Ideas page. In addition + to those specific projects, the following mentors are willing to + work with students in any of the broad areas listed below.

    + +
      +
    • &a.jkoshy; <jkoshy@FreeBSD.org> +
        +
      • BSD-licensed toolchain using libelf.
        • +
      • A GUI for PmcTools.
        • +
      +
      • +
    • &a.rwatson; <rwatson@FreeBSD.org> +
        +
      • Security, SEBSD, ACLs, Event auditing.
        • +
      • Networking.
        • +
      +
      • +
    • &a.bz; <bz@FreeBSD.org> +
      • Networking: user or kernel space.
      +
      • +
    • &a.thompsa; <thompsa@FreeBSD.org> +
      • Networking: ethernet improvements, trunking, vlans, etc.
      +
      • +
    • &a.murray; <murray@FreeBSD.org> +
      • Installation tools / userland.
      +
      • +
    • &a.netchild; <netchild@FreeBSD.org> +
      • Sound and Linux emulation.
      +
      • +
    • &a.gnn; <gnn@FreeBSD.org> +
      • IPv6, IPSec
      +
      • +
    • &a.phk; <phk@FreeBSD.org> +
      • Disk I/O
      +
      • +
    • &a.dds; <dds@FreeBSD.org> +
      • Userland and infrastructure tools.
      +
      • +
    + + +

    Proposal Guidelines

    + +

    Students are responsible for writing a proposal and submitting it + to Google before the application deadline. The following outline + was adapted from the Perl Foundation open + source proposal HOWTO. A strong proposal will include:

    + + +
      +
    • Name
      • + +
    • Email
      • + +
    • Project Title
      • + +
    • Possible Mentor (optional)
      • + +
    • Benefits to the FreeBSD Community - a good + project will not just be fun to work on, but also generally + useful to others.
      • + +
    • Deliverables - It is very important to list + quantifiable results here e.g. +
        +
      • "Improve X modules in ways Y and Z."
        • +
      • "Write 3 new man pages for the new interfaces."
        • +
      • "Improve test coverage by writing X more unit/regression + tests."
        • +
      • "Improve performance in FOO by X%."
        • +
      +
      • + +
    • Project Schedule - How long will the project + take? When can you begin work?
      • + +
    • Availability - How many hours per week can + you spend working on this? What other obligations do you have + this summer?
      • + +
    • Bio - Who are you? What makes you the best + person to work on this project?
      • +
    + + +

    Infrastructure Provided to Students

    + +

    In 2005 and 2006, the FreeBSD Project provided access to the FreeBSD +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.

    + + +

    Frequently Asked Questions

    + +
      + +

    • Am I eligible?

      + +

      Please see the Google FAQ + for all questions about eligibility.

      • + +

    • Where can I find more information about being a + student or mentor in this program?

      + +

      Please see the program wiki here.

      • + +

    • When does the application period begin?

      + +

      March 2007.

      • + +

    • Where do I send my proposal?

      + +

      Proposals must be sent directly to Google when the application + period begins.

      • + +

    • What projects were completed successfully by students + last summer?

      + +

      Please see the 2006 FreeBSD + Summer of Code and 2005 + FreeBSD Summer of Code pages for a list of the completed + projects from previous years.

      • + +
    + +
    +
    +
    + + +
    +
    + + + +     +