Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>

[[ 🗃 ^yEzqv rel4tion-wiki ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🛠 Commits]

Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

Tags

master :: projects /

issue-tracking.mdwn

Issue Tracking

I built a simple initial ontology around issue tracking. I want to examine some issue trackers and decide how I’m going to track my issues until I have my own working software (or anything which uses my semantic model).

Here’s a table from wikipedia:

http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems)

But some tools are missing: Distributed bug trackers. So here’s a list of some:

I want to go over the ones in the Wikipedia table and examine features. First, here’s a list of features from the Wikipedia table:

And more features I see while checking the software from the list:

—————————————————————————————–


Listen. I checked out things, and thought a lot and wrote a lot. There’s no way to have aspect-tagged issues and tasks with dependencies. I need to write an application with an RDF storage backend. This is not trivial, because after getting the graph from there I need to decide how I update it, how the data is loaded into a GUI widget and so on. Hmmm… is there no simple solution to this???

No, there isn’t.

I’m continuing with libKort then. Later I’ll work on the statement-based API and use libKort as a file-based backend for it.


Another update, I’m installing Redmine and moving all my tasks there. Later I will export the sqlite database to XML and import it into my own system.

[See repo JSON]