Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

“taskwarrior“ & “timewarrior“ snowblock decommission #253

Closed
arcticicestudio opened this issue Apr 15, 2020 · 1 comment · Fixed by #254
Closed

“taskwarrior“ & “timewarrior“ snowblock decommission #253

arcticicestudio opened this issue Apr 15, 2020 · 1 comment · Fixed by #254

Comments

@arcticicestudio
Copy link
Owner

arcticicestudio commented Apr 15, 2020

Related to #248


Both snowblocks for Taskwarrior and Timewarrior are not required anymore since they have been replaced with my own custom 💙 Go application that is currently private/closed source, but planned to be open sourced later on.
Both tools are great and provide a lot of features, but are also kind of overloaded with unused and unnecessary functions. I also missed the possibility to integrate the data and API into my other Go applications as well as web-based projects with a quite more modern techstack (Protocol Buffers, NATS Messaging, React SPA etc.).

Therefore the snowblocks will be removed while the data is still available through the Git repository history/logs.

@arcticicestudio arcticicestudio added this to the Next milestone Apr 15, 2020
arcticicestudio added a commit that referenced this issue Apr 15, 2020
Both snowblocks for Taskwarrior [1] and Timewarrior [2] are not required
anymore since they have been replaced with my own custom 💙 Go [3]
application that is currently private/closed source, but planned to be
open sourced later on.
Both tools are great and provide a lot of features, but are also kind
of overloaded with unused and unnecessary functions. I also missed the
possibility to integrate the data and API into my other Go applications
as well as web-based projects with a quite more modern techstack
(Protocol Buffers [4], NATS [5] Messaging, React SPA [6] etc.).

Therefore the snowblocks have been removed while the data is still
available through the Git repository history/logs [7].

[7]: https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History
[3]: https://go.dev
[1]: https://taskwarrior.org
[2]: https://timewarrior.net
[5]: https://nats.io
[4]: https://developers.google.com/protocol-buffers
[6]: https://reactjs.org

GH-253
Related to GH-248, GH-253, GH-131

Co-authored-by: Sven Greb <[email protected]>
arcticicestudio added a commit that referenced this issue Apr 15, 2020
Both snowblocks for Taskwarrior [1] and Timewarrior [2] are not required
anymore since they have been replaced with my own custom 💙 Go [3]
application that is currently private/closed source, but planned to be
open sourced later on.
Both tools are great and provide a lot of features, but are also kind
of overloaded with unused and unnecessary functions. I also missed the
possibility to integrate the data and API into my other Go applications
as well as web-based projects with a quite more modern techstack
(Protocol Buffers [4], NATS [5] Messaging, React SPA [6] etc.).

Therefore the snowblocks have been removed while the data is still
available through the Git repository history/logs [7].

[7]: https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History
[3]: https://go.dev
[1]: https://taskwarrior.org
[2]: https://timewarrior.net
[5]: https://nats.io
[4]: https://developers.google.com/protocol-buffers
[6]: https://reactjs.org

Closes GH-253
Related to GH-248, GH-253, GH-131

Co-authored-by: Sven Greb <[email protected]>
arcticicestudio added a commit that referenced this issue Apr 16, 2020
The pip [1] snowblock was only added in GH-141 in order to track
installed packages [2] and their versions through a `requirements.txt`
[3] file. The only tracked package was `taskw` [4] which was required
for the taskwarrior snowblock [5] to allow to use custom hooks to
interact with Taskwarrior API (the package is not available via
Homebrew). Anyway, since both the taskwarrior [5] and timewarrior [6]
snowblocks have also been decommissioned in GH-253 the "pip" snowblock
is now also not required anymore and has therefore been removed while
the data is still available through the Git repository history/logs [7].

[1]: https://pypi.org/project/pip
[2]: https://packaging.python.org/tutorials/installing-packages/#requirements-files
[3]: https://pip.pypa.io/en/latest/user_guide/#requirements-files
[4]: https://pypi.org/project/taskw
[5]: https://github.com/arcticicestudio/igloo/tree/master/snowblocks/taskwarrior
[6]: https://github.com/arcticicestudio/igloo/tree/master/snowblocks/timewarrior
[7]: https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History

GH-255
Related to GH-248, GH-253, GH-131

Co-authored-by: Sven Greb <[email protected]>
arcticicestudio added a commit that referenced this issue Apr 16, 2020
The pip [1] snowblock was only added in GH-141 in order to track
installed packages [2] and their versions through a `requirements.txt`
[3] file. The only tracked package was `taskw` [4] which was required
for the taskwarrior snowblock [5] to allow to use custom hooks to
interact with Taskwarrior API (the package is not available via
Homebrew). Anyway, since both the taskwarrior [5] and timewarrior [6]
snowblocks have also been decommissioned in GH-253 the "pip" snowblock
is now also not required anymore and has therefore been removed while
the data is still available through the Git repository history/logs [7].

[1]: https://pypi.org/project/pip
[2]: https://packaging.python.org/tutorials/installing-packages/#requirements-files
[3]: https://pip.pypa.io/en/latest/user_guide/#requirements-files
[4]: https://pypi.org/project/taskw
[5]: https://github.com/arcticicestudio/igloo/tree/master/snowblocks/taskwarrior
[6]: https://github.com/arcticicestudio/igloo/tree/master/snowblocks/timewarrior
[7]: https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History

Closes GH-255
Related to GH-248, GH-253, GH-131

Co-authored-by: Sven Greb <[email protected]>
@dimas-cyriaco
Copy link

@arcticicestudio do you still intend to release this go project. I'm very interested in check it out. Was planning in doing something like this myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants