Home Explore Help
Register Sign In
fr33domlover
/
Rel4tion-Wiki
mirror of git://seek-together.space/wiki.git
Watch 1
Star 0
Fork 0
Files Issues 0 Wiki
Branch: master
Branches Tags
Rel4tion-Wiki
/
projects
/
issue-tracking.mdwn

issue-tracking.mdwn 2.5 KB
Permalink History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455 
  1. Issue Tracking
    2. 

  2. ===============
    3. 

  3. 

  4. 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).
    5. 

  5. 

  6. Here's a table from wikipedia:
    7. 

  7. 

  8. <http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems)>
    9. 

  9. 

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

  11. 

  12. * Bugs Everywhere
    13. 

  13. * ditz
    14. 

  14. * ticgit
    15. 

  15. * Fossil
    16. 

  16. * Veracity
    17. 

  17. 

  18. 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:
    19. 

  19. 

  20. + Storage support for SQL databases, flat file and version control
    21. 

  21. + License: Consider using AGPL to enforce availability of source code for software used over the internet
    22. 

  22. + Generating report and scheduling their generation and mailing, RSS
    23. 

  23. + Integration with documentation and wiki
    24. 

  24. + Test planning integration
    25. 

  25. + Customizable workflow
    26. 

  26. + Unicode support
    27. 

  27. + Custom fields
    28. 

  28. + Plugin API
    29. 

  29. + Multiple projects
    30. 

  30. + Full-text search
    31. 

  31. + Indexed full-text search
    32. 

  32. + Indexed file search
    33. 

  33. + Input interfaces: Web, email, CLI, GUI, REST, SOAP, XML-RPC, JSON-RPC
    34. 

  34. + Notification interfaces: Email, RSS, Atom, XMPP, Twitter, IRC
    35. 

  35. + Version control system integration
    36. 

  36. + Authentication methods: Form based, public key cryptography, two-factor, openID, OAuth, LDAP, Shibboleth
    37. 

  37. 

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

  39. 

  40. + Attachments (e.g. screenshots) and patches to messages/bugs/comments (like in Bugzilla)
    41. 

  41. 

  42. -----------------------------------------------------------------------------------------
    43. 

  43. -----------------------------------------------------------------------------------------
    44. 

  44. -----------------------------------------------------------------------------------------
    45. 

  45. 

  46. 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???
    47. 

  47. 

  48. No, there isn't.
    49. 

  49. 

  50. 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.
    51. 

  51. 

  52. ----------------
    53. 

  53. 

  54. 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.
    55. 

  55.