Beginning Development & Documentation Barriers

1,290 views
1,227 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,290
On SlideShare
0
From Embeds
0
Number of Embeds
176
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Beginning Development & Documentation Barriers

  1. 1. Reducing Development Barriers By Natan Yellin
  2. 2. How Do Normal Users Begin Developing?
  3. 3. Case Study: Mac OS X
  4. 4. Step 1: Apple.com
  5. 5. Step 2: Find hidden links
  6. 6. Step 3: Find development links
  7. 7. Step 4: Overview page
  8. 8. Summary  Covers everything developers need to know:  Programming languages  Toolkits  Includes all necessary resources:  Tutorials  API reference  IDE installation  4 clicks only    
  9. 9. Case Study: Ubuntu Linux    
  10. 10. “Linux For Humans”    
  11. 11. Step 1: Ubuntu.com    
  12. 12.    
  13. 13. Just Kidding    
  14. 14. This page doesn't actually tell you anything    
  15. 15. Step 2: Find the link to the Developer Zone    
  16. 16. Step 3: Oh, this helps!    
  17. 17.    
  18. 18. Huh?    
  19. 19. Step 4: Wait a minute...    
  20. 20. Step 4: Wait a minute... Is “Packaging” a synonym for “Programming?”    
  21. 21.    
  22. 22. Umm...    
  23. 23. Umm...    
  24. 24. This isn't about programming!    
  25. 25. 200 Page Views Later....    
  26. 26. We're not even counting the steps any more...    
  27. 27. **Sigh    
  28. 28. Woohoo! An up-to-date developer page    
  29. 29. A Closer Look    
  30. 30. “Last Modified 2006”    
  31. 31. Let's try this anyway...    
  32. 32. Close up:This looks nice    
  33. 33. At last?    
  34. 34.    
  35. 35.    
  36. 36.   ?  
  37. 37. Backtracking    
  38. 38. How are users introduced to development tools?    
  39. 39.    
  40. 40. A Closer Look    
  41. 41. 1 Oops...    
  42. 42. 1 “Last modified 2003”    
  43. 43. 2 “GNOME Bug Tracker”    
  44. 44. 2 “GNOME Bug Tracker” Why is this the first item?    
  45. 45. 3 “GNU Build Tools”    
  46. 46. 3 “GNU Build Tools” Uh oh...    
  47. 47. 3 “GNU Build Tools” The Page of No Return    
  48. 48. Moving on    
  49. 49. http://live.gnome.org/GnomeLove    
  50. 50. This page (surprisingly) is useful http://live.gnome.org/GnomeLove    
  51. 51. It can only be found by clicking on every link on gnome.org http://live.gnome.org/GnomeLove    
  52. 52. Most of it's useful content hasn't been updated in years. http://live.gnome.org/GnomeLove    
  53. 53. Another Example    
  54. 54.    
  55. 55. This one is impossible to find without Google    
  56. 56. These are useful, but only if you already know something about programming    
  57. 57. On the other hand...    
  58. 58. “Oh! So this must be where I install an IDE”    
  59. 59.    
  60. 60. ?    
  61. 61. Never mind...    
  62. 62. Another case study    
  63. 63. Fedora Linux    
  64. 64. Step 1: FedoraProject.org    
  65. 65. Step 2: “Join Fedora”    
  66. 66. Step 2: “Join Fedora”    
  67. 67. Content Writer Designer OS Developer People Person Translator Web Developer or Administrator    
  68. 68. Where is App Developer? Content Writer Designer OS Developer People Person Translator Web Developer or Administrator    
  69. 69. Let's try OS Developer Content Writer Designer OS Developer People Person Translator Web Developer or Administrator    
  70. 70.    
  71. 71. “Design & build OS... develop new features” That sounds like what I'm interested in...    
  72. 72. Wait a minute... Why is there no actual information on getting started?    
  73. 73. Like with Ubuntu, the Fedora development pages don't even link to GNOME's documentation pages. They assume that new developers with no experience will know where to go by themselves. Even if developers do find GNOME's website, all the issues mentioned earlier apply.    
  74. 74.    
  75. 75. Summary    
  76. 76. Three websites and no good documentation...   Fedora  
  77. 77.  There's no central location for documentation­ some  docs are found on distributions websites and some  on project websites. Users don't know where to  look.  Most of the existing documentation (excluding API  reference) isn't up to date.   There are very few tutorials for helping people with  no coding experience write their first program.  The current documentation isn't geared towards  newcomers.    
  78. 78.    
  79. 79. It doesn't have to be this way.    
  80. 80. Proposal: One Developer Resource  Create one central developer website.  This can be hosted at Freedesktop.org.  Clicking on ubuntu.com's “Get Developing” button  should take you to the Freedesktop developer  website.  There still will be a page to learn about packaging on the  Freedesktop website. Now, more people will be able to  use that page after they learn to write their first program.  The website should be a wiki to allow anyone to  update tutorials and documentation.    
  81. 81. Making this happen. 1.We need to setup a wiki at develop.freedesktop.org. 2.We need distributions to support the effort and add  their own documentation to the wiki. 3.When the wiki is in a usable state, we can request that  the distributions work with us to make it fit in  transparently with their own sites and brands. ● E.g. If the user came from FedoraProject.org we can  show them the Fedora logo at the top of each wiki  page along with a link back to FedoraProject.org. ● We can also show Ubuntu users their all­important  guide to packaging at every corner.    
  82. 82. Thank you for listening.    

×