Re: Fwd: Re: [Savannah-hackers] Beginner howto.

[Loic Dachary]

Jean-Philippe Boisseau writes:
 > 
 > http://perso.wanadoo.fr/j-p.boisseau/savannah_beginner_howto.html
 > 

        I included my comments in the text. Martin A. Brooks proposed
himself to write more documentation, he should be able to provide
comments & additional sections to this howto.

<h1>The Savannah Beginner's Howto</h1>

<table cellpadding="2" cellspacing="2" border="0" width="75%">
<tbody>

<tr>
<td valign="Top"> <div align="justify">This small guide is intended to guive to 
developpers who have few experience of CVS, SSH etc. the notions they need to 
use Savannah. It is not intended to be a real, complete and exaustive reference 
of all tools you can use with Savannah. It just will try to guide full 
beginners during their first steps with free software shared development.<br>
Special thanks to Loic Dachary, who answered all my questions, and allowed me 
to write down these few lines. 


>>> There is no need to include thanks for a small document like this, IMHO.
        
     
     <h2>Overall description</h2>
<p align="justify">Savannah is intended to give to developpers what they need 
to work together on a free project. This means Savannah provides the following 
set of tools.</p>
<ul>
<li>SSH is intended to provide reliable crypted connections between you and 
Savannah servers.</li>
<li>An anonymous FTP server allows to common users to retrieve the files your 
team want to release</li>

>>> There is no ftp server, only a download space that can be used thru http.

<li>An HTTP space, to store the website related to your project needs.</li>
<li>CVS, the Concurrent Versions Systems, is the configuration management tool. 
It allows members of a project to work concurrently on the same files, to 
commit and retrieve all changes in the same database, and to other people to 
retrieve the last "bleeding edge" version of the project code. This database 
helps then to resolve conflicts, to manage and release versions, etc.</li>
</ul>
In the following paragraphs, I'll give you the necessary elements to start 
using each of these tools.<br>
I'll consider you already have an account on Savannah.

>>> I will assume ...
     

     <h2>SSH</h2>

As I said before, SSH provides you crypted connections between you and Savannah 
servers. A program implementing ssh protocol runs on Savannah, and you need 
your own on you computer: that's your ssh client.  Your client will use your 
private key to encrypt the data you send to the server, and the server will use 
your public key to decrypt it. 

>>> on your computer
     
     <h3>Providing yourself a SSH Client</h3> First, let's try to see

>>> getting a SSH client

     if a SSH Client is allready installed on you machine: at shell

>>> on your machine

     prompt, just type "ssh". If your shell doesn't insult you with
     and insane "ssh: command not found", you have a SSH Client: go to
     the next section. Otherwise, you have to install a SSH Client
     package from your Linux/BSD distribution (all distributions

>>> your GNU/Linux or BSD distribution

     include a SSH client).

     <h3>Generating your keys</h3>

This step will make you generate your private and your public keys.<br>
At shell prompt, type "ssh-keygen". Ssh-keygen will ask you file or directories 
names (default values will generally fit you perfectly: just accept them) and a 
passphrase (a password your SSH client will ask you to identify yourself).<brW 
This will generate in your home directory these files : ~/.ssh/identity (your 
private key), ~/.ssh/identity.pub (your public key), ~/.ssh/config (your ssh 
client personnal settings), ~/.ssh/known_hosts (your ssh client authorised 
servers).<br>

>>> For this you may want to cut/paste the instructions that are in the
>>> relevant Savannah page. 
>>> Including actual examples that someone can cut/paste is quite important
>>> in a HOWTO. It makes it a lot easier to quickly read and apply.

<h3>Setting up your key on Savannah Server</h3>

Log in your Savannah account.<br>
Go into the "Account maintenance" section.<br>
In the "Shell Account Information", select the the "[Edit Keys]" link.<br>
You are now able to copy your public (shared) key in the "Shared key" section. 
Be carefull: you have to copy the whole line of your ~/.ssh/identity.pub. This 
normally includes three numbers (the third is the "real" key, that's why it's 
soooo long) and an email address.
     <br>

        Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
12 bd  Magenta         http://www.senga.org/      address@hidden
75010    Paris         T: 33 1 42 45 07 97          address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt