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

Taskwarrior @foss-gbg

8e8f28274472851dde2ad480b8166522?s=47 Taskwarrior
September 16, 2015

Taskwarrior @foss-gbg

Taskwarrior presentation @foss-gbg 2015-09-16



September 16, 2015

Other Decks in Technology


  1. TASKWARRIOR http://taskwarrior.org Federico Hernandez f@ederi.co

  2. Taskwarrior software

  3. todo list

  4. todo list task management

  5. $ task add Buy milk Created task 1. $ task

    add Buy eggs Created task 2. $ task add Bake cake Created task 3.
  6. $ task list ID Description -- ----------- 1 Buy milk

    2 Buy eggs 3 Bake cake 3 tasks.
  7. $ task 1 done $ task 2 done $ task

    list ID Description -- ----------- 1 Bake cake 1 task.
  8. $ cat .task/pending.data [description:"Buy milk" entry:"1442349664" modified:"1442349664" status:"pending" uuid:"d385005e-e00e-49ca-860d-886dfaaeab7e"] [description:"Buy

    eggs" entry:"1442349671" modified:"1442349671" status:"pending" uuid:"9f5bfe76-2ca1-4f15-accc-437dde42d54e"] [description:"Bake cake" entry:"1442349679" modified:"1442349679" status:"pending" uuid:"68272ee9-8d5d-463f-9cb3-512ebab58454"]
  9. command line

  10. text based

  11. methodology-neutral

  12. scales with experience

  13. extensible

  14. MIT license

  15. install from source or use the packages

  16. Debian, Ubuntu, Fedora, RHEL, OpenSUSE, Archlinux, Slackware, Gentoo, Sabayon, FreeBSD,

    OpenBSD, Mac OS X, Cygwin
  17. http://taskwarrior.org/docs/ command reference pdf task help man task tutorial movies

  18. None
  19. None
  20. Taskserver

  21. Tools Frontends Libraries Hook scripts Extensions

  22. Taskwarrior project

  23. $ git log|tail -5 commit 837527c09989aa093d4c8994c04cadcdbe1491ca Author: Paul Beckingham <paul@beckingham.net>

    Date: Sat Apr 19 21:54:30 2008 -0400 - Initial commit. $ git tag|grep v|wc -l 42 $ whois taskwarrior.org Domain Name:TASKWARRIOR.ORG Creation Date: 2009-05-22T16:19:35Z
  24. Statistics

  25. None
  26. None
  27. None
  28. None
  29. None
  30. None
  31. Distributions

  32. Packaging politics

  33. Packaging politics BS

  34. Toolshed

  35. None
  36. None
  37. None
  38. Distributed team

  39. IRC (#taskwarrior - freenode) Slack Mail

  40. Github

  41. Github Gitorious

  42. Github Gitorious Stash

  43. Redmine

  44. Redmine Static & JIRA

  45. CI flod

  46. None
  47. None
  48. Sponsoring Infrastructure - Rackspace Infrastructure - DigitalOcean DevTools - Atlassian

    Monitoring - Pingdom Statuspage - StatusPage.io
  49. Sponsoring Donations (Paypal)

  50. Project stories

  51. Project stories War stories

  52. Feature requests

  53. supported not supported not supported not supported FEATURES

  54. Every change will ruin someone’s day.

  55. If a feature works well, you’ll never hear about it

  56. People only get excited about something a project doesn’t quite

    yet support.
  57. Users will disguise feature requests as bugs.

  58. Many people will throw features requests at you, just to

    show that they are clever. They don’t want that feature.
  59. Make them: sign up, log in, fill out a form

    for a feature request. It’s a laziness filter.
  60. Users usually only think incrementally.

  61. People threaten to not use software if it lacks their

    favourite feature.
  62. User: Does $PRODUCT support $TECHNOLOGY? Team: No, it doesn’t. User:

    I can’t see myself using $PRODUCT unless it supports $TECHNOLOGY. Team: Sorry, there are no plans to add that. User: Well, you’re going to lose a customer. Team: This is open source, there are no customers.
  63. Documentation

  64. Users will seek you out online to directly ask a

    question that is answered two clicks from the front page of a website.
  65. A looping, animated GIF will be watched over and over.

    A paragraph of text will not be read.
  66. Man pages are too densely crammed with information, and too

    long, for modern Humans.
  67. Support questions

  68. “What have you tried so far?” is the best question

    for finding time-wasters.
  69. User: How do I do X? Team: What have you

    tried so far? User: Nothing, I was just wondering...
  70. None
  71. None
  72. None
  73. Miscellaneous

  74. People will pick arguments with you about incidental things, such

    as your choice of bug database, branch names, version numbers, text editor used, PDF writer and so on.
  75. User: Why are you using $BUG_DB, when you could be

    using $ALTERNATIVE? Team: We like it. User: But $ALTERNATIVE is open source! Team: Our $PRODUCT is open source. That’s the part we care about and focus on.
  76. SEO consultants aren’t very good at searching the web, and

    identifying all-volunteer open-source projects.
  77. SEO: I can help you double your revenue! Team: We’re

    an open source, volunteer-only project. Oh look, I just doubled zero myself.