Taskwarrior @foss-gbg

Taskwarrior presentation @foss-gbg 2015-09-16

Transcript

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

   View Slide

2. Taskwarrior software
   

   View Slide

3. todo list
   

   View Slide

4. todo list
   task management
   

   View Slide

5. $ task add Buy milk
   Created task 1.
   $ task add Buy eggs
   Created task 2.
   $ task add Bake cake
   Created task 3.
   

   View Slide

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

   View Slide

7. $ task 1 done
   $ task 2 done
   $ task list
   ID Description
   -- -----------
   1 Bake cake
   1 task.
   

   View Slide

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"]
   

   View Slide

9. command line
   

   View Slide

10. text based
    

    View Slide

11. methodology-neutral
    

    View Slide

12. scales with
    experience
    

    View Slide

13. extensible
    

    View Slide

14. MIT license
    

    View Slide

15. install from source
    or use the packages
    

    View Slide

16. Debian, Ubuntu, Fedora, RHEL,
    OpenSUSE, Archlinux, Slackware,
    Gentoo, Sabayon, FreeBSD,
    OpenBSD, Mac OS X, Cygwin
    

    View Slide

17. http://taskwarrior.org/docs/
    command reference pdf
    task help
    man task
    tutorial movies
    

    View Slide

18. View Slide

19. View Slide

20. Taskserver
    

    View Slide

21. Tools
    Frontends
    Libraries
    Hook scripts
    Extensions
    

    View Slide

22. Taskwarrior project
    

    View Slide

23. $ git log|tail -5
    commit 837527c09989aa093d4c8994c04cadcdbe1491ca
    Author: Paul Beckingham
    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
    

    View Slide

24. Statistics
    

    View Slide

25. View Slide

26. View Slide

27. View Slide

28. View Slide

29. View Slide

30. View Slide

31. Distributions
    

    View Slide

32. Packaging politics
    

    View Slide

33. Packaging politics BS
    

    View Slide

34. Toolshed
    

    View Slide

35. View Slide

36. View Slide

37. View Slide

38. Distributed team
    

    View Slide

39. IRC (#taskwarrior - freenode)
    Slack
    Mail
    

    View Slide

40. Github
    

    View Slide

41. Github
    Gitorious
    

    View Slide

42. Github
    Gitorious
    Stash
    

    View Slide

43. Redmine
    

    View Slide

44. Redmine
    Static & JIRA
    

    View Slide

45. CI
    flod
    

    View Slide

46. View Slide

47. View Slide

48. Sponsoring
    Infrastructure - Rackspace
    Infrastructure - DigitalOcean
    DevTools - Atlassian
    Monitoring - Pingdom
    Statuspage - StatusPage.io
    

    View Slide

49. Sponsoring
    Donations (Paypal)
    

    View Slide

50. Project stories
    

    View Slide

51. Project stories
    War stories
    

    View Slide

52. Feature requests
    

    View Slide

53. supported
    not supported
    not supported
    not supported
    FEATURES
    

    View Slide

54. Every change will ruin
    someone’s day.
    

    View Slide

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

    View Slide

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

    View Slide

57. Users will disguise feature
    requests as bugs.
    

    View Slide

58. Many people will throw
    features requests at you,
    just to show that they are
    clever.
    They don’t want that feature.
    

    View Slide

59. Make them:
    sign up, log in, fill out a
    form for a feature
    request.
    It’s a laziness filter.
    

    View Slide

60. Users usually only think
    incrementally.
    

    View Slide

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

    View Slide

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.
    

    View Slide

63. Documentation
    

    View Slide

64. Users will seek you out
    online to directly ask a
    question that is answered
    two clicks from the front
    page of a website.
    

    View Slide

65. A looping, animated GIF
    will be watched over and
    over. A paragraph of text
    will not be read.
    

    View Slide

66. Man pages are too
    densely crammed with
    information, and too
    long, for modern
    Humans.
    

    View Slide

67. Support questions
    

    View Slide

68. “What have you tried so
    far?” is the best question
    for finding time-wasters.
    

    View Slide

69. User: How do I do X?
    Team: What have you tried so far?
    User: Nothing, I was just wondering...
    

    View Slide

70. View Slide

71. View Slide

72. View Slide

73. Miscellaneous
    

    View Slide

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.
    

    View Slide

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.
    

    View Slide

76. SEO consultants aren’t very
    good at searching the web,
    and identifying all-volunteer
    open-source projects.
    

    View Slide

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.
    

    View Slide