What is Reddit's opinion of TaskBoard?

From 3.5 billion Reddit comments

> Is that because it's easier to add/complete items

Yeah. Plus a few other reasons:

• I've started putting due dates on things that should be done soon (even if they don't have to be), I space them out over the next week or so, so that there's just a few per day. It makes me more mentally inclined/guilty to get all the "today" things done before going to bed. Trello has due dates too I know, but there's not really a screen to group cards from different lists together by date.
• Has reminders.
• Can repeat tasks, like in a calendar. I use this quite a bit for regular things I need to get done.
• Everything is just clearer in general specifically for the job of a task list.
• Phone app layout is more suitable for a list of tasks to get done.
• Makes a "ding" sound when you tick something off.

I'll still keep using Trello for project ideas n stuff, or might install http://taskboard.matthewross.me/ which is self hosted, and I prefer its interface a little better.

In terms of open source alternatives, I used http://taskboard.matthewross.me/ for a while.

But it doesn't really have any calendar/wiki type features.

But in the end went back to Trello for stability (mostly) and mobile access (only use it sometimes).

I use JWTs for authentication with TaskBoard and they work really well. Each request from the app (it's an Angular SPA) sends the JWT in the header and the PHP back-end authenticates the request using the JWT.

The user's JWT is assigned when they log in, and is kept in Local Storage to allow the app to access it for API calls.

I did this by providing default users to demo with (see here). I give both an admin user and a standard user so potential user of my app can try it out from both sides.

EDIT: Of course, this is a customized install specifically for demo purposes. However, creating a user for demo purposes may still be useful.

I don't know if it's "low overhead" but you could use TaskBoard for this (disclaimer, I made it).

Here's the GitHub and the site with docs

It's all about how you set up and use the columns. Trello was originally conceived for doing Kanban-style development. The idea is you set up different columns for each possible stage of a task or issue, and move items horizontally across as you work on them. The simplest organization is To-Do/Doing/Done, which is basically a to-do list, but you can set up something like this agile workflow meant for a team that goes into detail about each stage from conception to release.

One key Kanban concept is that most of the columns have limits to the number of items in them, making it easy to see when people are working at capacity. e.g. for a team the max number of "In progress items" might be the number of team members.

If you want a self-hosted Trello, TaskBoard is pretty good, though it can be tricky to set up on shared hosting.

While my project doesn't tick all those boxes, it might still be something worth looking at. There is a lot planned out (look at the issues) which will cover some of those things.

Also, it's free and open source so it would be easy for you to modify (and I'd love pull requests).

I recently switched from using Thunderbird to just using the Gmail interface.

I was looking into using something like fetchmail to store email backups, but considering I already have Thunderbird set up to download everything using POP3, I just left that in place. Additional bonus is that I've got a full email interface into my "backup archive", which comes in handy occasionally.

POP3 is obviously better for backing up, as server deletions don't get synced to my backup. No automatic backup of Gmail labels/filters, but those are trivial to set up again. You can export them to a XML file under Gmail's settings if you like though.

I leave Thunderbird running anyway as I still use Lightning for my calendar.

I use this for backing up Trello. But I'll probably switch over to this self-hosted alternative when I get around to it.

Sounds like you have a good workflow. The example you gave can be broken down though! I'd give that a new task for 'Learn new API for printing labels', then have the task 'Use API...' later on. But yeah, that still looks really simple compared to the effort required.

In case you're interested in moving away from a spreadsheet, you might like something like the thing I made: TaskBoard.