Skip to content
Permalink
Browse files

Problem: depending one external issue trackers has downsides

In certain projects, issues are not just todo-lists that can
be discarded once in a while. In fact, they contain some vital
records on how decisions are made, giving a unique insight
into the reasoning behind them.

However, most of popular options are not great for that. Over time,
services shut down, SCMs go out of fashion, etc.

Solution: design an SCM-agnostic, never-delete-anything issue
tracker.

This commit includes a very basic prototype to start off. It is
not the most efficient or ergonomic implementation. The code can
also use a lot of improvements. There are bugs for sure. You have
been warned. Good luck!
  • Loading branch information...
yrashk committed Jan 28, 2018
0 parents commit f6ed1193d58b031f83aa7bbe4b699cb301a2f6fd
Showing with 1,898 additions and 0 deletions.
  1. +2 −0 .gitignore
  2. +4 −0 .travis.yml
  3. +416 −0 Cargo.lock
  4. +3 −0 Cargo.toml
  5. +202 −0 LICENSE-APACHE
  6. +17 −0 LICENSE-MIT
  7. +148 −0 README.md
  8. +27 −0 sit-core/Cargo.toml
  9. +32 −0 sit-core/src/encoding.rs
  10. +147 −0 sit-core/src/hash.rs
  11. +31 −0 sit-core/src/id.rs
  12. +30 −0 sit-core/src/issue.rs
  13. +41 −0 sit-core/src/lib.rs
  14. +23 −0 sit-core/src/record.rs
  15. +595 −0 sit-core/src/repository.rs
  16. +10 −0 sit/Cargo.toml
  17. +170 −0 sit/src/main.rs
@@ -0,0 +1,2 @@
target
.idea
@@ -0,0 +1,4 @@
language: rust
rust:
- stable
- nightly

0 comments on commit f6ed119

Please sign in to comment.
You can’t perform that action at this time.