Slide 1

Slide 1 text

Code is only slightly relevant Lightning talk OSDC 2008

Slide 2

Slide 2 text

Nic Steenhout - [email protected] What is OS developer?  Mind reader  Documenter  Fundraiser  Marketer  Insomniac  May just happen to have a life too!  Programmers just wanna code

Slide 3

Slide 3 text

Nic Steenhout - [email protected] OS relies on many aspects  PR / Marketing  If a tree falls in the wood and no one is there to hear, does it make a noise?  Documentation  How do users know how to use the app?  Who’s gonna write it?  Users  Meeting users needs if not all users feedback

Slide 4

Slide 4 text

Nic Steenhout - [email protected] No code, vibrant project No real development for 6 months + Users blogging + Users active on forums + Community built momentum ---------------------------------------- = Very well known project, while no code built

Slide 5

Slide 5 text

Nic Steenhout - [email protected] It’s not a bug – it’s a feature  It’s not a security hole, your server is badly setup!!!  Most important users:  Those reporting bugs  Those who think they found a bug  Way devs think software will be used not the way software used in the wild

Slide 6

Slide 6 text

Nic Steenhout - [email protected] Listen to users!  Go to restaurant  Order steak  Arrives charcoaled instead of medium-rare  Complain, but staff just shrugs  Tell 10 people  Never go back  Imagine that happening to your project!

Slide 7

Slide 7 text

Nic Steenhout - [email protected] User responsibility  They want it, they want it all, and they want it yesterday  FOSS a product like any other – even if free, there is user expectation (rights?¿?)  No rights without responsibility  Dev’s responsibility – listen, don’t dismiss  You never know who you are talking with  Vicious circle / Catch-22 / Chicken vs. Egg

Slide 8

Slide 8 text

Nic Steenhout - [email protected] Feedback != negative criticism  Wanting people to blog about application, good *and* bad  If you don’t know it’s broken, you can’t fix it  Users encouraged to feedback often bring solutions at the same time

Slide 9

Slide 9 text

Thank you!