X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/cc3df0d0cf06c49e3d4f843f3e2e3dd40c37a8b3..62c058f8953a44f8898e6c4f67d0c559306cca89:/mypapers/free-sw-devel/free-sw-devel.html

diff --git a/mypapers/free-sw-devel/free-sw-devel.html b/mypapers/free-sw-devel/free-sw-devel.html
index 75d2bd1a88..8c82485ebc 100644
--- a/mypapers/free-sw-devel/free-sw-devel.html
+++ b/mypapers/free-sw-devel/free-sw-devel.html
@@ -92,7 +92,7 @@
 
       <li>add more info if the bug is already reported
 
-      <li>use the relevang bug reporting tool, such as bug-buddy (Gnome),
+      <li>use the relevant bug reporting tool, such as bug-buddy (Gnome),
       perlbug (Perl), reportbug (Debian) and sendpr (FreeBSD) or
       use the projects bug reporting web site (bugzilla, request-tracker,
       gnats, etc. check the project home page)
@@ -126,24 +126,25 @@
     </ul>      
     
     <h2>Joining a free software project</h2>
+    <ul>
 
     <li>start by checking out the bugs in the btw
     <li>try to fix them
 
     <li>give feedback into the bts on the reported bugs, after trying
-    to reproduce
-    them.
+    to reproduce them.
+
+    <li>go through the user documentation, and submit suggestions for
+    improvement
 
-- aktiv prosjektdeltager
+    <li>be active on the mailing lists, provide answers to the
+    questions (and use references tot he user documentation, to save
+    everybody some work)
 
-  - fiks feilene som er rapportert i bugrapport-systemet (prosjektet
-    _har_ et feilrapportsystem, ikke sant?)
-  - Test og gi tilbakemelding på rapporterte feil.
-  - sørg for at brukerdokumentasjonen er oppdatert, og henvis til
-    denne (så slipper du ekstraarbeide)
-  - sørg for at kildekoden du lager er selvdokumenterende, følger
-    kode-policy og har akkurat nok kommentarer til at formålet med
-    koden er lett å forstå
+    <li>make sure the code you write is self documenting, follow the
+    code policy and include enough comments to make the purpose of the
+    code easy to understand.
+    </ul>
 
     <h2>Starting a free software project</h2>
 
@@ -165,14 +166,17 @@
 	
     </ul>
 
-     - tools
+    <p>This software suck.  A lot! - Do not take it personally.</p>
+
+    <h2>Use the best free development tools available</h2>
+
    - compiler
    - libraries
    - debugging utilities (gdb, ddd, dmalloc, valgrind, strace, ltrace,
      electric fence, fncchk, etc)
 
 
-    <p>This software suck.  A lot! - Do not take it personally.</p>
+    
     
     <h2>Running a successful free software project</h2>
 
@@ -198,11 +202,14 @@
       commit emails)
       <li>communicate the intention behind the choice of license
     </ul>
-    
-- prosjektleder
+
+    <h2>As the project grows larger</h2>
+
+    <p>Leading by example is your only option.</p>
 
     - hold oversikt over hvem som gjør hva
     - kommuniser prosjektplanen til alle prosjektdeltagerne
+    - reduce friction and avoid hard language
 
     <h2>Conclusion</h2>