From owner-svn-doc-projects@FreeBSD.ORG Mon Jul 16 09:40:39 2012 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 903F61065672; Mon, 16 Jul 2012 09:40:39 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id 76F538FC08; Mon, 16 Jul 2012 09:40:39 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q6G9edpZ026029; Mon, 16 Jul 2012 09:40:39 GMT (envelope-from gabor@svn.freebsd.org) Received: (from gabor@localhost) by svn.freebsd.org (8.14.4/8.14.4/Submit) id q6G9edvn026019; Mon, 16 Jul 2012 09:40:39 GMT (envelope-from gabor@svn.freebsd.org) Message-Id: <201207160940.q6G9edvn026019@svn.freebsd.org> From: Gabor Kovesdan Date: Mon, 16 Jul 2012 09:40:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Subject: svn commit: r39223 - in projects/sgml2xml/en_US.ISO8859-1/htdocs: community platforms/ia64 projects projects/ideas X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2012 09:40:39 -0000 Author: gabor Date: Mon Jul 16 09:40:38 2012 New Revision: 39223 URL: http://svn.freebsd.org/changeset/doc/39223 Log: - Rename converted XSLT templates to .sgml Approved by: doceng (implicit) Added: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.sgml - copied unchanged from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.sgml - copied unchanged from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.sgml - copied unchanged from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.sgml - copied unchanged from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml - copied unchanged from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl Deleted: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xsl projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/Makefile projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/Makefile projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/Makefile Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/Makefile ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/community/Makefile Mon Jul 16 09:33:21 2012 (r39222) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/Makefile Mon Jul 16 09:40:38 2012 (r39223) @@ -7,8 +7,6 @@ .include "../Makefile.inc" .endif -DOCS= irc.sgml mailinglists.sgml newsgroups.sgml webresources.sgml +DOCS= irc.sgml mailinglists.sgml newsgroups.sgml social.sgml webresources.sgml -XMLDOCS+= social::${XML_EVENTS_EVENTS}: - -.include "${DOC_PREFIX}/share/mk/web.site.mk" \ No newline at end of file +.include "${DOC_PREFIX}/share/mk/web.site.mk" Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/community/social.xsl) @@ -0,0 +1,51 @@ + + + + + +]> + + + &title; + + + +

&os; is represented on a number of different social + networks.

+ + + + + Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile Mon Jul 16 09:33:21 2012 (r39222) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/Makefile Mon Jul 16 09:40:38 2012 (r39223) @@ -7,10 +7,7 @@ .include "../Makefile.inc" .endif -DOCS= machines.sgml refs.sgml +DOCS= index.sgml machines.sgml refs.sgml todo.sgml DATA= i2inside.png mckinley-die.png merced-die.png montecito-die.png -XMLDOCS= index::news.xml: -XMLDOCS+= todo::news.xml: - .include "${DOC_PREFIX}/share/mk/web.site.mk" Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/index.xsl) @@ -0,0 +1,67 @@ + + + + + +]> + + + &title; + + + McKinley die + +

Search the ia64 mailing list archives:

+ +
+ + + + +
+ +

Table Of Contents

+ + + +

Introduction

+ +

The FreeBSD/ia64 project pages contain information about the + FreeBSD port to Intel's IA-64 architecture; officially known as + the Intel Itanium® Processor Family (IPF). As with the port + itself, these pages are still mostly a work in progress.

+ +

Current status

+ +

The ia64 port is still considered a tier 2 platform. This boils + down to not being fully supported by our security officer, release + engineers and toolchain maintainers. In practice however the + distinction between a tier 1 platform (which is fully supported) + and a tier 2 platform is not as strict as it seems. In almost all + aspects the ia64 port is a tier 1 platform. +
+ From a developer point of view there's an advantage to have the ia64 + port be a tier 2 platform for a while longer. We still have a couple + of ABI breaking changes in the pipeline and having to maintain + backward compatibility this early in a ports life is less than + ideal.

+ + Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xsl) @@ -0,0 +1,126 @@ + + + + + +]> + + + &title; + + + + Montecito die + +

Search the FreeBSD/ia64 PR database:

+ +
+ + + + +
+ +

+ What needs to be done +

+

+ This page tries to be the starting point for people trying to find + anything that can be done. The order of the items on this page are + not strictly an indication of priority, but it is a good indication. + There are in all likelihood tasks that are not mentioned here, but + that should be done nonetheless. A typical example is the maintenance + of the ia64 web pages... unfortunately. +

+ +

+ Becoming a tier 1 platform +

+

+ With two releases as a tier 2 platform, it is time to work towards + becoming a tier 1 platform. This involves tasks as varied as: +

+
    +
  • + Improve the installation process to take into account that + there is already a GPT with an EFI partition, including other + operating systems. The ability to add a FreeBSD entry to the + EFI boot menu is also a nice thing. +
    • +
  • + Port the GNU debugger. It is sorely missed on a development + machine and required on tier 1 platforms. +
    • +
  • + Port the X server (ports/x11/XFree86-4-Server). Not really + required for tier 1 status, but one cannot truly do without + if one wants to use ia64 as a desktop machine. +
    • +
+ +

+ Ports and packages +

+

+ A very important task for the success of FreeBSD on ia64 is making + sure that users have something to run besides ls(1). Our huge ports + collection has been targeting ia32 for the most part, so it is not + surprising that there are a lot of ports that do not build or do not + work on ia64. Look + + here + + for the most up-to-date list of ports that fail to build for some + reason or another. Note that if there are ports depending on one or + more ports that fail, those are not built and are not counted. A good + way to help out here is to work on those ports that have a lot of + ports depending on it (see the "Aff." column in the table). +

+ +

+ Sharpening the saw +

+

+ There are plenty functions (especially assembly routines) that + have been written to provide the missing functionality without any + consideration for speed and/or robustness. Reviewing those functions + and replacing them if necessary is a good task that can be done + concurrently and independently from other activity and does not + necessarily require huge amounts of knowledge and/or experience. +

+ +

+ Core development +

+

+ On top of the high-level things that do not work or do not exist, + there is also some rather involved rewriting to be done at the + foundation and can potentially affect all other platforms as well. + This includes: +

+
    +
  • + Improve UP and SMP stability by revamping the PMAP module. + The low-level handling of VM translations needs to be improved. + This involves both correctness as well as performance. +
    • +
  • + Basic device drivers such as sio(4) and syscons(4) do not + work on ia64 machines that do not have support for legacy + devices. This is a rather big issue, because it affects all + platforms and may involve rewriting (big) parts of certain + subsystems. Clearly a task that needs wholesale support and + coordination. +
    • +
  • + Better handling of sparse (physical) memory configurations + by not creating VM tables that span the whole address space, + but rather cover the memory "chunks" that are present. We are + currently forced to ignore memory because of this. +
    • +
+ + Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/Makefile ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/Makefile Mon Jul 16 09:33:21 2012 (r39222) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/Makefile Mon Jul 16 09:40:38 2012 (r39223) @@ -10,6 +10,7 @@ DOCS= projects.sgml DOCS+= newbies.sgml DOCS+= cvsweb.sgml +DOCS+= summerofcode.sgml DOCS+= summerofcode-2005.sgml DOCS+= summerofcode-2006.sgml DOCS+= summerofcode-2007.sgml @@ -22,11 +23,6 @@ DATA+= 2010-freebsd-gsoc.pdf #DATA+= 2011-freebsd-gsoc-thumbnail.jpg DATA+= 2011-freebsd-gsoc.pdf -XML_IDEAS= ${DOC_PREFIX}/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml -XSL_SOC= ${DOC_PREFIX}/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl - -XMLDOCS= summerofcode:${XSL_SOC}:${XML_IDEAS}: - INDEXLINK= projects.html SUBDIR= acpi busdma c99 ideas mips bigdisk netperf Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/Makefile ============================================================================== --- projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/Makefile Mon Jul 16 09:33:21 2012 (r39222) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/Makefile Mon Jul 16 09:40:38 2012 (r39223) @@ -13,11 +13,6 @@ MAINTAINER= joel DATA= style.css -XML_IDEAS= ${DOC_PREFIX}/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml -XSL_IDEAS= ${DOC_PREFIX}/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xsl - -XMLDOCS= ideas:${XSL_IDEAS}:${XML_IDEAS}: - -INDEXLINK= ideas.html +DOCS= ideas.sgml .include "${DOC_PREFIX}/share/mk/web.site.mk" Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xsl) @@ -0,0 +1,18 @@ + + + + +]> + + + &title; + + + +

The ideas page has moved to the FreeBSD wiki.

