googlecodein:gettingstarted

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:gettingstarted [2011/11/27 18:27] – No need for duplication of information GavinAtkinsongooglecodein:gettingstarted [2020/12/30 02:52] (current) – Remove 1 broken hyperlink. SashaVigole
Line 4: Line 4:
  
 If you have any problems with any of the instructions here, please do feel free to talk to your mentor, or ask on IRC.  There are many mentors available in #freebsd-soc on EFnet, feel free to pop in and say hello even if you are not having issues! If you have any problems with any of the instructions here, please do feel free to talk to your mentor, or ask on IRC.  There are many mentors available in #freebsd-soc on EFnet, feel free to pop in and say hello even if you are not having issues!
 +
 +===== Requirements for Google Code-In tasks =====
 +
 +Most of the Google Code-In tasks require the following:
 +
 +  * A %%FreeBSD%% system (in a [[/VirtualBox|VirtualBox]] Virtual Machine) installed on your computer.  A pre-prepared image along with instructions for use can be found below.  It is recommended that students new to %%FreeBSD%% use this pre-prepared image.
 +  * Knowledge of the documentation guidelines for the %%FreeBSD%% project: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ 
 +  * A copy of the %%FreeBSD%% documentation tree checked out from the %%FreeBSD%% doc repository.  The pre-prepared VM image already contains this, or see below for details on how to obtain this.
 +  * Knowledge on how to research information on the internet
 +  * Thorough work style
  
 ===== Using the pre-prepared VM images ===== ===== Using the pre-prepared VM images =====
  
-The easiest way to get started with the Google Code-In tasks is to download the pre-made Virtual Machine image.  This is available for download from http://people.FreeBSD.org/~gavin/FreeBSD9.0_GCIN.ova (2.2Gb download, SHA256 aa212d1ca717a6a9800e67462ec3456c5e652fea1bba09bb649d6fa3cb0c6ea6).  It is known to work with [[/VirtualBox|VirtualBox]] 4, but should also work with minimal effort on anything supporting the OVF format for virtual machine images, including VMware.+The easiest way to get started with the Google Code-In tasks is to download the pre-made Virtual Machine image.  This is available for download from ''%%people.FreeBSD.org/~gavin/FreeBSD9.0_GCIN.ova%%'' (2.2Gb download, SHA256 aa212d1ca717a6a9800e67462ec3456c5e652fea1bba09bb649d6fa3cb0c6ea6).  It is known to work with [[/VirtualBox|VirtualBox]] 4, but should also work with minimal effort on anything supporting the OVF format for virtual machine images, including VMware.
  
 Once the VM image has been imported, boot it.  The image has been set up so that all your work can either be done on the VM console itself, or over SSH.  After the machine has booted, basic instructions will be shown on the console, including the IP address that the virtual machine has been given.  You can SSH to this IP address (using the gcin account) if you wish to work over SSH rather than directly on the console.  GNOME is also available in the VM image, should you prefer to use the VM directly. Once the VM image has been imported, boot it.  The image has been set up so that all your work can either be done on the VM console itself, or over SSH.  After the machine has booted, basic instructions will be shown on the console, including the IP address that the virtual machine has been given.  You can SSH to this IP address (using the gcin account) if you wish to work over SSH rather than directly on the console.  GNOME is also available in the VM image, should you prefer to use the VM directly.
Line 13: Line 23:
 There are two accounts set up: There are two accounts set up:
  
-| 'username' | 'password' |+| username | password |
 | root | gcin | | root | gcin |
 | gcin | gcin | | gcin | gcin |
Line 42: Line 52:
 ==== Submitting your work ==== ==== Submitting your work ====
  
-The preferred format for submitting work done is in diff format.  To produce a diff of your work, us the "svn diff" command.+The preferred format for submitting work done is in diff format.  To produce a diff of your work, use the "svn diff" command.
  
 For example, to create a diff of changes made to the %%FreeBSD%% handbook, the following command should be used: For example, to create a diff of changes made to the %%FreeBSD%% handbook, the following command should be used:
  • googlecodein/gettingstarted.1322418443.txt.gz
  • Last modified: 2011/11/27 18:27
  • by GavinAtkinson