PERFORCE change 159353 for review
Gabor Pali
pgj at FreeBSD.org
Tue Mar 17 14:39:57 PDT 2009
http://perforce.freebsd.org/chv.cgi?CH=159353
Change 159353 by pgj at beehive on 2009/03/17 21:38:56
IFC
Affected files ...
.. //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/authors.ent#24 integrate
.. //depot/projects/docproj_hu/doc/share/pgpkeys/fabient.key#1 branch
.. //depot/projects/docproj_hu/doc/share/pgpkeys/pgpkeys-developers.sgml#18 integrate
.. //depot/projects/docproj_hu/doc/share/pgpkeys/pgpkeys.ent#18 integrate
.. //depot/projects/docproj_hu/www/en/developers.sgml#20 integrate
.. //depot/projects/docproj_hu/www/en/news/2008/Makefile#2 integrate
.. //depot/projects/docproj_hu/www/en/news/2008/press.xml#2 delete
.. //depot/projects/docproj_hu/www/en/projects/2009-freebsd-gsoc-thumbnail.jpg#1 branch
.. //depot/projects/docproj_hu/www/en/projects/2009-freebsd-gsoc.pdf#1 branch
.. //depot/projects/docproj_hu/www/en/projects/Makefile#2 integrate
.. //depot/projects/docproj_hu/www/en/projects/ideas/ideas.xml#9 integrate
.. //depot/projects/docproj_hu/www/en/projects/ideas/ideas.xsl#5 integrate
.. //depot/projects/docproj_hu/www/en/projects/summerofcode.xsl#3 integrate
.. //depot/projects/docproj_hu/www/en/releases/7.2R/Makefile#1 branch
.. //depot/projects/docproj_hu/www/en/releases/7.2R/docbook.css#1 branch
.. //depot/projects/docproj_hu/www/en/releases/7.2R/schedule.sgml#1 branch
.. //depot/projects/docproj_hu/www/en/releases/Makefile#3 integrate
.. //depot/projects/docproj_hu/www/en/releng/index.sgml#15 integrate
.. //depot/projects/docproj_hu/www/share/sgml/libcommon.xsl#7 integrate
.. //depot/projects/docproj_hu/www/share/sgml/news.xml#43 integrate
.. //depot/projects/docproj_hu/www/share/sgml/press.xml#12 integrate
.. //depot/projects/docproj_hu/www/share/sgml/usergroups.xml#6 integrate
Differences ...
==== //depot/projects/docproj_hu/doc/en_US.ISO8859-1/share/sgml/authors.ent#24 (text+ko) ====
@@ -13,7 +13,7 @@
builds for the other languages, and we will poke fun of you
in public.
- $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.473 2009/03/05 21:38:01 dhn Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/share/sgml/authors.ent,v 1.474 2009/03/17 14:52:00 fabient Exp $
-->
<!ENTITY a.aaron "Aaron Dalton <email>aaron at FreeBSD.org</email>">
@@ -330,6 +330,8 @@
<!ENTITY a.erwin "Erwin Lansing <email>erwin at FreeBSD.org</email>">
+<!ENTITY a.fabient "Fabien Thomas <email>fabient at FreeBSD.org</email>">
+
<!ENTITY a.fanf "Tony Finch <email>fanf at FreeBSD.org</email>">
<!ENTITY a.farrokhi "Babak Farrokhi <email>farrokhi at FreeBSD.org</email>">
==== //depot/projects/docproj_hu/doc/share/pgpkeys/pgpkeys-developers.sgml#18 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/share/pgpkeys/pgpkeys-developers.sgml,v 1.90 2009/03/05 22:06:02 dhn Exp $
+ $FreeBSD: doc/share/pgpkeys/pgpkeys-developers.sgml,v 1.91 2009/03/17 14:52:00 fabient Exp $
-->
<sect2 id="pgpkey-ariff">
@@ -356,6 +356,11 @@
&pgpkey.lippe;
</sect2>
+ <sect2 id="pgpkey-fabient">
+ <title>&a.fabient;</title>
+ &pgpkey.fabient;
+ </sect2>
+
<sect2 id="pgpkey-fanf">
<title>&a.fanf;</title>
&pgpkey.fanf;
==== //depot/projects/docproj_hu/doc/share/pgpkeys/pgpkeys.ent#18 (text+ko) ====
@@ -1,5 +1,5 @@
-<!-- $FreeBSD: doc/share/pgpkeys/pgpkeys.ent,v 1.186 2009/03/05 22:08:00 dhn Exp $ -->
+<!-- $FreeBSD: doc/share/pgpkeys/pgpkeys.ent,v 1.187 2009/03/17 14:52:00 fabient Exp $ -->
<!-- PGP keyblocks -->
<!ENTITY pgpkey.aaron SYSTEM "aaron.key">
<!ENTITY pgpkey.ache SYSTEM "ache.key">
@@ -84,6 +84,7 @@
<!ENTITY pgpkey.ehaupt SYSTEM "ehaupt.key">
<!ENTITY pgpkey.emax SYSTEM "emax.key">
<!ENTITY pgpkey.erwin SYSTEM "erwin.key">
+<!ENTITY pgpkey.fabient SYSTEM "fabient.key">
<!ENTITY pgpkey.fanf SYSTEM "fanf.key">
<!ENTITY pgpkey.farrokhi SYSTEM "farrokhi.key">
<!ENTITY pgpkey.fjoe SYSTEM "fjoe.key">
==== //depot/projects/docproj_hu/www/en/developers.sgml#20 (text+ko) ====
@@ -6,7 +6,7 @@
us to update author names, or the representation of those names (such
as adding email addresses), by just editing a single file.
-$FreeBSD: www/en/developers.sgml,v 1.215 2009/03/05 21:46:33 dhn Exp $
+$FreeBSD: www/en/developers.sgml,v 1.216 2009/03/17 14:52:00 fabient Exp $
-->
@@ -166,6 +166,7 @@
<!ENTITY a.erich "Eric L. Hernes">
<!ENTITY a.erik "Erik Cederstrand">
<!ENTITY a.erwin "Erwin Lansing">
+<!ENTITY a.fabient "Fabien Thomas">
<!ENTITY a.fanf "Tony Finch">
<!ENTITY a.farrokhi "Babak Farrokhi">
<!ENTITY a.fenner "Bill Fenner">
==== //depot/projects/docproj_hu/www/en/news/2008/Makefile#2 (text+ko) ====
@@ -1,4 +1,4 @@
-# $FreeBSD: www/en/news/2008/Makefile,v 1.1 2009/02/11 17:15:28 pgj Exp $
+# $FreeBSD: www/en/news/2008/Makefile,v 1.2 2009/03/16 07:58:53 pgj Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@@ -10,7 +10,4 @@
XMLDOCS+= index:${XSL_NEWS_NEWSFLASH_OLD}:news.xml:
DEPENDSET.index=transtable news
-XMLDOCS+= press:${XSL_NEWS_PRESS_OLD}::
-DEPENDSET.press=transtable press
-
.include "${WEB_PREFIX}/share/mk/web.site.mk"
==== //depot/projects/docproj_hu/www/en/projects/Makefile#2 (text+ko) ====
@@ -1,4 +1,4 @@
-# $FreeBSD: www/en/projects/Makefile,v 1.32 2008/04/22 08:59:24 murray Exp $
+# $FreeBSD: www/en/projects/Makefile,v 1.33 2009/03/16 13:43:53 rwatson Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@@ -15,6 +15,9 @@
DOCS+= summerofcode-2007.sgml
DOCS+= summerofcode-2008.sgml
+DATA= 2009-freebsd-gsoc-thumbnail.jpg
+DATA+= 2009-freebsd-gsoc.pdf
+
XML_IDEAS= ${WEB_PREFIX}/en/projects/ideas/ideas.xml
XSL_SOC= ${WEB_PREFIX}/en/projects/summerofcode.xsl
==== //depot/projects/docproj_hu/www/en/projects/ideas/ideas.xml#9 (text+ko) ====
@@ -15,7 +15,7 @@
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
- $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.109 2009/03/13 15:28:47 brooks Exp $
+ $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.123 2009/03/17 18:28:37 rpaulo Exp $
</cvs:keyword>
</cvs:keywords>
@@ -179,7 +179,7 @@
</desc>
</idea>
- <idea id="extenddump" class="soc">
+ <idea id="extenddump">
<title>Improve the performance of dump/restore</title>
<desc><p>A performance evaluation of the split cache (as is) and an unified cache
@@ -535,58 +535,51 @@
</desc>
</idea>
- <idea id="modrefcnt">
- <title>Dynamic module references</title>
+ <idea id="kernel-dvb" class="soc">
+ <title>Kernel support for linux DVB device drivers</title>
- <desc>
-<p><strong>Technical contact</strong>: <a
- href="mailto:sam at FreeBSD.org">Sam Leffler</a></p>
-<p>Kernel modules may have dynamic references created during operation.
- For example net80211 key entries reference functions in the crypto module
- that implements the key's cipher. Presently there is no standard mechanism
- for expressing this dependency so that module unloading is disallowed;
- instead modules must track references and implement their own semantics.
- This task is to define and implement a general mechanism for tracking
- these references and use them in handling module unload requests.</p>
-<p><strong>Requirements</strong>:</p>
-<ul>
- <li>Good knowledge of C.</li>
- <li>Kernel awareness.</li>
-</ul>
- </desc>
- </idea>
-
- <idea id="kernel-linuxemu" class="soc">
- <title>Kernel support for linux device drivers</title>
-
<desc>
<p><strong>Technical contact</strong>: <a href="mailto:luigi at FreeBSD.org">Luigi Rizzo</a></p>
-<p>Recently, a project was started to compile linux device drivers
- on FreeBSD through an in-kernel emulation layer, which
+<p>In early 2007 we started a project was started to support the
+ building of linux device drivers on FreeBSD.
+ This was done through an in-kernel emulation layer, which
implements part of the linux kernel API on top of the FreeBSD
kernel API. The initial implementation was good enough to
support a few USB webcam drivers, and is documented
<a
-href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html">here</a>.</p>
+href="http://info.iet.unipi.it/~luigi/FreeBSD/linux_bsd_kld.html">here</a>.
+ The code is actually available as a port, devel/linux-kmod-compat,
+ and a popular driver that uses this infrastructure is
+ multimedia/linux-gspca-kmod .
+</p>
+<p>We would like to use a similar approach to add support
+ for DVB devices, which are widely supported in Linux
+ but not in FreeBSD. In particular we expect the project to provide,
+ within the FreeBSD kernel, enough of linux compatibility to build
+ the core components of the drivers/media/ linux kernel, and then
+ a few device drivers including one for a PCI DVB card (e.g.
+ saa7134-based).
+</p>
-<p>The goal of this project is to extend this emulation layer
- to cover more of the linux kernel API. Two areas that need
- further work are the API used by network/communication device drivers (e.g.
- many USB wired and wireless device drivers; telephony cards), and the API used
- by memory-mapped devices and drivers (e.g. analog or DVB video
- acquisition cards, both USB and PCI).</p>
-
-<p>A Summer of Code applicant would be required to choose a significant set of
- extensions to the existing work (e.g. one of those indicated
- above), and select at least two linux device drivers to be
- ported to FreeBSD using the newly implemented functions.</p>
-
-<p>Before the start of the project a Summer of Code applicant is expected to
- have studied the above URL and understood the emulation technique
- used, and to have/acquire access to at least some of the hardware
- involved, so that actual functionality tests can be performed
- in addition to the compile tests.</p>
+<p>Before the start of the project, a Summer of Code applicant is expected to
+ i) become familiar with the approach used by linux-kmod-compat;
+ ii) set up a proper test environment, with a couple of DVB devices
+ supported by linux, and a working linux installation so that
+ one can compare results;
+ iii) become familiar with the architecture of the linux code in
+ drivers/media.
+<br/>
+ Probably the attention should be focused in PCI devices, because
+ at this stage the USB stack is in a transition phase and would
+ pose some additional difficulties.
+</p>
+<p>
+ Expected results are a working porting infrastructure, a working
+ linux-dvb-kmod device driver, and a working application to demonstrate
+ that the driver is working as expected. We suggest to look at
+ "kaffeine" for which a FreeBSD port already exists.
+</p>
</desc>
</idea>
@@ -673,12 +666,9 @@
</desc>
</idea>
- <idea id="powerd" class="soc">
+ <idea id="powerd">
<title>Implement and profile algorithms for powerd</title>
<desc>
-<p><strong>Technical contacts</strong>: <a
- href="mailto:njl at FreeBSD.org">Nate Lawson</a>, <a
- href="mailto:bruno at FreeBSD.org">Bruno Ducrot</a></p>
<p>Implement a range of predictive algorithms (and perhaps design your own)
and profile them for power usage and performance loss. The best
algorithm will save the most power while losing the least performance. This
@@ -722,29 +712,95 @@
</desc>
</idea>
- <idea id="psched">
- <title>Pluggable Disk Scheduler</title>
+ <idea id="per-job-limits" class="soc">
+ <title>Collective limits on set of processes (a.k.a. jobs)</title>
+
+ <desc>
+<p><strong>Technical contact</strong>: <a
+ href="mailto:brooks at freebsd.org">Brooks Davis</a></p>
+
+<p>In SGI's Irix operating system, there is a concept of a job which is
+ a collection of processes. These processes share a set of resource
+ limits similar to those accessible through the set/getrlimit and
+ getrusage system calls. Schedulers such as Sun Grid Engine currently
+ implement tracking the processes that make up a job and enforcing
+ collective limits on them in an adhoc manner. Having first class
+ kernel support would be useful.</p>
+
+<p>It seems most likely that implementing something like the Irix
+ interface would be the most useful approach since that would enable us
+ to leverage existing code. Implementers will need to make sure that
+ the job construct has no negative performance implications when not
+ enabled (ideally, processes that are not part of jobs should be
+ unaffected) and quantify the impact on perfomance when enabled.</p>
+
+<p><strong>References</strong>: <a
+ href="http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?cmd=search&coll=0650&db=man&pth=&srch=jid_t&searchpth=man&rpt=20">Irix
+ Man Pages mentioning jid_t</a></p>
+
+<p><strong>Requirements</strong>:</p>
+<ul>
+ <li>Good knowledge of C.</li>
+ <li>Kernel awareness.</li>
+ <li>Ability to implement functionality from interface specifications.</li>
+</ul>
+ </desc>
+ </idea>
+
+ <idea id="psched" class="soc">
+ <title>Geom-based Disk Schedulers</title>
<desc>
<p><strong>Technical contact</strong>: <a
- href="mailto:s223560 at studenti.ing.unipi.it">Emiliano Mennucci</a></p>
+ href="mailto:luigi at freebsd.org">Luigi Rizzo</a></p>
+<p>In a 2005 GSoC project, "Pluggable Disk Schedulers", Emiliano
+ Mennucci explored the feasibility of pluggable disk schedulers
+ for FreeBSD. The project was successful, but we could not explore
+ certain approaches (e.g. "anticipation", where requests are delayed
+ hoping that some future ones can served without a seek) due to
+ architectural limitations the kernel had at the time.
+</p>
+<p>
+ Since then, the GEOM infrastructure has become available on FreeBSD
+ for interacting with disk I/O requests. GEOM has enabled us to
+ work on disk schedulers in a much more flexible way, allowing a
+ much faster development of disk scheduling algorithms. With
+ Fabio Checconi, we have developed a prototype
+ implementation of some anticipatory schedulers, see
+ <a href="http://info.iet.unipi.it/~luigi/FreeBSD/#geom_sched">GEOM_SCHED</a>.
+</p>
+<p>
+ GEOM_SCHED works within the geom layer, i.e. above the device driver
+ where queueing of requests may actually occur. The way GEOM_SCHED
+ does scheduling is by limiting the number of outstanding requests
+ to the device, and the performance implications of this approach
+ need to be measured. An alternative approach is to push the
+ scheduler (using the same algorithms developed in GEOM_SCHED,
+ and most likely the same code) within the device drivers. This less general
+ (as it needs to be replicated in all drivers) but it may be
+ an interesting thing to do e.g. for some popular device drivers
+ such as ATA.
+</p>
+<p>
+ The proposed SoC work can address one or more of the following
+ aspects:
+<ul>
+<li>implement suitable classifiers for disk requests;</li>
+<li>implement techniques for the auto-tuning of
+ the scheduler parameters;</li>
+<li>measure the performance implications
+ of doing scheduling above the device driver, and possibly design
+ and implement a suitable mechanism to push the GEOM_SCHED
+ module within the device driver itself.</li>
+</ul>
+ Ultimately, we expect to end up with a production quality subsystem
+ for use in FreeBSD.
+</p>
<p><strong>References</strong>: <a
href="http://wiki.freebsd.org/moin.cgi/Hybrid">The Pluggable Disk
Schedulers SoC project</a>, <a
href="http://www.happyemi.org/hybrid/">Patches</a></p>
-<p>Our "Pluggable Disk Schedulers" SoC 2005 project resulted in code which
- solved the problem where large sequential I/O requests, or certain
- access patterns from one or a few processes, might almost completely
- starve other processes. It is available as a patch for RELENG_4 and
- RELENG_5. Unfortunately the code in FreeBSD-current (and RELENG_6)
- changed too much, so that the patches can not be committed. The goal
- of this project is to port the pluggable disk schedulers to the GEOM
- framework.</p>
-<p>Interested people should also have a look at <a
- href="http://lists.freebsd.org/pipermail/freebsd-geom/2007-January/001854.html">
- a mail thread about this</a> (Ulf is not working on this) and <a
- href="http://www.freebsd.org/cgi/mid.cgi?db=irt&id=20071011022001.GC13480@gandalf.sssup.it">
- further discussion</a> of the corresponding GEOM aspects.</p>
+
<p><strong>Requirements</strong>:</p>
<ul>
<li>Ability to read and understand foreign C code.</li>
@@ -771,13 +827,10 @@
</desc>
</idea>
- <idea id="suspend" class="soc">
+ <idea id="suspend">
<title>Suspend to disk</title>
<desc>
-<p><strong>Technical contacts</strong>: <a
- href="mailto:njl at FreeBSD.org">Nate Lawson</a>, <a
- href="mailto:bruno at FreeBSD.org">Bruno Ducrot</a></p>
<p>Implement a suspend/resume from disk mechanism. Possibly use the dump
functions to dump pages to disk, then use ACPI to put the system in S4 or
power-off. Resume would require changes to the loader to load the memory
@@ -842,26 +895,24 @@
</desc>
</idea>
- <idea id="vmalgorithm" class="soc">
- <title>VM Algorithm Improvement</title>
+ <idea id="efi" class="soc">
+ <title>EFI support for FreeBSD/i386 and FreeBSD/amd64</title>
+ <desc>
+ <p><strong>Technical contact</strong>: <a
+ href="mailto:rpaulo at FreeBSD.org">Rui Paulo</a></p>
+ <p>Finish EFI support on the i386/amd64 ports. Final work
+ should be able to boot a FreeBSD kernel into single user
+ mode, at least.</p>
- <desc>
-<p><strong>Technical contact</strong>: <a
- href="mailto:jeff at FreeBSD.org">Jeff Roberson</a>, <a
- href="mailto:alc at FreeBSD.org">Alan Cox</a></p>
+ <p><strong>Requirements</strong>:</p>
+ <ul>
+ <li>Good knowledge of C.</li>
+ <li>Deep understanding of the boot process and EFI.</li>
+ <li>A system running EFI 1.0 (Intel Macs, for example)</li>
+ </ul>
-<p>The vm uses a splay tree to lookup pages associated with an offset and a
- file. This tree structure is space inefficient and cache inefficient for
- large objects. This project will be to replace the splay with a dynamic
- depth page-table like structure similar to a radix tree. This will improve
- large object performance and reduce the size of the vm_page.</p>
-<p><strong>Requirements</strong>:</p>
-<ul>
- <li>Strong knowledge of C.</li>
- <li>Familiarity with concepts of virtual memory and advanced data
- structures and algorithms.</li>
-</ul>
</desc>
+
</idea>
</category>
@@ -946,27 +997,6 @@
</desc>
</idea>
- <idea id="wi" class="soc">
- <title>Update wi</title>
-
- <desc>
-<p><strong>Technical contact</strong>: <a
- href="mailto:sam at FreeBSD.org">Sam Leffler</a></p>
-<p>Many new and useful features (e.g. crypto protocols like WPA) of the WLAN
- infrastructure in the kernel are not used in wi(4). While wi(4)
- cards are old and can not compete with recent wireless cards, they are still
- in use in a lot of places. The goal of this item is to examine the WLAN
- infrastructure and other WLAN drivers in the tree for nice features and
- port/use them in the wi(4) driver.</p>
-<p><strong>Requirements</strong>:</p>
-<ul>
- <li>Knowledge of C.</li>
- <li>No fear of undocumented parts of the kernel.</li>
- <li>One wi(4) card and one other wireless device to test against.</li>
-</ul>
- </desc>
- </idea>
-
<idea id="wpa2preauth" class="soc">
<title>WPA2 preauthentication in hostapd</title>
@@ -1013,7 +1043,7 @@
</desc>
</idea>
- <idea class="soc" id="sctp">
+ <idea id="sctp">
<title>SCPS, Space Communication Protocol Standards</title>
<desc><p><a href="http://www.scps.org">SCPS</a> is a protocol suite
@@ -1027,6 +1057,26 @@
others.)</p>
</desc>
</idea>
+
+ <idea id="tcp-uto" class="soc">
+ <title>Implement TCP UTO</title>
+ <desc>
+ <p><strong>Technical contact</strong>: <a
+ href="mailto:rpaulo at FreeBSD.org">Rui Paulo</a></p>
+
+ <p>Implement TCP UTO (User Timeout Option) as defined by RFC
+ 5482.</p>
+
+ <p><strong>Requirements</strong>:</p>
+ <ul>
+ <li>Good knowledge of C and TCP.</li>
+ <li>Able to understand the FreeBSD TCP/IP stack.</li>
+ <li>A testbed with at least two machines.</li>
+ </ul>
+
+ </desc>
+ </idea>
+
</category>
<category>
@@ -1287,6 +1337,37 @@
</desc>
</idea>
+ <idea id="mac_policy" class="soc">
+ <title>Path-based file system MAC policy</title>
+ <desc>
+ <p><strong>Technical contact</strong>: <a
+ href="mailto:rwatson at FreeBSD.org">Robert Watson</a>, <a
+ href="mailto:trustedbsd-discuss at TrustedBSD.org">TrustedBSD discuss
+ mailing list</a></p>
+ <p>The TrustedBSD MAC Framework makes it easy to extend the FreeBSD
+ kernel security model using pluggable modules, which has provided
+ support for "traditional" mandatory access control, as well as
+ allowed a number of companies to build local security policy
+ extensions for workstation, server, and appliance products; one
+ such example is Apple's "Seatbelt" policy for Mac OS X. However,
+ the base system MAC policies are difficult to use, primarily
+ because they either don't extend security meta-data (ugidfw) or
+ they require extensive labeling (Biba, MLS). This project idea
+ involves crafting a new OS security policy extension along the
+ lines of ugidfw, the file system firewall, but using path names
+ instead of existing file properties to manage protection. This
+ requires careful thinking about what a file system path "is" in
+ the UNIX environment, as well as regarding what sorts of
+ policies would be useful.</p>
+ <p><strong>Requirements</strong>:</p>
+ <ul>
+ <li>Strong C programming skills.</li>
+ <li>Familiarity with OS security policies, including
+ discretionary and mandatory access control.</li>
+ </ul>
+ </desc>
+ </idea>
+
<idea id="securityregression" class="soc">
<title>Security regression tests</title>
@@ -1506,12 +1587,13 @@
</desc>
</idea>
- <idea id="bsdtexttools" class="soc">
+ <idea id="bsdtexttools" class="soc2008">
<title>BSD-licensed Text-Processing Tools</title>
<desc>
<p><strong>Technical contact</strong>: <a
- href="mailto:dds at FreeBSD.org">Diomidis Spinellis</a></p>
+ href="mailto:dds at FreeBSD.org">Diomidis Spinellis</a>,
+ <a href="mailto:gabor at FreeBSD.org">Gábor Kövesdán</a></p>
<p>Create/port BSD-licensed versions of one or more of the text processing
tools that are currently missing from the FreeBSD distribution:
<strong>sort</strong>,
@@ -1530,7 +1612,9 @@
like the current GNU versions we use. Additionally this implementation has
support for common vector fonts and unicode. If those utilities are
option-compatible or not has to be analyzed. A port of this is already
- available as textproc/heirloom-doctools.
+ available as textproc/heirloom-doctools. Alternativly, OpenBSD's
+ <a href="http://mdocml.bsd.lv/">mdocml</a> can replace groff's mdoc
+ functionality and may be sufficent for our purposes.
</p>
<p><strong>Requirements</strong>:</p>
<ul>
@@ -1635,7 +1719,7 @@
</desc>
</idea>
- <idea id="ndmp" class="soc">
+ <idea id="ndmp">
<title>NDMP data server</title>
<desc>
@@ -1682,7 +1766,7 @@
</desc>
</idea>
- <idea id="pacfile" class="soc">
+ <idea id="pacfile">
<title>Proxy auto-config file support for libfetch</title>
<desc>
==== //depot/projects/docproj_hu/www/en/projects/ideas/ideas.xsl#5 (text+ko) ====
@@ -7,7 +7,7 @@
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
]>
-<!-- $FreeBSD: www/en/projects/ideas/ideas.xsl,v 1.13 2009/03/12 11:42:55 rwatson Exp $ -->
+<!-- $FreeBSD: www/en/projects/ideas/ideas.xsl,v 1.14 2009/03/17 14:50:04 rwatson Exp $ -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
xmlns:cvs="http://www.FreeBSD.org/XML/CVS">
@@ -145,8 +145,7 @@
technical contacts below:</p>
<ul>
<li><strong>ACPI</strong>:
- <a href="mailto:njl at FreeBSD.org">&a.njl;</a>,
- <a href="mailto:bruno at FreeBSD.org">&a.bruno;</a>.</li>
+ <a href="mailto:rpaulo at FreeBSD.org">&a.rpaulo;</a>.</li>
<li><strong>File systems</strong>:
<a href="mailto:scottl at FreeBSD.org">&a.scottl;</a>,
<a href="mailto:alfred at FreeBSD.org">&a.alfred;</a>.</li>
==== //depot/projects/docproj_hu/www/en/projects/summerofcode.xsl#3 (text+ko) ====
@@ -7,7 +7,7 @@
<!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
]>
-<!-- $FreeBSD: www/en/projects/summerofcode.xsl,v 1.15 2008/09/19 05:01:12 murray Exp $ -->
+<!-- $FreeBSD: www/en/projects/summerofcode.xsl,v 1.22 2009/03/16 14:19:06 rwatson Exp $ -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
xmlns:cvs="http://www.FreeBSD.org/XML/CVS">
@@ -38,10 +38,10 @@
<div id="CONTENTWRAP">
&header3;
-<p>The FreeBSD Project is pleased to participate as a mentoring
- organization in the <a
+<p>The FreeBSD Project is looking forward to participating as a mentoring
+ organization in <a
href="http://code.google.com/summerofcode.html">Google Summer of
- Code</a> 2008. This program funds students to contribute to an open
+ Code</a> 2009. This program funds students to contribute to an open
source project over the summer break. We have had over 70 successful
students working on FreeBSD as part of this program in <a
href="&base;/projects/summerofcode-2005.html">2005</a>, <a
@@ -51,12 +51,13 @@
<ul>
<li><a href="#benefits">Benefits of Participating</a></li>
- <li><a href="#current">Current Student Projects</a></li>
<li><a href="#students">Past Student Projects</a></li>
<li><a href="#ideas">Example Proposal Ideas</a></li>
<li><a href="#mentors">Possible Mentors</a></li>
+ <li><a href="#proposals">Proposal Guidelines</a></li>
<li><a href="#infrastructure">Infrastructure Provided to Students</a></li>
<li><a href="#faq">Frequently Asked Questions</a></li>
+ <li><a href="#advertise">Advertise on Your Campus</a></li>
</ul>
<a name="benefits"></a>
@@ -82,13 +83,6 @@
become FreeBSD developers. It's also a great job networking
opportunity!</p>
-<a name="current"></a>
-<h2>Current Student Projects</h2>
-
-<p>We've recently <a
- href="&base;/projects/summerofcode-2008.html">announced</a> the
- successful students from the Summer of Code 2008.</p>
-
<a name="students"></a>
<h2>Past Student Projects</h2>
@@ -117,16 +111,129 @@
<a name="ideas"></a>
<h2>Example Proposal Ideas</h2>
- <p>The application period for this year has closed, but students and
- interested developers can always find interesting work that needs
- to be done on the <a
- href="&base;/projects/ideas/index.html">FreeBSD Project Ideas</a>
- list.</p>
+ <p>The following example project ideas are a subset of the general
+ <a href="&base;/projects/ideas/index.html">FreeBSD Project
+ Ideas</a> list that we think are the most suitable for Summer of
+ Code projects. You are not required to submit a proposal using one of
+ these ideas - original ideas, if of interest to the project, are
+ most welcome.</p>
+
+ <xsl:for-each select="document($ideas.xml)//descendant::category[child::idea[@class='soc']]">
+ <h3><xsl:value-of select="title"/></h3>
+
+ <ul>
+ <xsl:for-each select="idea[@class='soc']">
+ <li><xsl:element name="a">
+ <xsl:attribute name="href">
+ ./ideas/index.html#p-<xsl:value-of select="@id" />
+ </xsl:attribute>
+ <xsl:value-of select="title" />
+ </xsl:element>
+ </li>
+ </xsl:for-each>
+ </ul>
+ </xsl:for-each>
<p>For additional ideas about upcoming development projects in
FreeBSD, take a look at recent <a
href="&base;/news/status">Developer Status Reports</a>.</p>
+<a name="proposals"></a>
+<h2>Proposal Guidelines</h2>
+
+<p>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 <a
+ href="http://www.perlfoundation.org/gc/grants/proposals.html">open
+ source proposal HOWTO</a>. The objective of the proposal is to identify
+ what is to be done, explain why this needs to be done, and convince us
+ that:</p>
+
+ <ul>
+ <li>You are qualified to do this project. This means both having the
+ necessary background and demonstrating a general understanding of the
+ problem.</li>
+ <li>You have the resources (especially time!) needed to complete the
+ project within the working period of the Summer of Code.</li>
+ </ul>
+
+ <p>A strong proposal will include (at least):</p>
+
+ <h3>General Information</h3>
+ <ul>
+ <li><p><strong>Name</strong></p></li>
+
+ <li><p><strong>Email</strong></p></li>
+
+ <li><p><strong>Phone</strong></p></li>
+
+ <li><p><strong>IM/IRC</strong></p></li>
+
+ <li><p><strong>Availability</strong></p>
+
+ <p>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 and? You should be ready to produce
+ a day by day schedule before the program starts.)</p>
+
+ <p><strong>Please note</strong>: 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.</p></li>
+
+ <li><p><strong>Bio</strong></p>
+
+ <p>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?</p></li>
+
+ <li><p><strong>Possible Mentor</strong></p>
+
+ <p>Optional, but highly recommended. Do not put a name here if you have
+ not contacted them.</p></li>
+ </ul>
+
+ <h3>Project Information</h3>
+ <ul>
+ <li><p><strong>Project Title</strong></p>
+
+ <p>In forty characters or less, what you propose to do.</p></li>
+
+ <li><p><strong>Project Description</strong></p>
+
+ <p>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.</p></li>
+
+ <li><p><strong>Deliverables</strong></p>
+
+ <p>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.</p></li>
+
+ <li><p><strong>Test Plan</strong></p>
+
+ <p>What parts of your code need testing and how do you plan to test
+ them? This might include both functionality and performance tests.
+ </p></li>
+
+ <li><p><strong>Project Schedule</strong></p>
+
+ <p>How long will the project take? When can you begin work?</p></li>
+
+ </ul>
+
<a name="mentors"></a>
<h2>Mentors</h2>
@@ -155,16 +262,84 @@
<h2>Frequently Asked Questions</h2>
<ul>
- <li><p><strong>I wasn't selected for funding by Google as part of the Google Summer of Code, can I still participate?</strong></p>
+ <li><p><strong>When are proposals due, and how do I submit mine?</strong>
+ </p>
+
+ <p>At the time of writing, Google has announced the following dates of
+ interest relating to the application process:</p>
+
+ <ul>
+ <li><p><strong>18 March</strong> - Google to announce what open source
+ organizations will participate in Google Summer of Code 2009.</p></li>
+
+ <li><p><strong>23 March</strong> - Student application period opens.
+ </p></li>
+
+ <li><p><strong>3 April</strong> - Student application period closes.
+ </p></li>
+
+ <li><p><strong>15 April</strong> - Organizations finish reviewing
+ applications an mentors registered.</p></li>
+
+ <li><p><strong>20 April</strong> - Accepted students announced.</p>
+ </li>
+ </ul>
+
+ <p>Note that these dates may change, and the Google FAQ timeline is the
+ authoritative source of detailed schedule information:</p>
+
+ <ul><p><a href="http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline">GSoC FAQ: Important Dates</a></p></ul>
+
+ <p>All students must register with, and submit applications via, the
+ Google Summer of Code home page:</p>
+
+ <ul><p><a href="http://socghop.appspot.com/program/home/google/gsoc2009">Google Summer of Code Home Page</a></p></ul></li>
+
+ <li><p><strong>What advice do you have for a student who might want to
+ submit a proposal?</strong></p>
+
+ <p>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.</p></li>
+
+ <li><p><strong>Can I submit multiple project proposals to the FreeBSD
+ Project?</strong></p>
+
+ <p>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.</p></li>
+
+ <li><p><strong>Will the FreeBSD Project accept more than one student for
+ the same idea?</strong></p>
+
+ <p>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.</p></li>
+
+ <li><p><strong>What if my proposal is not selected in the application
+ process? Can I still participate?</strong></p>
- <p>Yes! By all means. Each year we have many more talented
- student applications that there are available places and we are
- very happy when students choose to get involved with FreeBSD.
- Please mail soc-mentors at FreeBSD.org about how to proceed with
- your project.</p></li>
+ <p>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.</p></li>
<li><p><strong>What projects were completed successfully by students
- last summer?</strong></p>
+ in previous summers?</strong></p>
<p>Please see the <a href="summerofcode-2008.html">2008 FreeBSD
Summer of Code</a> page, as well as older project pages from <a
@@ -173,8 +348,44 @@
href="summerofcode-2005.html">2005</a> for a list of the
completed projects from previous years.</p></li>
+ <li><p><strong>How can I learn more about FreeBSD?</strong></p>
+
+ <p>The <a href="http://www.FreeBSD.org/">FreeBSD Project Home Page</a>
+ 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 <a
+ href="mailto:soc-admins at FreeBSD.org">soc-admins at FreeBSD.org</a>.</p>
+ </li>
+
+ <li><p><strong>Is there an IRC channel I can join to talk about proposal
+ ideas or get help finding out more?</strong></p>
+
+ <p>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.</p></li>
+
</ul>
+<a name="advertise"></a>
+<h2>Advertise on Your Campus</h2>
+
+ <p>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
+ <a href="2009-freebsd-gsoc.pdf">FreeBSD GSoC 2009 poster</a>.</p>
+
+ <p><a href="2009-freebsd-gsoc.pdf" align="left"> <img
+ src="2009-freebsd-gsoc-thumbnail.jpg"
+ alt="[FreeBSD GSoC 2009 poster thumnail]" height="248" width="192"
+ border="0" /></a></p>
+
</div> <!-- CONTENTWRAP -->
<br class="clearboth" />
</div> <!-- CONTENT -->
==== //depot/projects/docproj_hu/www/en/releases/Makefile#3 (text+ko) ====
@@ -1,4 +1,4 @@
-# $FreeBSD: www/en/releases/Makefile,v 1.52 2008/08/22 14:30:38 hrs Exp $
+# $FreeBSD: www/en/releases/Makefile,v 1.53 2009/03/17 13:40:36 rwatson Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@@ -15,7 +15,7 @@
SUBDIR+= 4.6.2R 4.7R 4.8R 4.9R 4.10R 4.11R
SUBDIR+= 5.0R 5.1R 5.2R 5.2.1R 5.3R 5.4R 5.5R
SUBDIR+= 6.0R 6.1R 6.2R 6.3R 6.4R
-SUBDIR+= 7.0R 7.1R
+SUBDIR+= 7.0R 7.1R 7.2R
.if defined $(NEW_BUILD)
SUBDIR=
==== //depot/projects/docproj_hu/www/en/releng/index.sgml#15 (text+ko) ====
@@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.251 2009/03/05 09:23:50 blackend Exp $">
+<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.254 2009/03/17 13:55:58 rwatson Exp $">
<!ENTITY email 're'>
<!ENTITY title "Release Engineering Information">
<!ENTITY % navinclude.developers "INCLUDE">
@@ -47,17 +47,10 @@
<th>Information</th>
</tr>
-<!--
<tr>
- <td>January 2009</td>
- <td>FreeBSD <a href="../releases/7.1R/schedule.html">7.1</a></td>
- <td> </td>
- </tr>
--->
- <tr>
<td>May 2009</td>
- <td>FreeBSD 7.2</td>
- <td> </td>
+ <td><a href="../releases/7.2R/schedule.html">FreeBSD 7.2</a></td>
+ <td>A draft release schedule has been announced.</td>
</tr>
<tr>
==== //depot/projects/docproj_hu/www/share/sgml/libcommon.xsl#7 (text+ko) ====
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE xsl:stylesheet PUBLIC "-//FreeBSD//DTD FreeBSD XSLT 1.0 DTD//EN"
"http://www.FreeBSD.org/XML/www/share/sgml/xslt10-freebsd.dtd">
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list