docs/developer.html

   1 <!--#include file="header.html" -->
   2
   3
   4 <h3>Developer Access</h3>
   5
   6 Because we use Git for version control, you don't need developer (ssh)
   7 access on uclibc.org to contribute to Buildroot, but you can request
   8 it if needed.
   9
  10 <p>
  11
  12 To obtain developer access, you will need to demonstrate you are
  13 serious by submitting a few good patches first.  Then, you will need
  14 to select a username to use when logging in, you will need to send me
  15 the username you have selected, you must send me your preferred
  16 contact email address, and finally, you must send me an ssh version 2
  17 DSA key with 1024 bits (the default) or more.  If you do not currently
  18 have an ssh version 2 DSA key, you can generate a key using the
  19 command<pre>ssh-keygen -t dsa</pre> This will create the
  20 files <pre>/home/&lt;USERNAME&gt;/ssh/id_dsa
  21 /home/&lt;USERNAME&gt;/.ssh/id_dsa.pub</pre> It is recommended that
  22 you generate a key with a "passphrase" for security reasons.
  23
  24 <p>
  25 Make the file known to the system by running
  26
  27 <pre>ssh-add ~/.ssh/id_dsa</pre>
  28
  29 You must then send the content of 'id_dsa.pub' to me so I can setup your account.
  30 The content of 'id_dsa' should of course be kept secret.
  31
  32 <p>
  33
  34 Once you have an account, you can use it to store Git
  35 repositories. Simply put them in subdirectories of your ~/git, and
  36 touch ~/git/<repo>/git-daemon-export-ok, after which the hourly
  37 cronjob will pick them up and show them in cgit. They are also
  38 available though git-daemon:
  39
  40 <pre>git clone git://git.buildroot.net/~&lt;USERNAME&gt/git/&lt;REPO&gt;</pre>
  41
  42 For additional detail on how to use Git, please visit the
  43 <a href="http://git-scm.org/">the Git website</a>.
  44
  45 <!--#include file="footer.html" -->
  46
  47