Hi,

Ever wondered if the tooling for issue tracking can be more like Git -- 
lean, decentralized and adaptable? If yes, read on!

I would like to share a project I've been working on with you. SIT 
(https://sit.sh) is a Serverless Information Tracker with its first 
application in issue tracking. It's a small, 
zero-dependencies tool that allows to keep track of issues and collaborate 
on them in a decentralized way.

Instead of having to setup and maintain a server and a database, or having 
to rely on services of an external third party, SIT is a self-contained 
binary for Linux,
OS X and Windows that typically works on the end-user's computer. SIT's 
medium of record is files. No external database is required.

As far as analogies go, it is doing to issue tracking what Git did to 
version control systems. But lets further elaborate on a few benefits to 
consider:

* Works offline. You can synchronize issues, go offline and work on it 
without needing a connection. You can synchronize at any time later.
* Contextualizes state. When used together with an SCM (such as Git), you 
can see the state of any issue at any given revision (it can answer the 
question of "what release branches is this issue closed on?")
* Continuously localizes data. You can access the data at any time. No API 
rate limits. It's on your file system.
* Adapts to your group topology. Synchronization can be done over Git, 
Dropbox, Keybase, USB flash drives or anything else that allows you to copy 
files between computers.
* Malleable. You can make it handle just about any workflow and payload. 
The customization is in its blood.

It's still at an early stage but it's pretty functional and is steadily 
progressing towards 1.0. The issue tracking module has a simple and useful 
UI as well. One thing that really makes me a happy user of it is how it 
does Merge Requests. Because everything is files, these requests are 
effectively becoming first-class citizens and you can do pretty interesting 
things -- like opening or changing existing issues within a merge request, 
so that when it's merged all these changes would automatically apply.

You can find more details at https://github.com/sit-it/sit and I will be 
happy to answer any questions!

Yurii.

P.S. I apologize if I just stole your weekend :)

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to