<div class="presenter">Petter Reinholdtsen
<br>pere@hungry.com
- <br>IFI/UiO, 2004-04-27</div>
+ <br>IFI/UiO, Forskningsparken rom 207 2004-04-27</div>
<h2>Who am I</h2>
<ul>
- <li>Been involved in free software development since 1992</li>
+ <li>been involved in free software development since 1992</li>
- <li>contributor to several projects (linux, glibc, kde, debian,
- mapserver, openstreetmap.org, skolelinux, etc)</li>
+ <li>programmer and system administrator</li>
+
+ <li>past and current contributor to several projects (linux,
+ glibc, kde, debian-{edu, gis, java, cdd}, mapserver,
+ openstreetmap.org, skolelinux, etc)</li>
<li>debian developer</li>
<li>initiater and current tech coordinator in skolelinux</li>
+ </ul>
+
<h2>What is free software</h2>
- user freedom
- freedom to modify
- freedom to distribute
- <h2>Rookie checkin</h2>
+ freedom to run the program as you wish for any purpose, freedom
+to study and change the source code as you wish, freedom to make and
+redistribute copies, and freedom to publish modified versions.
+
+ <h2>Getting involved and helping out</h2>
+
+ - use mailing lists
+
+ <h2>Joining a free software project</h2>
+
+ - painful
- <h2>TBPITW - The Best project in the World</h2>
+ <h2>Making your own project</h2>
+
+ <ul>
+
+ <li>Reuse when possible, improve existing projects</li>
+
+ <li>
- avoid starting from scratch, reuse an existing project if
possible.
- <h2>Joining a free software project</h2>
+
+ <h2>Reporting bugs</h2>
<h2>Starting a free software project</h2>
- - use mailing lists
- public review (anonymous CVS, commit emails)
- bug tracking systems
- licenses
- tools
- compiler
- libraries
- - debugging utilities (gdb, ddd, dmalloc, valgrind, electric fence,
- fncchk, etc)
+ - debugging utilities (gdb, ddd, dmalloc, valgrind, strace, ltrace,
+ electric fence, fncchk, etc)
- avoid duplicate work (check freshmeat)
- søk i bug-databasen til produktet om dette er en kjent feil
- hvis ikke, test siste utgave lokalt
- hvis feilen fremdeles er der, og er gjenproduserbar, send en
- feilrapport
+ feilrapport (valgrind, strace, gdb, ltrace)
- hvis feilen ikke er fikset, men utviklerne er klar over denne,
send en feilrapport til!
- sørg for at feilrapporten inneholder nødvendig informasjon for å
- prosjektleder
+ - hold oversikt over hvem som gjør hva
+ - kommuniser prosjektplanen til alle prosjektdeltagerne
+
<h2>Conclusion</h2>
<h2>References</h2>