bashtickets VS learn

A nice terminal-based ticketing system. https://github.com/tpapastylianou/bashtickets

v2 on master is as simple as it gets, but still incredibly functional; my team is dogfooding the hell out of it at work.

v3 on the "commandbased" branch is a total rehaul on the works, hoping to make this a more traditional/complete package, with a command-based interface (i.e. similar to how git works)

I created something similar when I had to work in an extremely resource-constrained project (we could only work by ssh'ing to a server with no graphical utilities, and no internet access other than ssh). It has worked like a charm, and I would find it difficult to go back to anything else for ticket management now. I use this for 'in-project tickets/milestones' and leave stuff like github issues for 'external' issues by users.

Here it is on github for anyone who's interested: https://github.com/tpapastylianou/bashtickets

My tool is slightly less minimal than the one in the article, but essentially the same philosophy. Everything is a local file following a simple but fixed template, so that they can be grepped / manipulated if necessary. It plays very well with versioning, and supports milestones and 'advanced queries' as pre-made scripts. Obviously, since the tickets/milestones are simple text, it should be fairly straightforward to write your own queries if you know a bit of bash (or any other language you prefer, obviously).

In fact, this little system has worked so well, that I have recently been trying to convert it to a nice, portable, "command-based" tool, i.e. the way git works; bashtickets init (or just bt init) initialises a ticket repository, bt new ticket creates a new ticket, bt list lists open/closed tickets, or active/completed milestones etc. There's nothing wrong with the original, of course, except for the fact that it's a bit ugly to have a bag of scripts in each ticket repository you want to manage. A command-based interface simply makes it look a bit more 'modern', and clean, putting any pre-made scripts and 'template' files out of sight for peace of mind. This is still very much under development, but please see the "commandbased" branch if interested. I'd be very open to feedback :)

I don't have a way to find and curate audiobooks. Plus, LibGen books are already available on IPFS so all I need is collect links. I have been running https://learnawesome.org/ so books seemed far more approachable.

Fantastic! I'll have a deeper look and see if there's any opportunities for integrating this into https://learnawesome.org (which is also open-source).

I am building https://learnawesome.org

It's an attempt to organize world's knowledge. Right now, it looks like GoodReads-like social network for learning resources organized by topics, formats, difficulty levels etc. But there's a knowledge-graph that separates ideas and the medium those ideas are expressed in. For eg: "Sapiens - the book" and "TED Talk given by Yuval Harari" are connected to the same node.

This idea isn't anything new. Here is Danny Hillis talking about it at OSCON 2012: https://youtu.be/wKcZ8ozCah0

https://github.com/learn-awesome/learn for example

Perhaps https://learnawesome.org/.

I have been dealing with the same problem for curating resources at https://learnawesome.org. Projects like Openlibrary do collect unique identifiers for _books_, but for everything else, it mostly takes manual effort. For example, I collect talks/podcasts by the author where they discuss ideas from their books. Then there are summaries written by others.

This is a fantastic effort! Kudos :-)

I have been collecting learning resources and their reviews by experts at https://learnawesome.org/ (open-source, built with Ruby on Rails and TailwindCSS). Would you be kind enough to share the raw JSON files for their books?

LearnAwesome has its own topic taxonomy so it will still require tagging topics manually, but it can save me some effort on scraping/parsing LSE/Nature sites.

I have been adding a number of these free books at https://learnawesome.org/

Do you really care about the format being PDF or is it about the books being FREE? I'd like to make common queries like yours easier. LearnAwesome is open-source, so of course you're free to contribute: https://github.com/learn-awesome/learn