Resources for Technologists

Contents 1 Why hack for humanity? 2 Why Open Source? 3 ICT for Development 4 Getting Started 5 Documentation 6 Open Source Community Building 7 Managing an Open Source Project 8 Security 9 QA/Testing 10 Fund-raising 11 Product Management 12 Marketing 13 Design and User Experience 14 Open Hardware 15 Building a Startup with Your Project 16 Learning GitHub 17 Learning Development 18 YouTube Channels 19 Communities for Developers 20 On-line Courses 21 Principles of Good Code 22 Reducing "Code Smell"

[edit] Why hack for humanity?

• It feels good to help people, especially when it's fun
• Learning about new technologies and social sector subjects
• Practice and use your skills to benefit humanity
• Opportunities to build your reputation

[edit] Why Open Source?

• Open source gives people the freedom to use, learn, improve and share. This lowers barriers for those with the least resources.

[edit] ICT for Development

• Work On Stuff That Matters: Video Interview with Tim O'Reilly
• Tim O'Reilly Work on Stuff that Matters
• Leveraging Information and Communication Technology (ICT) for the Base of the Pyramid (BoP)
• Ending poverty with software using globally distributed teams to tackle difficult problems
• A Study and Report on Open Source Health Information Technology Systems

[edit] Getting Started

• Getting started in Free and Open Source

[edit] Documentation

• How to Write Software Documentation
• Effectively Managing Documentation for Open-Source Projects

[edit] Open Source Community Building

• Build Your Own Contributors (One Part at a Time)
• Crunching the Numbers: Open Source Community Metrics

[edit] Managing an Open Source Project

• Linus Torvalds’s Lessons on Software Development Management
• What I Learned From Releasing My First Open Source Project
• Code Stewardship

[edit] Security

• EFF Guidelines for securing open source software

[edit] QA/Testing

• Saving Time and Improving Software Quality Using Checklists

[edit] Fund-raising

• How to Raise Millions of Dollars Using Open Source Software

[edit] Product Management

• Product launch and pre-launch checklist
• The role of face-to-face meetings in technology-supported self- organizing distributed teams

[edit] Marketing

• Marketing your Open Source Project on a Shoestring Budget

[edit] Design and User Experience

• Grokkin' Design
• Ten Usability Epiphanies for Your Open Source Web-app Presentation
• Designing for Engagement with Gamification in Open Source
• Creating and Designing the User Experience
• Applying Systems Design for the Ideal User Experience

[edit] Open Hardware

• Open Circuits is a wiki for sharing open source electronics knowledge, schematics, board layouts, ports and parts libraries
• Harkopen is an open source hardware community
• Case Studies of Open Source Hardware Projects:The Nuclear Accident in Japan
• iFixit is a Wikipedia of repair
• Opening up hardware projects
• Opening sourcing the engineering process

[edit] Building a Startup with Your Project

• Pricing software
• The Role of Open Source in Creating Competitive Markets
• So, You Think You Want to Start an Open Source Business

[edit] Learning GitHub

• GitHub Help
• Git is Simpler
• GitCasts

[edit] Learning Development

• Google Code University
• Programming constructs

[edit] YouTube Channels

• phpacademy channel - covers php,mysql,jquery
• thenewboston channel - covers java,c++,c,python,after affects,php,dreamweaver,3Ds max
• MIT's channel -search playlists for actual MIT computer class lectures!
• Google's Python classes - covers python (not a channel)
• briantwill's channel - *covers hardware/os, general beginning programming, python, java, C, clojure *

[edit] Communities for Developers

• Reddit Programming
• Reddit Learn Programming
• Stackoverflow

[edit] On-line Courses

• MIT
• Stanford
• Khan Academy
• The New Boston

[edit] Principles of Good Code

• Code should be single-purpose, self contained, predictable, unit testable, documented
• Use comments for every function, method, class, object property, constant, parameter
• Unit test
• Reduce Cyclomatic complexity wherever possible (no more than 3 indentations)

[edit] Reducing "Code Smell"

http://www.codinghorror.com/blog/2006/05/code-smells.html

Recommended Reading for Developers http://www.codinghorror.com/blog/2004/02/recommended-reading-for-developers.html http://www.artima.com/intv/fixit.html http://www.artima.com/intv/dry3.html Learning to Love Unit Testing - http://media.pragprog.com/articles/other-published-articles/stqe-01-2002.pdf Art in Programming - http://media.pragprog.com/articles/other-published-articles/ArtInProgramming.pdf Pipelines - http://media.pragprog.com/articles/nov_03_pipelines.pdf Agile software principles - http://agilemanifesto.org/principles.html Code Stewardship - http://c2.com/cgi/wiki?CodeStewardship

Contributing without code Advocacy - Introducing new people to RHoK - Blog posts, video, screencasts, twitter, Facebook Design - Collateral - UX/UI Documentation - User documentation Project Management - Issue/bug wrangling - Organization Support - Forums - Issues/bug reports - Sitting down next to someone Testing - Setting up for testing - Writing bug reports - Applying fixes Translation - The RHoK site - New translations - Fixing translations