8 ms·

I went through a CLI phase were I tried to do everything there, including calendar, sideshows, email etc. The thing that makes Kanban useful is the collaborati

I went through a CLI phase were I tried to do everything there, including calendar, sideshows, email etc. The thing that makes Kanban useful is the collaboration in a team. I doubt a whole team would agree to use this tool though.

petemir 4y ago
Please, how did you get out of it?
- jcbrand 4y ago
  (After work) I sometimes lie on the couch with my laptop on my stomach. Having to do everything via the keyboard and CLI (I even disabled my touchpad) became a hassle and over time I slowly started using the mouse and GUIs again.
tlamponi 4y ago
> I doubt a whole team would agree to use this tool though. Definitively, but it could work if was just one of the possible frontends and create another, for example, web based frontend. That naturally adds quite a bit of complexity as you either need a central server app that holds the source of truth or handle merging otherwise, be it by let the user take care (e.g., holding it as somewhat merge friendly text records in git) or do come up with some automatic conflict resolution. IMO that shows why developing and using such CLI tools is somewhat popular; it's really simple to do but often then only works for a single person or a team with a very similar mindset in the usage/tooling regard.
rsolva 4y ago
It is possible to use calDAV, cardDAV etc to sync tasks, contacts and calenders independent of the client you use. I have been doing this exercise the past few days with one guy who does everything in the CLI (mutt, todoman etc) while I have been using Thunderbird. It kinda works, but you have to forgo some features that are not supported by booth clients to make it work. It's rather basic feature set; no sub-task support for example. But I do not know of any other way to sync tasks and calenders across a team where preferences for different clients and tools vary.
- zorr 4y ago
  This would be the ideal solution for collaboration. A shared *DAV server as a datastore where everyone can bring their own client. Unfortunately this breaks down rather quickly as the various calDAV and cardDAV implementations vary wildly for features outside of simple task lists. About a year ago I tried configuring sync between Linux/Windows/MacOS/Android and failed. I documented my search here [1]. 1. https://stevenvanbael.com/open-calendar-task-space-is-a-mess https://stevenvanbael.com/open-calendar-task-space-is-a-mess
  - pc86 4y ago
    This comment reminded me of this sentiment[0] I'd like to echo here. Central server of some open or semi-open standard where "everyone can bring their own client" is not realistic for most solutions, because most people just don't give a shit. It's great for nerds like us, but not so much... anyone else. [0] https://twitter.com/levelsio/status/1572973761300774915 https://twitter.com/levelsio/status/1572973761300774915
    - zorr 4y ago
      Unfortunately that tweet is pretty accurate for a lot of fields. Although there are examples that show it can be done. Look at email and Git for example, or HTTP, WebRTC and browser js/css in general. I think it is up to us OSS nerds to keep working towards a world that is more interoperable, preferring protocols over implementations. It is either that or giving up entirely and rolling over to the whims of Google, Meta and other big corps. In the two minutes it took me to write this comment Google has released two new chat apps, fragmenting my contact list even more /s.

petemir 4y ago

Please, how did you get out of it?

jcbrand 4y ago
(After work) I sometimes lie on the couch with my laptop on my stomach. Having to do everything via the keyboard and CLI (I even disabled my touchpad) became a hassle and over time I slowly started using the mouse and GUIs again.

tlamponi 4y ago

> I doubt a whole team would agree to use this tool though. Definitively, but it could work if was just one of the possible frontends and create another, for example, web based frontend. That naturally adds quite a bit of complexity as you either need a central server app that holds the source of truth or handle merging otherwise, be it by let the user take care (e.g., holding it as somewhat merge friendly text records in git) or do come up with some automatic conflict resolution. IMO that shows why developing and using such CLI tools is somewhat popular; it's really simple to do but often then only works for a single person or a team with a very similar mindset in the usage/tooling regard.

rsolva 4y ago

It is possible to use calDAV, cardDAV etc to sync tasks, contacts and calenders independent of the client you use. I have been doing this exercise the past few days with one guy who does everything in the CLI (mutt, todoman etc) while I have been using Thunderbird. It kinda works, but you have to forgo some features that are not supported by booth clients to make it work. It's rather basic feature set; no sub-task support for example. But I do not know of any other way to sync tasks and calenders across a team where preferences for different clients and tools vary.

zorr 4y ago
This would be the ideal solution for collaboration. A shared *DAV server as a datastore where everyone can bring their own client. Unfortunately this breaks down rather quickly as the various calDAV and cardDAV implementations vary wildly for features outside of simple task lists. About a year ago I tried configuring sync between Linux/Windows/MacOS/Android and failed. I documented my search here [1]. 1. https://stevenvanbael.com/open-calendar-task-space-is-a-mess https://stevenvanbael.com/open-calendar-task-space-is-a-mess
- pc86 4y ago
  This comment reminded me of this sentiment[0] I'd like to echo here. Central server of some open or semi-open standard where "everyone can bring their own client" is not realistic for most solutions, because most people just don't give a shit. It's great for nerds like us, but not so much... anyone else. [0] https://twitter.com/levelsio/status/1572973761300774915 https://twitter.com/levelsio/status/1572973761300774915
  - zorr 4y ago
    Unfortunately that tweet is pretty accurate for a lot of fields. Although there are examples that show it can be done. Look at email and Git for example, or HTTP, WebRTC and browser js/css in general. I think it is up to us OSS nerds to keep working towards a world that is more interoperable, preferring protocols over implementations. It is either that or giving up entirely and rolling over to the whims of Google, Meta and other big corps. In the two minutes it took me to write this comment Google has released two new chat apps, fragmenting my contact list even more /s.