3 ms·
Do you have any suggestions for what you think distributed issue trackers should look like? My favorite was simple defects with the prophet database backend, b
by codemac 11y ago
Do you have any suggestions for what you think distributed issue trackers should look like?
My favorite was simple defects with the prophet database backend, but it was very "outside" of git and this gave people heartache.
Are there any that you have liked? Ikiwiki changed what I thought version control could be, but I never really used it for a project because I struggled with spam. I'd love to hear your thoughts on the more targeted issue tracker approaches.
- WorldMaker 11y agoI've experimented with a number of them over the years. I even put some effort into my own. Of the off-the-shelf ones, I like the YAML-based ones the best for the artifacts they store in the repository. ditz [1] is the grand-daddy in that space. However, given that the majority of an issue is formatted text, I think the best ones are actually based on a markup language of some sort with an easy to parse frontmatter. The one I built way back when was based on ReStructuredText and used it's nice, easy to RegEx, definition list format as frontmatter. These days I'd probably take the semi-standard "Jekyll" frontmatter approach of YAML+Markdown, and I'm somewhat surprised there still hasn't been a big tool yet (that I've seen) take that approach. (That said, you can admirably fake it with a custom Jekyll collection as-is, so maybe it's something we could build as an interesting template and/or plugin...) [1] http://ditz.rubyforge.org/ http://ditz.rubyforge.org/