+ + + Copied: projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml (from r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.sgml Mon Jul 16 09:40:38 2012 (r39223, copy of r39222, projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/summerofcode.xsl) @@ -0,0 +1,370 @@ + + + + + +]> + + + &title; + + + +

The FreeBSD Project is looking forward to participating as a mentoring + organization in Google + Summer of Code 2011. + This program funds students to contribute to an open source project over + the summer break. + We have had over 100 successful + students working on FreeBSD as part of this program in 2005, 2006, 2007, 2008, + 2009, + and + 2010.

+ +

This page will be updated throughout the GSoC 2011 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!

+ + + + +

Benefit of Participating

+ +

Google Summer of Code is an exciting opportunity for students to + "intern" with an open source project for a summer. The FreeBSD + Project, as one of the most successful and oldest open source projects, + is an excellent place to do this internship. Founded in 1993, the + project now consists of several hundred "committers" and tens of + thousands of contributors. FreeBSD is the foundation for many + commercial products, including Apple's Mac OS X, NetApp's OnTap/GX, + Juniper's JunOS, as well countless other products, and is widely used + in the Internet Service Provider and corporate IT worlds. Many of + these sponsors participate daily in the FreeBSD community, and students + have the opportunity to develop software ideas in an exciting + environment with many real world applications, and under the mentorship + of experienced developers.

+ +

After the summer ends, many of our students are sponsored by Google or + the FreeBSD Foundation to attend operating systems and open source + conferences to present on their work, and a significant number go on to + become FreeBSD developers. It's also a great job networking + opportunity!

+ + +

Past Student Projects

+ +

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

+ + +

See also our wiki pages for student projects [2008, +2007, +2006, and +2005].

+ + +

Example Proposal Ideas

+ +

The FreeBSD Project maintains an Ideas Page on our + wiki. + Projects specifically tagged as "GSoC" are believed to be sized for a + useful summer hacking, and have technical contacts who can help answer + questions as you write your proposal. + Ideas not marked as GSoC-friendly are also fine to propose, but may be + scoped larger or smaller than a summer, or might not have such a clear + mentor -- we suggest e-mailing our soc-admins alias for help if you do + decide to propose one of them. + You are, of course, welcome to propose your own ideas, and if the + proposal is strong, we'll try to match you with a mentor!

+ +

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

+ + +

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. + The objective of the proposal is to identify + what is to be done, explain why this needs to be done, and convince us + that:

+ +
    +
  • You are qualified to do this project. This means both having the + necessary background and demonstrating a general understanding of the + problem.
    • +
  • You have the resources (especially time!) needed to complete the + project within the working period of the Summer of Code.
    • +
+ +

A strong proposal will include (at least):

+ +

General Information

+
    +

  • Name

    • + +

  • Email

    • + +

  • Phone

    • + +

  • IM/IRC

    • + +

  • Availability

    + +

    How many hours per week will you spend working on this? How many on + other things? What other obligations (work, school, vacation, + weddings, etc.) do you have this summer? Be as specific as possible: + when will the project begin and end? You should be ready to produce + a day by day schedule before the program starts.)

    + +

    Please note: participating in Google Summer of Code + is a significant time commitment, and you should not apply if you + already have another full-time job planned for the summer.

    • + +

  • Bio

    + +

    Who are you? What skills do you bring to this project? What is your + past involvement with The FreeBSD Project? (Past involvement is not + required, but ideally you will have at least installed FreeBSD and + perhaps fixed a bug or two) If your project includes programming in + a particular language, such as C, or in a specific environment, such + as the kernel or an embedded platform, what experience do you have + working in that area? Are you familiar with or a user of revision + control systems? Have you completed courses that will be relevant to + your project idea? What do you think you will need to learn to + complete this project?

    • + +

  • Possible Mentor

    + +

    Optional, but highly recommended. Do not put a name here if you have + not contacted them.

    • +
+ +

Project Information

+
    +

  • Project Title

    + +

    In forty characters or less, what you propose to do.

    • + +

  • Project Description

    + +

    A few paragraphs describing your project. Direct copies from the + ideas page will be rejected - proposals should reveal that you have + done some research into the problem and its solutions. Include both + what you will be doing and why it is a good thing for The FreeBSD + Project.

    • + +

  • Deliverables

    + +

    A list quantifiable results and related code milestones. We suggest + at least two milestones before the mid-term evaluations and two + after. Where appropriate, this schedule should include multiple + committable or releasable points so people can benefit from and/or + test your work as early as possible.

    • + +

  • Test Plan

    + +

    What parts of your code need testing and how do you plan to test + them? This might include both functionality and performance tests. +

    • + +

  • Project Schedule

    + +

    How long will the project take? When can you begin work?

    • + +
