Must have open source applications


Published on

Come find out about three great, free-as-in-beer open source applications and why you should be using them. Trac is an outstanding tool that combines web-based project management, a wiki, trouble tickets, and source control under one umbrella. Drupal is an extremely modular content management system with an enormous community of support. And a solid Ruby-on-Rails shopping cart and inventory control system with built-in PayPal and capability.

Published in: Economy & Finance, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Must have open source applications

  1. 1. Open Source for Small Business: What Works, What Doesn't Created and displayed with open source software + Linux Presented by Brian Jamison Must-Have Open Source Applications
  2. 2. Brian Jamison --> <ul><li>Co-Founder of OpenSourcery </li></ul><ul><li>President of POSSE </li></ul><ul><ul><li>Portland Open Source Software Entrepreneurs </li></ul></ul><ul><li>Using open source software to solve business needs since 1995 </li></ul><ul><ul><li>clients: Sony, Nissan, Energizer, Disney... </li></ul></ul><ul><li>Personally using Linux on the desktop since 2001 </li></ul><ul><li>Hiring Ruby on Rails developers / Linux sysadmins </li></ul>
  3. 3. Overview <ul><li>What are the must-have apps and why? </li></ul><ul><li>Trac </li></ul><ul><li>Drupal </li></ul><ul><li>Ruby on Rails commerce app </li></ul>
  4. 4. Trac <ul><li>Basic philosophy: </li></ul><ul><li>project management software is too complex </li></ul><ul><li>doesn't serve the client </li></ul><ul><li>doesn't serve the developer </li></ul>
  5. 5. Trac Project management is not as interesting as design/development
  6. 6. Trac Revision control is not optional
  7. 7. Trac Gracefully handle work out of scope
  8. 8. Trac Manage client signoffs
  9. 9. Trac Answer the client's favorite question: ” Are we there yet?”
  10. 10. Trac Manage client feedback
  11. 11. Trac Clients like to know that you've been working
  12. 12. Trac Installs in 10 minutes
  13. 13. Trac Questions about Trac?
  14. 14. Drupal <ul><li>Content Management is a pain </li></ul>
  15. 15. Drupal <ul><li>Lack of content management tools </li></ul><ul><li>costs you money </li></ul>
  16. 16. Designers have been heard saying <ul><li>” It looks like a CMS site” </li></ul><ul><li>alternatively </li></ul><ul><li>” it's ugly as hell” </li></ul>
  17. 17. Drupal
  18. 18. Drupal
  19. 19. Drupal
  20. 20. Drupal
  21. 21. Drupal
  22. 22. Drupal
  23. 23. Drupal
  24. 24. Drupal <ul><li>Ok, you can make it pretty. </li></ul><ul><li>But what can it do? </li></ul>
  25. 25. Drupal <ul><li>Lots o' Modules </li></ul>”Drupal includes features to enable content management systems, blogs, collaborative authoring environments, forums, newsletters, picture galleries, file uploads and download, and much more.” -A smart person at IBM
  26. 26. Drupal It's reasonably easy to modify modules
  27. 27. Drupal It installs in less than an hour
  28. 28. Drupal Downsides It's in PHP
  29. 29. Drupal Downsides Some modules are b0rken or appallingly bad
  30. 30. Drupal Downsides It's not real intuitive to theme
  31. 31. Some things we've done with it Booking conference rooms Google map mashups Enabling videoconferencing
  32. 32. Drupal Anyone want to see it?
  33. 33. A cart with no name Basic philosophy: Existing open source shopping carts suck spaghetti code difficult/impossible to theme
  34. 34. [Railroad metaphor] cart Ultra-clean default layout No whizzy AJAX crap CSS
  35. 35. [Happy Capitalist Reference] cart Solid ecommerce – extensible to multiple payment gateways
  36. 36. [Gemstone reference] cart Reasonably Rapid Releases Free
  37. 37. [variant of Red] commerce Ruby on Rails / PostgreSQL
  38. 38. [hawaiian word for] commerce demo
  39. 39. [symbolic community word] cart What do you want in an ecommerce application?
  40. 40. Thank you! <ul><li>Now hiring Ruby on Rails developers and Linux System administrators! </li></ul><ul><li>Brian Jamison </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>(503) 544-3558 </li></ul></ul>
  41. 41. <ul><li>Attribution 3.0 </li></ul><ul><li>You are free: </li></ul><ul><ul><ul><li>To copy, distribute, display, and perform the work </li></ul></ul></ul><ul><ul><ul><li>To make derivitave works </li></ul></ul></ul><ul><li>Under the following conditions: </li></ul><ul><li>Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). </li></ul><ul><li>For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page. </li></ul><ul><li>Any of the above conditions can be waived if you get permission from the copyright holder. </li></ul><ul><li>Apart from the remix rights granted under this license, nothing in this license impairs or restricts the author's moral rights.You must give the original author credit. </li></ul><ul><li>For any reuse or distribution, you must make clear to others the license terms of this work. </li></ul><ul><ul><ul><li>Any of these conditions can be waived if you get permission from the author. </li></ul></ul></ul><ul><li>Your fair use and other rights are in no way affected by the above. </li></ul><ul><li>This is a human-readable summary of the Legal Code </li></ul><ul><li>The full license is available here: </li></ul><ul><ul><li> </li></ul></ul>