I'm impressed! One just probably need a bugs branch to get things
working and gitorious can look into this and show issues related to the
repo (or project if needed). Thanks for the pointer.
On 05/07/2011 16:53, Guilhem Bonnefille wrote:
2011/7/5 Christian Johansen<christ...@cjohansen.no>:
As for the discussion on issue tracking and Gitorious in general: I agree
that if/when issue tracking becomes a part of Gitorious (pluggable in some
way) - i.e. something we offer projects hosted with us - shipping something
which is distributed is key. We've been mulling over this a lot, and even
looked at a few such systems backed by Git. I don't know yet exactly how it
would work, but I want an issue tracking system that:
stores issues in plain text (so they can be put in Git)
can be distributed
has a CLI for programmer efficiency
has pluggable nice UI for stake-holders
Obviously, as Rodrigo said, we likely won't be able to build something like
that any time soon, but for what it's worth, these are some of my ideas on
the topic.
So, please, take a look at ditz: http://ditz.rubyforge.org/
It's ruby.
It has plugable system.
It offers UI.
And it's a distributed issue tracking
--
To post to this group, send email to gitorious@googlegroups.com
To unsubscribe from this group, send email to
gitorious+unsubscr...@googlegroups.com
