googlecodein:2012tasks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
googlecodein:2012tasks [2012/11/23 23:11] – Add task. WojciechKoszekgooglecodein:2012tasks [2021/04/26 01:23] (current) – Use MailTo macros. JethroNederhof
Line 9: Line 9:
 Contact channels: Contact channels:
   * IRC: #freebsd-soc @ EFNET   * IRC: #freebsd-soc @ EFNET
-  * Mailing list: freebsd-hackers@ (for helping others, please put "GCIN" as a first word of the Subject)+  * Mailing list: [[freebsd-hackers@FreeBSD.org|freebsd-hackers@]] (for helping others, please put "GCIN" as a first word of the Subject)
  
 Stuff from 2011: Stuff from 2011:
Line 15: Line 15:
  
 Stuff to read: Stuff to read:
-  * **What GCIN is for %%FreeBSD%%??**: [[http://wiki.freebsd.org/action/edit/GoogleCodeIn]]+  * **What GCIN is for %%FreeBSD%%??**: [[/GoogleCodeIn]]
   * **From mentors**: [[http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation]]   * **From mentors**: [[http://code.google.com/p/google-code-in/wiki/GCIAdminMentorInformation]]
  
Line 40: Line 40:
 technologies than just "cgi-bin.pl" or "ANSI C", since people with Ruby, technologies than just "cgi-bin.pl" or "ANSI C", since people with Ruby,
 Python or Perl etc.. skillsets are more likely to get attracted. It would Python or Perl etc.. skillsets are more likely to get attracted. It would
-be up to [[/SomeBody|SomeBody]] (tm) to figure out what the project could be and how to+be up to %%SomeBody%% (tm) to figure out what the project could be and how to
 break it down to small tasks. This could let us "steal" people from other break it down to small tasks. This could let us "steal" people from other
 projects. projects.
Line 85: Line 85:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 20 | | Time limit | 20 |
-| Mentor | theraven@freebsd.org |+| Mentor | <theraven@freebsd.org> |
 | Requirements | Add static lock order annotations to kernel locking primitives. | | Requirements | Add static lock order annotations to kernel locking primitives. |
  
Line 101: Line 101:
 | Difficulty | hard | | Difficulty | hard |
 | Time limit | 20 | | Time limit | 20 |
-| Mentor | theraven@freebsd.org |+| Mentor | <theraven@freebsd.org> |
 | Requirements | A Clang static analyser plugin checking correct usage of a kernel API. | | Requirements | A Clang static analyser plugin checking correct usage of a kernel API. |
  
Line 115: Line 115:
 | Difficulty | hard | | Difficulty | hard |
 | Time limit | 40 | | Time limit | 40 |
-| Mentor | theraven@freebsd.org rdivacky@%%FreeBSD%%.org |+| Mentor | <theraven@freebsd.org> <rdivacky@FreeBSD.org> |
 | Requirements | Benchmarks comparing libc++ to libstdc++ and a list of performance troublespots for libc++ | | Requirements | Benchmarks comparing libc++ to libstdc++ and a list of performance troublespots for libc++ |
  
Line 129: Line 129:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 4-16 | | Time limit | 4-16 |
-| Mentor | bcr@%%FreeBSD%%.org |+| Mentor | <bcr@FreeBSD.org> |
 | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains how to set up a zfs mirror in textual form with some examples (i.e. using programlisting tags). It has to have correctly formatted XML according to our Documentation Primer. | | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains how to set up a zfs mirror in textual form with some examples (i.e. using programlisting tags). It has to have correctly formatted XML according to our Documentation Primer. |
  
Line 152: Line 152:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 6-20 | | Time limit | 6-20 |
-| Mentor | bcr@%%FreeBSD%%.org |+| Mentor | <bcr@FreeBSD.org> |
 | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what deduplication is and what the benefits are with some examples (i.e. using programlisting tags). It has to have correctly formatted XML according to our Documentation Primer. | | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what deduplication is and what the benefits are with some examples (i.e. using programlisting tags). It has to have correctly formatted XML according to our Documentation Primer. |
  
Line 170: Line 170:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 7-14 | | Time limit | 7-14 |
-| Mentor | bcr@freebsd.org eadler@freebsd.org |+| Mentor | <bcr@freebsd.org> <eadler@freebsd.org> |
 | Requirements | The X11 configuration section contains a subsection on how to configure X11 without HAL (with common items to both in a subsection before them) | | Requirements | The X11 configuration section contains a subsection on how to configure X11 without HAL (with common items to both in a subsection before them) |
  
Line 193: Line 193:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 10-20 | | Time limit | 10-20 |
-| Mentor | rea@freebsd.org |+| Mentor | <rea@freebsd.org> |
 | Requirements | a new article containing instructions what clang/llvm is and how to use it in %%FreeBSD%% | | Requirements | a new article containing instructions what clang/llvm is and how to use it in %%FreeBSD%% |
  
 ==== Description of task ==== ==== Description of task ====
  
-The %%FreeBSD%% system is moving to replace the GCC (GNU Compiler Collection) with clang/llvm (C language for the low level virtual machine). The following wiki page has an initial writeup of the subject with some instructions on how to use it to compile the %%FreeBSD%% base system: http://wiki.freebsd.org/BuildingFreeBSDWithClang+The %%FreeBSD%% system is moving to replace the GCC (GNU Compiler Collection) with clang/llvm (C language for the low level virtual machine). The following wiki page has an initial writeup of the subject with some instructions on how to use it to compile the %%FreeBSD%% base system: [[/BuildingFreeBSDWithClang]]
 The goal is to create an article which has more detailed instructions based on this wiki page with our official %%FreeBSD%% documentation markup and style applied. The goal is to create an article which has more detailed instructions based on this wiki page with our official %%FreeBSD%% documentation markup and style applied.
  
Line 213: Line 213:
 | Difficulty | easy | | Difficulty | easy |
 | Time limit | 10-25 | | Time limit | 10-25 |
-| Mentor |+| Mentor | <remko@freebsd.org> |
  
 The objective of this task is to create a list of man pages that do not contain this string. The best way to do this is to create a script that can automatically search for that string in a set of files (man pages in this case) passed to it. Your mentor can help you with commands or advice on which programming language to use. But if you don't want to code, you can also do this task manually (or semi-manually), but this will take more time than writing and running a script to produce the list. The objective of this task is to create a list of man pages that do not contain this string. The best way to do this is to create a script that can automatically search for that string in a set of files (man pages in this case) passed to it. Your mentor can help you with commands or advice on which programming language to use. But if you don't want to code, you can also do this task manually (or semi-manually), but this will take more time than writing and running a script to produce the list.
Line 230: Line 230:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 8-22 | | Time limit | 8-22 |
-| Mentor | bcr@%%FreeBSD%%.org |+| Mentor | <bcr@FreeBSD.org> |
 | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what zfs compression is and what the benefits are with some examples (i.e. using programlisting tags). The subsection 21.2.2.2 ZFS RAID-Z does not contain anything about compression after this. The section has to have correctly formatted XML according to our Documentation Primer. | | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what zfs compression is and what the benefits are with some examples (i.e. using programlisting tags). The subsection 21.2.2.2 ZFS RAID-Z does not contain anything about compression after this. The section has to have correctly formatted XML according to our Documentation Primer. |
  
Line 250: Line 250:
 | Difficulty | easy | | Difficulty | easy |
 | Time limit | 4-12 | | Time limit | 4-12 |
-| Mentor | rea@freebsd.org |+| Mentor | <rea@freebsd.org> |
 | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what zfs snapshots are and what their benefits are with some examples (i.e. using programlisting tags). The subsection 21.2.2.2 ZFS RAID-Z does not contain anything about snapshots after this. The section has to have correctly formatted XML according to our Documentation Primer. | | Requirements | A new subsection in the ZFS chapter of the %%FreeBSD%% handbook explains what zfs snapshots are and what their benefits are with some examples (i.e. using programlisting tags). The subsection 21.2.2.2 ZFS RAID-Z does not contain anything about snapshots after this. The section has to have correctly formatted XML according to our Documentation Primer. |
  
Line 271: Line 271:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 15-25 | | Time limit | 15-25 |
-| Mentor | ''%%ed@freebsd.org%%'' |+| Mentor | ''%%<<MailTo(ed AT freebsd DOT org)>>%%'' |
 | Requirements | The %%FreeBSD%% developers handbook has a new chapter about the details of the new TTY layer, as well as man pages for category 9. | | Requirements | The %%FreeBSD%% developers handbook has a new chapter about the details of the new TTY layer, as well as man pages for category 9. |
  
 ==== Description of task ==== ==== Description of task ====
-The %%FreeBSD%% developers handbook currently has no information about %%FreeBSD%%'s new TTY layer. However, this has been documented in the %%FreeBSD%% wiki on the following page: http://wiki.freebsd.org/TTYRedesign+The %%FreeBSD%% developers handbook currently has no information about %%FreeBSD%%'s new TTY layer. However, this has been documented in the %%FreeBSD%% wiki on the following page: [[/TTYRedesign]]
 The task is to take the relevant information from that wiki page and create a chapter in the developers handbook to describe the new TTY layer. The chapter needs to be correctly formatted and must conform to our documentation source code style guidelines. The task is to take the relevant information from that wiki page and create a chapter in the developers handbook to describe the new TTY layer. The chapter needs to be correctly formatted and must conform to our documentation source code style guidelines.
  
Line 290: Line 290:
 | Difficulty | easy, medium, hard | | Difficulty | easy, medium, hard |
 | Time limit | 4-8 | | Time limit | 4-8 |
-| Mentor | ''%%pgj@freebsd.org%%'' |+| Mentor | ''%%<<MailTo(pgj AT freebsd DOT org)>>%%'' |
 | Requirements | A new section in the filesystems chapter explains the TMPFS filesystem with an example | | Requirements | A new section in the filesystems chapter explains the TMPFS filesystem with an example |
  
 ==== Description of task ==== ==== Description of task ====
  
-The %%FreeBSD%% operating system supports the TMPFS filesystem, which is described on the following %%FreeBSD%% wiki page, but not in the %%FreeBSD%% handbook: http://wiki.freebsd.org/TMPFS+The %%FreeBSD%% operating system supports the TMPFS filesystem, which is described on the following %%FreeBSD%% wiki page, but not in the %%FreeBSD%% handbook: [[/TMPFS]]
 The basics of TMPFS, it's pros and cons must to be explained with an example for /tmp and the procedure of activating/using it must be described in the handbook for our user community. The basics of TMPFS, it's pros and cons must to be explained with an example for /tmp and the procedure of activating/using it must be described in the handbook for our user community.
  
Line 310: Line 310:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 8-20 | | Time limit | 8-20 |
-| Mentor | adrian@freebsd.org, freebsd-wireless@freebsd.org |+| Mentor | <adrian@freebsd.org>, <freebsd-wireless@freebsd.org> |
 | Requirements | Basic knowledge of C; An ath(4) 802.11n NIC (non-USB); I can likely help you acquire one. | | Requirements | Basic knowledge of C; An ath(4) 802.11n NIC (non-USB); I can likely help you acquire one. |
  
Line 326: Line 326:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 12-23 | | Time limit | 12-23 |
-| Mentor | ''%%uqs@freebsd.org%%'' |+| Mentor | ''%%<<MailTo(uqs AT freebsd DOT org)>>%%'' |
 | Requirements | The %%FreeBSD%% developers handbook will have a new chapter giving information on the use of Mercurial for %%FreeBSD%% daily work as a developer. | | Requirements | The %%FreeBSD%% developers handbook will have a new chapter giving information on the use of Mercurial for %%FreeBSD%% daily work as a developer. |
  
 ==== Description of task ==== ==== Description of task ====
-The Mercurial source code management system can be used to send and retrieve the %%FreeBSD%% project's source code to/from the main repository. To help developers work with Mercurial and the %%FreeBSD%% repository, the following wiki page was created: http://wiki.freebsd.org/LocalMercurial+The Mercurial source code management system can be used to send and retrieve the %%FreeBSD%% project's source code to/from the main repository. To help developers work with Mercurial and the %%FreeBSD%% repository, the following wiki page was created: [[/LocalMercurial|LocalMercurial]]
  
 The contents of this wiki page needs to be converted into the developers handbook as a separate chapter so that all information for developers who want to use Mercurial is present in one place to find. When adding these instructions and examples to the developers handbook, the source code needs to be correctly formatted and must conform to our documentation source code style guidelines. The contents of this wiki page needs to be converted into the developers handbook as a separate chapter so that all information for developers who want to use Mercurial is present in one place to find. When adding these instructions and examples to the developers handbook, the source code needs to be correctly formatted and must conform to our documentation source code style guidelines.
Line 347: Line 347:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 12-23 | | Time limit | 12-23 |
-| Mentor | uqs@freebsd.org |+| Mentor | <uqs@freebsd.org> |
 | Requirements | The %%FreeBSD%% developers handbook will have a new chapter giving information on the use of GIT for %%FreeBSD%% daily work as a developer. | | Requirements | The %%FreeBSD%% developers handbook will have a new chapter giving information on the use of GIT for %%FreeBSD%% daily work as a developer. |
  
 ==== Description of task ==== ==== Description of task ====
-The GIT source code management system has become popular among software developers over the years. It is possible to use it to to send and retrieve the %%FreeBSD%% project's source code to/from the main repository. To help developers work with GIT and the %%FreeBSD%% repository, the following wiki page was created that details the basic workflow:  http://wiki.freebsd.org/GitWorkflow+The GIT source code management system has become popular among software developers over the years. It is possible to use it to to send and retrieve the %%FreeBSD%% project's source code to/from the main repository. To help developers work with GIT and the %%FreeBSD%% repository, the following wiki page was created that details the basic workflow: [[/GitWorkflow|GitWorkflow]]
  
 The contents of this wiki page needs to be converted into the developers handbook as a separate chapter so that all information for developers who want to use GIT is present in one place to find. When adding these instructions and examples to the developers handbook, the source code needs to be correctly formatted and must conform to our documentation source code style guidelines. The contents of this wiki page needs to be converted into the developers handbook as a separate chapter so that all information for developers who want to use GIT is present in one place to find. When adding these instructions and examples to the developers handbook, the source code needs to be correctly formatted and must conform to our documentation source code style guidelines.
Line 368: Line 368:
 | Difficulty | hard | | Difficulty | hard |
 | Time limit | 10-25 | | Time limit | 10-25 |
-| Mentor | rea@freebsd.org |+| Mentor | <rea@freebsd.org> |
 | Requirements | The %%FreeBSD%% handbook will have an updated chapter on using CUPS to manage printers connected via USB or the network to a %%FreeBSD%% system. | | Requirements | The %%FreeBSD%% handbook will have an updated chapter on using CUPS to manage printers connected via USB or the network to a %%FreeBSD%% system. |
  
Line 389: Line 389:
 | Difficulty | hard | | Difficulty | hard |
 | Time limit | 15-25 | | Time limit | 15-25 |
-| Mentor | rea@freebsd.org |+| Mentor | <rea@freebsd.org> |
 | Requirements | The %%FreeBSD%% handbook will have each chapter in it's index when rendered to Postscript/PDF output. | | Requirements | The %%FreeBSD%% handbook will have each chapter in it's index when rendered to Postscript/PDF output. |
  
Line 409: Line 409:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 10-15 | | Time limit | 10-15 |
-| Mentor | ed@freebsd.org |+| Mentor | <ed@freebsd.org> |
 | Requirements | A page similar to Jens Schweikhardt's from 2001 | | Requirements | A page similar to Jens Schweikhardt's from 2001 |
  
Line 433: Line 433:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 20-30 | | Time limit | 20-30 |
-| Mentor | ed@freebsd.org |+| Mentor | <ed@freebsd.org> |
 | Requirements | A page similar to Jens Schweikhardt's from 2001 | | Requirements | A page similar to Jens Schweikhardt's from 2001 |
  
Line 461: Line 461:
 | Difficulty | easy | | Difficulty | easy |
 | Time limit | 10-12 | | Time limit | 10-12 |
-| Mentor | gavin@%%FreeBSD%%.org |+| Mentor | <gavin@FreeBSD.org> |
 | Requirements | The %%FreeBSD%% developers handbook chapter on debugging modules contains the new information from the wiki page. | | Requirements | The %%FreeBSD%% developers handbook chapter on debugging modules contains the new information from the wiki page. |
  
Line 467: Line 467:
  
 %%FreeBSD%%'s developers handbook has a section describing the steps needed to debug kernel modules: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-kld.html %%FreeBSD%%'s developers handbook has a section describing the steps needed to debug kernel modules: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-kld.html
-However, the information contained in that section are somewhat outdated. Newer instructions are available in the following wiki page: +However, the information contained in that section are somewhat outdated. Newer instructions are available in the following wiki page: [[/DebuggingModules|DebuggingModules]]
-http://wiki.freebsd.org/DebuggingModules+
 The purpose of this task is to take the information from the wiki page and update the developers handbook chapter accordingly. The final page needs to conform to %%FreeBSD%%'s documentation formatting and style guidelines described in the %%FreeBSD%% documentation primer: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ The purpose of this task is to take the information from the wiki page and update the developers handbook chapter accordingly. The final page needs to conform to %%FreeBSD%%'s documentation formatting and style guidelines described in the %%FreeBSD%% documentation primer: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/
  
Line 475: Line 474:
 Students are encouraged to use a %%FreeBSD%% system like our [[/VirtualBox|VirtualBox]] image to test the procedure, but can also use the information available online. Students are encouraged to use a %%FreeBSD%% system like our [[/VirtualBox|VirtualBox]] image to test the procedure, but can also use the information available online.
  
-Please read http://wiki.FreeBSD.org/GoogleCodeIn/GettingStarted before accepting this task, as it contains further details on what this task consists of, as well as providing useful information on how to obtain the page source and how to proceed with the task.+Please read [[GoogleCodeIn/GettingStarted|Getting Started]] before accepting this task, as it contains further details on what this task consists of, as well as providing useful information on how to obtain the page source and how to proceed with the task.
  
 ---- ----
Line 484: Line 483:
 | Difficulty | easy | | Difficulty | easy |
 | Time limit | 12-17 | | Time limit | 12-17 |
-| Mentor | gavin@%%FreeBSD%%.org |+| Mentor | <gavin@FreeBSD.org> |
 | Requirements | The %%FreeBSD%% developers handbook will have a new section describing the use of MIIBus for devices attached to the network. | | Requirements | The %%FreeBSD%% developers handbook will have a new section describing the use of MIIBus for devices attached to the network. |
  
Line 490: Line 489:
  
 %%FreeBSD%% implements IEEE 802.3 Media Independent Interface or MIIBus for its underlying networking capabilities. %%FreeBSD%% Developers who want to know more about this interface currently find no information about it in the %%FreeBSD%% developers handbook. The purpose of this task is to remedy this by %%FreeBSD%% implements IEEE 802.3 Media Independent Interface or MIIBus for its underlying networking capabilities. %%FreeBSD%% Developers who want to know more about this interface currently find no information about it in the %%FreeBSD%% developers handbook. The purpose of this task is to remedy this by
-using the following wiki page as a source of information: http://wiki.freebsd.org/MIIBUS+using the following wiki page as a source of information: [[/MIIBUS]]
 Other links to more information about MIIBus are also available at the bottom of this wiki page. The information should be used to create a new section/chapter describing the use of MIIBus and it's implementation in %%FreeBSD%%. The added information needs to conform to %%FreeBSD%%'s documentation formatting and style guidelines described in the %%FreeBSD%% documentation primer: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ Other links to more information about MIIBus are also available at the bottom of this wiki page. The information should be used to create a new section/chapter describing the use of MIIBus and it's implementation in %%FreeBSD%%. The added information needs to conform to %%FreeBSD%%'s documentation formatting and style guidelines described in the %%FreeBSD%% documentation primer: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/
  
Line 497: Line 496:
 Students are encouraged to use a %%FreeBSD%% system like our [[/VirtualBox|VirtualBox]] image to test the procedure, but can also use the information available online. Students are encouraged to use a %%FreeBSD%% system like our [[/VirtualBox|VirtualBox]] image to test the procedure, but can also use the information available online.
  
-Please read http://wiki.FreeBSD.org/GoogleCodeIn/GettingStarted before accepting this task, as it contains further details on what this task consists of, as well as providing useful information on how to obtain the page source and how to proceed with the task.+Please read [[GoogleCodeIn/GettingStarted|Getting Started]] before accepting this task, as it contains further details on what this task consists of, as well as providing useful information on how to obtain the page source and how to proceed with the task.
  
 ---- ----
Line 506: Line 505:
 | Difficulty | easy | | Difficulty | easy |
 | Time limit | 5-12 | | Time limit | 5-12 |
-| Mentor | rea@freebsd.org |+| Mentor | <rea@freebsd.org> |
 | Requirements | The FAQ contains a new entry on how to solve common USB problems like when mass storage devices are not detected. The entry needs to be formatted correctly according to our %%FreeBSD%% style and doc source code standards. | | Requirements | The FAQ contains a new entry on how to solve common USB problems like when mass storage devices are not detected. The entry needs to be formatted correctly according to our %%FreeBSD%% style and doc source code standards. |
  
 ==== Description of task ==== ==== Description of task ====
 The %%FreeBSD%% operating system has support for many devices connected via the Universal Serial Bus (USB). However, given the vast amount of devices, there are some problems that occur frequently for which there are already solutions available on the following wiki page: The %%FreeBSD%% operating system has support for many devices connected via the Universal Serial Bus (USB). However, given the vast amount of devices, there are some problems that occur frequently for which there are already solutions available on the following wiki page:
-http://wiki.freebsd.org/USB . The %%FreeBSD%% FAQ is the right place for this, so the mini FAQ on the wiki page needs to be transformed into a %%FreeBSD%% FAQ entry. With this, we can point users directly to the FAQ when these kinds of questions come up in the mailing lists.+[[/USB]] . The %%FreeBSD%% FAQ is the right place for this, so the mini FAQ on the wiki page needs to be transformed into a %%FreeBSD%% FAQ entry. With this, we can point users directly to the FAQ when these kinds of questions come up in the mailing lists.
  
 Task requires: Task requires:
Line 546: Line 545:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 12-20 | | Time limit | 12-20 |
-| Mentor | gavin@freebsd.org |+| Mentor | <gavin@freebsd.org> |
 | Requirements | The %%FreeBSD%% developers handbook has a new chapter giving some hints on what is important when benchmarking the system and how to do it properly. | | Requirements | The %%FreeBSD%% developers handbook has a new chapter giving some hints on what is important when benchmarking the system and how to do it properly. |
  
 ==== Description of task ==== ==== Description of task ====
-An important part when enhancing the %%FreeBSD%% operating systems is to know whether or not the added functionality makes the system perform faster than before. In order to do that, benchmarks are being used to collect useful information to make educated comparisons. However, when done wrong, these benchmarks will either not make any sense, provide the wrong data or results in false conclusions drawn by the developer doing the benchmark. To avoid that, a wiki page listing some of the pitfalls when benchmarking is available here: http://wiki.freebsd.org/BenchmarkAdvice+An important part when enhancing the %%FreeBSD%% operating systems is to know whether or not the added functionality makes the system perform faster than before. In order to do that, benchmarks are being used to collect useful information to make educated comparisons. However, when done wrong, these benchmarks will either not make any sense, provide the wrong data or results in false conclusions drawn by the developer doing the benchmark. To avoid that, a wiki page listing some of the pitfalls when benchmarking is available here: [[/BenchmarkAdvice|BenchmarkAdvice]]
 The advice given there needs to be added to the %%FreeBSD%% developers handbook so that people doing benchmarks can be pointed there for doing correct benchmarks. When adding these hints to the developers handbook, the source code for the chapter needs to be correctly formatted and must conform to our documentation source code style guidelines. The advice given there needs to be added to the %%FreeBSD%% developers handbook so that people doing benchmarks can be pointed there for doing correct benchmarks. When adding these hints to the developers handbook, the source code for the chapter needs to be correctly formatted and must conform to our documentation source code style guidelines.
  
Line 565: Line 564:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 10-40 | | Time limit | 10-40 |
-| Mentor | cs@freebsd.org |+| Mentor | <cs@freebsd.org> |
 | Requirements | The descriptions of ports/packages in at least one category are spell and grammar checked and consistently aligned. | | Requirements | The descriptions of ports/packages in at least one category are spell and grammar checked and consistently aligned. |
  
Line 583: Line 582:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 20-30 | | Time limit | 20-30 |
-| Mentor | rpaulo@freebsd.org |+| Mentor | <rpaulo@freebsd.org> |
 | Requirements | The %%FreeBSD%% developer's handbook has a chapter giving some information on DTrace, but it's incomplete. | | Requirements | The %%FreeBSD%% developer's handbook has a chapter giving some information on DTrace, but it's incomplete. |
  
Line 601: Line 600:
 | Difficulty | medium | | Difficulty | medium |
 | Time limit | 20-30 | | Time limit | 20-30 |
-| Mentor | beat@freebsd.org, bcr@%%FreeBSD%%.org |+| Mentor | <beat@freebsd.org>, <bcr@FreeBSD.org> |
 | Requirements | Merge the Ports Subversion Primer from the wiki to the Subversion Primer in the the %%FreeBSD%% developers handbook. | | Requirements | Merge the Ports Subversion Primer from the wiki to the Subversion Primer in the the %%FreeBSD%% developers handbook. |
  
 ==== Description of task ==== ==== Description of task ====
  
-The %%FreeBSD%% ports tree is using the Subversion (SVN) as source code management system. There is a Ports Subversion Primer in the %%FreeBSD%% Wiki http://wiki.freebsd.org/PortsSubversionPrimer describing all the SVN operation needed for Port Committers. In the %%FreeBSD%% developers handbook a Subversion Primer http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html exists where some of the information are already available. The Primer from the wiki needs to be merged into the existing Subversion Primer so that all information for developers is available in one place.+The %%FreeBSD%% ports tree is using the Subversion (SVN) as source code management system. There is a Ports Subversion Primer in the %%FreeBSD%% Wiki [[/PortsSubversionPrimer|PortsSubversionPrimer]] describing all the SVN operation needed for Port Committers. In the %%FreeBSD%% developers handbook a Subversion Primer http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html exists where some of the information are already available. The Primer from the wiki needs to be merged into the existing Subversion Primer so that all information for developers is available in one place.
  
 Task requires: Task requires:
Line 827: Line 826:
  
 But NIS servers are less and less available at some sites while But NIS servers are less and less available at some sites while
-[[/ActiveDirectory|ActiveDirectory]] has massively popularized LDAP. The availability of %%OpenLDAP%%+%%ActiveDirectory%% has massively popularized LDAP. The availability of %%OpenLDAP%%
 (for unix and OS/X) means a Unix/BSD only method of centralized (for unix and OS/X) means a Unix/BSD only method of centralized
 administration is possible but a BSD licensed set of nss and pam modules are administration is possible but a BSD licensed set of nss and pam modules are
Line 895: Line 894:
 | Difficulty | easu | | Difficulty | easu |
 | Time limit | 20 | | Time limit | 20 |
-| Mentor | ''%%eadler@FreeBSD.org%%'' |+| Mentor | ''%%<<MailTo(eadler AT FreeBSD DOT org)>>%%'' |
 | Requirements | a tool similar to patchcheck for Linux | | Requirements | a tool similar to patchcheck for Linux |
  
Line 932: Line 931:
 | Time | 16 | | Time | 16 |
 | Mentor | FREEBSDMENTOR | | Mentor | FREEBSDMENTOR |
-| Requirement (task outcome) | Slick high quality PDFs and [[/HandBook|HandBook]] |+| Requirement (task outcome) | Slick high quality PDFs and Handbook |
 | Description | Hook PDF creation targets into build process. | | Description | Hook PDF creation targets into build process. |
 | Contributor's name | ANONYMOUS | | Contributor's name | ANONYMOUS |
Line 1207: Line 1206:
 | Mentor | FREEBSDMENTOR | | Mentor | FREEBSDMENTOR |
 | Requirements | a tool that will emulate an ISP providing home IPv6 service | | Requirements | a tool that will emulate an ISP providing home IPv6 service |
-| Idea contributor bc979@lafn.org |+| Idea contributor <bc979@lafn.org> |
 | Description | of a task | | Description | of a task |
  
Line 1219: Line 1218:
 | Mentor | FREEBSDMENTOR | | Mentor | FREEBSDMENTOR |
 | A | tool that will identify files that should be included in CVS but are not | | A | tool that will identify files that should be included in CVS but are not |
-| Idea contributor bc979@lafn.org |+| Idea contributor <bc979@lafn.org> |
 | Description | of a task | | Description | of a task |
  
Line 1271: Line 1270:
   * lot of testing.   * lot of testing.
  
-Contributor's name: Volodymyr Kostyrko %%<%%c.kworr@gmail.com>+Contributor's name: Volodymyr Kostyrko <<[[/MailTo|MailTo]](%%<%%c.kworr AT gmail DOT com>
  
 ---- ----
  
-===== Update/Import new IPFilter =====+%%=%%=)>>  Update/Import new IPFilter ==
  
 | Category | Code | | Category | Code |
Line 1510: Line 1509:
  
 Description*: Take directions from a suitable TET mentor (jkoshy??) and get Description*: Take directions from a suitable TET mentor (jkoshy??) and get
-your feet wet with Integrated Testing approaches to software development: +your feet wet with Integrated Testing approaches to software development: [[/TetIntegration|TetIntegration]]
- +
-http://wiki.freebsd.org/TetIntegration+
  
 One day this could make you employable with companies that use %%FreeBSD%% in One day this could make you employable with companies that use %%FreeBSD%% in
Line 1598: Line 1595:
 Time*: 16 Time*: 16
  
-Mentor*: bcr@freebsd.org +Mentor*: <<[[/MailTo|MailTo]](bcr AT freebsd DOT org 
 +)>>
 Requirement (task outcome)*: Usable ZFS chapter in %%FreeBSD%% Handbook about Requirement (task outcome)*: Usable ZFS chapter in %%FreeBSD%% Handbook about
 ZFS pool import/export ZFS pool import/export
Line 1848: Line 1845:
  
 The utility could be a shell script or compiled program. It would The utility could be a shell script or compiled program. It would
-add/manipulate headers related to DKIM and [[/DomainKeys|DomainKeys]].+add/manipulate headers related to DKIM and %%DomainKeys%%.
  
 Contributor's name: ANONYMOUS Contributor's name: ANONYMOUS
Line 2036: Line 2033:
 The tool should ability to serve/convert troff formatted man pages and serve The tool should ability to serve/convert troff formatted man pages and serve
 Markdown formatted text directly from the localhost's /usr/share/docs or Markdown formatted text directly from the localhost's /usr/share/docs or
-handbook/artciles as HTML.+handbook/articles as HTML.
  
 Manual pages can be extended by adding references to handbook and wiki Manual pages can be extended by adding references to handbook and wiki
Line 2152: Line 2149:
 be fetched stored/mirrored at illumos/freebsd/joyent and other ZFS be fetched stored/mirrored at illumos/freebsd/joyent and other ZFS
 implementors. With sun's demise or passing on to a glorious after life we implementors. With sun's demise or passing on to a glorious after life we
-(e.g. Illumos, %%SmartOS%%, %%ZFSonLinux%%, [[/NeXenta|NeXenta]], %%FreeBSD%%) are all "the vendors"+(e.g. Illumos, !%%SmartOS%%, %%ZFSonLinux%%, %%NeXenta%%, %%FreeBSD%%) are all "the vendors"
 now and we should clean up and maintain these error messages. This would now and we should clean up and maintain these error messages. This would
 allow the %%FreeBSD%% proejct to strengthen its collaboration with other ZFS allow the %%FreeBSD%% proejct to strengthen its collaboration with other ZFS
Line 2208: Line 2205:
 Basic firewall / nat/pat working principles. Basic firewall / nat/pat working principles.
  
-Contributor's name: Eugene Grosbein %%<%%eugen@eg.sd.rdtc.ru>+Contributor's name: [[eugen@eg.sd.rdtc.ru|Eugene Grosbein]]
  
 ---- ----
Line 2283: Line 2280:
  
 Description*: Samba is nice. Samba is not nice. It sort of depends on the Description*: Samba is nice. Samba is not nice. It sort of depends on the
-day. Plus Samba is and complicated to set up compared to [[/OpenSolaris|OpenSolaris]]  (and+day. Plus Samba is and complicated to set up compared to %%OpenSolaris%%  (and
 it's GPLv3) it's GPLv3)
  
 the code for CIFS server and client could go int src/cddl (haha!) or just be the code for CIFS server and client could go int src/cddl (haha!) or just be
 made into a port. Better integration with ZFS and vendor support from our made into a port. Better integration with ZFS and vendor support from our
-friends at Illumos, Joyent, [[/OpenIndiana|OpenIndiana]] and Oracle.+friends at Illumos, Joyent, %%OpenIndiana%% and Oracle.
  
 It's nice to have choices It's nice to have choices
Line 2389: Line 2386:
 each container, according to priority. each container, according to priority.
  
-Contributor's name: alberto.esposito@webscientist.us+Contributor's name: <<[[/MailTo|MailTo]](alberto.esposito AT webscientist DOT us
  
 ---- ----
  
-===== Title: WiFox Protocol for FreeBSD 802.11 Stack =====+%%=%%=)>> Title: [[/WiFox|WiFox]] Protocol for %%FreeBSD%% 802.11 Stack ==
  
 Category*: Code, Documentation/Training Category*: Code, Documentation/Training
Line 2412: Line 2409:
 %%FreeBSD%% wireless support is very stable and secure to use in production %%FreeBSD%% wireless support is very stable and secure to use in production
 sites. In a way to improve performance and stability, a new research point a sites. In a way to improve performance and stability, a new research point a
-very large gain with this new protocol. [[/WiFox|WiFox]] - Reference: +very large gain with this new protocol: 
-http://news.ncsu.edu/releases/wms-gupta-wifi+[[http://news.ncsu.edu/releases/wms-gupta-wifi|WiFox Reference]]
 The task is implement this protocol and document his usage. Important: The task is implement this protocol and document his usage. Important:
 Develop in sync to %%FreeBSD%% 10 and downgrade the code to %%FreeBSD%% 9 and Develop in sync to %%FreeBSD%% 10 and downgrade the code to %%FreeBSD%% 9 and
Line 2464: Line 2461:
 | Difficulty | easy, medium, hard | | Difficulty | easy, medium, hard |
 | Time limit | number of **participant's** hours/days for this task | | Time limit | number of **participant's** hours/days for this task |
-| Mentor | ''%%email@freebsd.org%%'' |+| Mentor | ''%%<<MailTo(email AT freebsd DOT org)>>%%'' |
 | Requirements | What do we expect to be there to grade this task as 'completed' | | Requirements | What do we expect to be there to grade this task as 'completed' |
 | Idea contributor | IF YOUR IDEA, EMAIL wkoszek (at) %%FreeBSD%%.org | | Idea contributor | IF YOUR IDEA, EMAIL wkoszek (at) %%FreeBSD%%.org |
Line 2480: Line 2477:
 over the duration of the Google Code-In. This should give you a feeling of what kind over the duration of the Google Code-In. This should give you a feeling of what kind
 of tasks we must have here. of tasks we must have here.
 +
 +----
 +
 +{{tag>Historical}}
  
  • googlecodein/2012tasks.1353712277.txt.gz
  • Last modified: 2012/11/23 23:11
  • by WojciechKoszek