Generated.

[homepage.git] / 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 75d2bd1a88ec0078169a5f79f6a74a6bfb80f79f..e911b2e13aff1814026b9b2928f40b419bc0821b 100644 (file)
--- a/mypapers/free-sw-devel/free-sw-devel.html
+++ b/mypapers/free-sw-devel/free-sw-devel.html
@@ -13,7 +13,7 @@
     <p>An introduction to free software development, for those
       interested in participating.</p>
 
     <p>An introduction to free software development, for those
       interested in participating.</p>
 

-    <p><tt><a href="free-sw-devel.html">http://www.hungry.com/~pere/mypapers/free-sw-devel/free-sw-devel.html</a></tt></p>
+    <p><tt><a href="http://www.hungry.com/~pere/mypapers/free-sw-devel/free-sw-devel.html">http://www.hungry.com/~pere/mypapers/free-sw-devel/free-sw-devel.html</a></tt></p>

 
     <div class="presenter">Petter Reinholdtsen
       <br>pere@hungry.com
 
     <div class="presenter">Petter Reinholdtsen
       <br>pere@hungry.com


@@ -33,7 +33,7 @@
 
       <li>debian developer</li>
 
 
       <li>debian developer</li>
 

-      <li>initiater and current tech coordinator in skolelinux</li>
+      <li>initiator and current tech coordinator in skolelinux</li>

 
       <li>currently employed at USIT, UiO</li>
 
 
       <li>currently employed at USIT, UiO</li>
 


@@ -54,7 +54,8 @@
 
     <h2>Getting involved and helping out</h2>
 
 
     <h2>Getting involved and helping out</h2>
 

-    <p>So, you found a nice project on Freshmeat, and want to help
+    <p>So, you found a nice project on
+      <a href="http://freshmeat.net/">Freshmeat</a>, and want to help

       improve it...</p>
 
     <ul>
       improve it...</p>
 
     <ul>


@@ -63,7 +64,7 @@
       <li>read the project documentation
       <li>join the relevant mailing list, IRC channels, etc
       <li>use mailing lists
       <li>read the project documentation
       <li>join the relevant mailing list, IRC channels, etc
       <li>use mailing lists

-      <li>irc, wiki
+      <li>update the wiki

       <li>get to know the source
       <li>understand licensing issues
       <li>learn to use the bug tracking system (bts)
       <li>get to know the source
       <li>understand licensing issues
       <li>learn to use the bug tracking system (bts)


@@ -92,7 +93,7 @@
 
       <li>add more info if the bug is already reported
 
 
       <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)
       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)


@@ -111,7 +112,7 @@
     <ul>
       <li>if you can fix the problem you are facing, remember to let
         the package author know about this.
     <ul>
       <li>if you can fix the problem you are facing, remember to let
         the package author know about this.

-      <li>make a patch! (<tt>patch -u file.orig file.new >
+      <li>make a patch! (<tt>diff -u file.orig file.new >

       myfix.diff</tt>)
       <li>send the patch to the developer list, or possibly into the
       bts (learn how the developers want it)
       myfix.diff</tt>)
       <li>send the patch to the developer list, or possibly into the
       bts (learn how the developers want it)


@@ -126,24 +127,25 @@
     </ul>      
     
     <h2>Joining a free software project</h2>
     </ul>      
     
     <h2>Joining a free software project</h2>

+    <ul>

 
 

-    <li>start by checking out the bugs in the btw
+    <li>start by checking out the bugs in the bts

     <li>try to fix them
 
     <li>give feedback into the bts on the reported bugs, after trying
     <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>
 
 
     <h2>Starting a free software project</h2>
 


@@ -161,29 +163,44 @@
 
       <li>consider sourceforge
 
 
       <li>consider sourceforge
 

-      <li>
-       

     </ul>
 
     </ul>
 

-     - tools
-   - 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>Use the best free development tools available</h2>

 
 

-    <p>This software suck.  A lot! - Do not take it personally.</p>
+    <ul>
+      <li>compile with lots of warnings
+      <li>use existing libraries, but avoid to many dependencies
+
+      <li>learn to use debugging utilities (gdb, ddd, dmalloc,
+       valgrind, strace, ltrace, electric fence, fncchk, etc)
+      <li>learn to use profiling tools (kprof, gprof, etc)
+      <li>write automatic self testing
+
+      <li>do automatic coverage testing to check the quality of the
+       self test
+
+    </ul>

     
     

-    <h2>Running a successful free software project</h2>
+    <h2>Running a successful free software project I</h2>

 
     <ul>
 
 
     <ul>
 

+      <li>be responsive to comments and suggestions

       <li>write down where you want the project to go
       <li>do not accept every change.  make sure you like it first
 
       <li>let everyone work on the things that interests them, use the
       carrot, as you have no whip
       <li>set up and use a bts
       <li>write down where you want the project to go
       <li>do not accept every change.  make sure you like it first
 
       <li>let everyone work on the things that interests them, use the
       carrot, as you have no whip
       <li>set up and use a bts

+
+    </ul>
+
+    <h2>Running a successful free software project II</h2>
+
+    <ul>
+

       <li>create web pages for your project, include screen shots, a
       short summary and who to contact for more info
       
       <li>create web pages for your project, include screen shots, a
       short summary and who to contact for more info
       


@@ -198,11 +215,17 @@
       commit emails)
       <li>communicate the intention behind the choice of license
     </ul>
       commit emails)
       <li>communicate the intention behind the choice of license
     </ul>

-    
-- prosjektleder

 
 

-    - hold oversikt over hvem som gjør hva
-    - kommuniser prosjektplanen til alle prosjektdeltagerne
+    <h2>As the project grows larger</h2>
+
+    <p>Leading by example is your only option.</p>
+
+    <ul>
+
+      <li>communicate the project plan to all project members
+      <li>try to reduce friction and avoid hard language
+      <li>keep track of what everyone is working on
+    </ul>

 
     <h2>Conclusion</h2>
 
 
     <h2>Conclusion</h2>
 


@@ -210,14 +233,24 @@
 
       <li>working on free software is very rewarding and challenging
 
 
       <li>working on free software is very rewarding and challenging
 

-      <li>nobody owns you a fawour
+      <li>nobody owns you a favour, get used to it

 
 

-      <li>
+      <li>do it for your own gain, not to get rewards from others

       
     </ul>
 
     <h2>References</h2>
 
       
     </ul>
 
     <h2>References</h2>
 

+    <ul>
+
+      <li>"The Practice of Programming" by Kernighan and Pike.
+
+      <li>"<a href="http://opensource.mit.edu/online_paper">Free /
+      Open Source Research Community - online papers</a>,
+      <tt>http://opensource.mit.edu/online_paper</tt></li>
+
+    </ul>
+

     <h2>Thank you very much</h2>
 
     <h3>Questions?</h3>
     <h2>Thank you very much</h2>
 
     <h3>Questions?</h3>