Slide 1

Slide 1 text

TASKWARRIOR http://taskwarrior.org Federico Hernandez [email protected]

Slide 2

Slide 2 text

Taskwarrior software

Slide 3

Slide 3 text

todo list

Slide 4

Slide 4 text

todo list task management

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

command line

Slide 10

Slide 10 text

text based

Slide 11

Slide 11 text

methodology-neutral

Slide 12

Slide 12 text

scales with experience

Slide 13

Slide 13 text

extensible

Slide 14

Slide 14 text

MIT license

Slide 15

Slide 15 text

install from source or use the packages

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

Taskserver

Slide 21

Slide 21 text

Tools Frontends Libraries Hook scripts Extensions

Slide 22

Slide 22 text

Taskwarrior project

Slide 23

Slide 23 text

$ 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

Slide 24

Slide 24 text

Statistics

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

Distributions

Slide 32

Slide 32 text

Packaging politics

Slide 33

Slide 33 text

Packaging politics BS

Slide 34

Slide 34 text

Toolshed

Slide 35

Slide 35 text

No content

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Distributed team

Slide 39

Slide 39 text

IRC (#taskwarrior - freenode) Slack Mail

Slide 40

Slide 40 text

Github

Slide 41

Slide 41 text

Github Gitorious

Slide 42

Slide 42 text

Github Gitorious Stash

Slide 43

Slide 43 text

Redmine

Slide 44

Slide 44 text

Redmine Static & JIRA

Slide 45

Slide 45 text

CI flod

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

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

Slide 49

Slide 49 text

Sponsoring Donations (Paypal)

Slide 50

Slide 50 text

Project stories

Slide 51

Slide 51 text

Project stories War stories

Slide 52

Slide 52 text

Feature requests

Slide 53

Slide 53 text

supported not supported not supported not supported FEATURES

Slide 54

Slide 54 text

Every change will ruin someone’s day.

Slide 55

Slide 55 text

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

Slide 56

Slide 56 text

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

Slide 57

Slide 57 text

Users will disguise feature requests as bugs.

Slide 58

Slide 58 text

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

Slide 59

Slide 59 text

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

Slide 60

Slide 60 text

Users usually only think incrementally.

Slide 61

Slide 61 text

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

Slide 62

Slide 62 text

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.

Slide 63

Slide 63 text

Documentation

Slide 64

Slide 64 text

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

Slide 65

Slide 65 text

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

Slide 66

Slide 66 text

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

Slide 67

Slide 67 text

Support questions

Slide 68

Slide 68 text

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

Slide 69

Slide 69 text

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

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

No content

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Miscellaneous

Slide 74

Slide 74 text

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.

Slide 75

Slide 75 text

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.

Slide 76

Slide 76 text

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

Slide 77

Slide 77 text

SEO: I can help you double your revenue! Team: We’re an open source, volunteer-only project. Oh look, I just doubled zero myself.