Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Projects, Community and Github

Projects, Community and Github

Andy Lester

October 16, 2011

More Decks by Andy Lester

Other Decks in Programming


  1. What we’ll cover • Presenting your project to the world

    • Managing the development process • Side trip to diversity • Your experiences Sunday, October 16, 11
  2. Why to stay • Perspectives on community & you! •

    Adorable Octocat art! • Tips for patch management! • Star Trek references! • Release management! • Sweaty Steve Ballmer! Sunday, October 16, 11
  3. What's it do? What's it look like? Do I want

    to use it? Sunday, October 16, 11
  4. Make a project site. • Answer the newcomer's questions. •

    Aimed toward the end users. • Users who are not as ninja as you. • Make download + install incredibly obvious. • It can be on github, but not the default github project page. Sunday, October 16, 11
  5. Get your own domain. • Not tied to github, in

    case things change. • $10/year = dirt-cheap investment • Which is easier to remember? • http://github.com/petdance/ack • http://betterthangrep.com/ Sunday, October 16, 11
  6. Release for simplicity • Releases are an affirmation: "Yes, you

    can use this." • Single, verifiable tarball. • Nobody wants to run autoconf. • Users expect them. Sunday, October 16, 11
  7. Release for history and visibility • Lets others build on

    your work. • Maintain an accurate, human-written changelog of all releases. • A dump of commit messages is not a changelog! Sunday, October 16, 11
  8. The needs of the many outweigh the needs of the

    few, or the one. Sunday, October 16, 11
  9. The needs of the users outweigh the needs of the

    project team. Sunday, October 16, 11
  10. About @petdance • Perl guy: ack, prove, WWW::Mechanize • Programming

    for money since the 1980s • I sling PHP for B2B web apps for a midsize corporation. • From the midwest, Chicago area Sunday, October 16, 11
  11. You want to accept changes from newbies if at all

    possible. Sunday, October 16, 11
  12. Don't reject patches just because of... • No tests •

    No documentation • Not following code standards • Those can all be fixed! Sunday, October 16, 11
  13. I am happy to suggest use cases that I have

    found useful. What is the best way - to mailing list, on a wiki somewhere, email to you. Don't quite feel up to being more proactive. I am dyslexic and find writing stuff hard (and finishing of writing etc). Sunday, October 16, 11
  14. Make a project guide • Small chunks of the elephant

    • "TODO: Better error handling" is not helpful to the newbie. • Project direction • Coding standards • Workflow + branch strategy Sunday, October 16, 11
  15. Thank you • Put yourself in the newbie's shoes. •

    Make a project home page outside Github. • Visible, documented releases matter. • Optimize for others, not yourself. • Use Github to encourage your community, not fend it off. • Thank you for listening and for Githubbing. Sunday, October 16, 11