+ + +

Mentors

+ +

A number of FreeBSD committers are willing to mentor students. A + good place to start is the 'Technical contacts' listed with the + example projects on the ideas page.

+ + +

Infrastructure Provided to Students

+ +

In previous years, 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

+ +
    +

  • When are proposals due, and how do I submit mine? +

    + +

    At the time of writing, Google has announced the following dates of + interest relating to the application process:

    + +
      +

    • 18 March - Google to announce what open source + organizations will participate in Google Summer of Code 2011.

      • + +

    • 28 March - Student application period opens. +

      • + +

    • 8 April - Student application period closes. +

      • + +

    • 22 April - Organizations finish reviewing + applications an mentors registered.

      • + +

    • 25 April - Accepted students announced.

      +
      • +
    + +

    Note that these dates may change, and the Google FAQ timeline is the + authoritative source of detailed schedule information:

    + + + +

    All students must register with, and submit applications via, the + Google Summer of Code home page:

    + +
    • + +

  • What advice do you have for a student who might want to + submit a proposal?

    + +

    Experience suggests that the strongest proposals come from students + who contact FreeBSD developers and potential mentors well in advance + of submitting their proposal, seek feedback on their proposal ideas, + and write proposals that reflect time spent exploring and understanding + the problem area to be addressed. Even if the FreeBSD developer(s) you + contact aren't the eventual mentor of the project, their feedback can + be invaluable.

    • + +

  • Can I submit multiple project proposals to the FreeBSD + Project?

    + +

    Yes, but do make sure you invest adequate time in each proposal. We + are not able to accept more than one project per student, so you may do + better spending more time on one or two detailed proposals than by + submitting lots of less-detailed ones.

    • + +

  • Will the FreeBSD Project accept more than one student for + the same idea?

    + +

    In general, we will accept only one student for any given proposal + idea, as most proposal ideas in our ideas list are sized with a single + student summer project in mind. This is a good reason to consider + coming up with your own idea, or at least, making sure that your + proposal for one of our project ideas reflects your unique contribution + and viewpoint. If you plan to submit multiple proposals, you might + consider doing one with an idea from the list, and another with an + original idea.

    • + +

  • What if my proposal is not selected in the application + process? Can I still participate?

    + +

    We always have more good applications than student places, but that + doesn't mean you can't do the project anyway. The FreeBSD Project + always welcomes new volunteers to work on projects, and is generally + happy to provide mentoring and support for students whose proposals + could not be selected in order to allow them to work on their project + anyway. You will need to work with the FreeBSD Project GSoC + administrators to identify a possible mentor. However, Google will not + fund that participation.

    • + +

  • What projects were completed successfully by students + in previous summers?

    + +

    Please see the 2010 FreeBSD + Summer of Code page, as well as older project pages from + 2009, 2008, 2007, 2006, and 2005 for a list of the + completed projects from previous years.

    • + +

  • How can I learn more about FreeBSD?

    + +

    The FreeBSD Project Home Page + is the best way to learn more about the project -- from there you can + reach the FreeBSD Handbook, FreeBSD Developer's Handbook, project + mailing list archives, regular project status reports, and more. If + you have questions about specific project ideas, e-mail the technical + contacts for those ideas. If you have general GSoC questions relating + to FreeBSD, such as if you are unable to reach a project technical + contact, need help finding documentation, or want to know who might be + a good person to talk to about your idea, send them to soc-admins@FreeBSD.org.

    +
    • + +

  • Is there an IRC channel I can join to talk about proposal + ideas or get help finding out more?

    + +

    You can join #freebsd-soc on the efnet IRC network to chat with + FreeBSD developers interested in mentoring student proposals and + projects, past FreeBSD/GSoC students, and other students applying to + FreeBSD/GSoC this year.

    • + +
+ + +

Advertise on Your Campus

+ +

Please help us advertise Google Summer of Code with FreeBSD at your + local university or college campus! You can forward around our e-mail + announcement to department and club mailing lists, and to department + secretaries to distribute. You can also print out and post copies of the + FreeBSD GSoC 2011 poster.

+ +

[FreeBSD GSoC 2011 poster thumnail]

+ + +