Thank you for the feedback guys (great run-through, Carlos!). We'll need
to think about this. :)
cheers,
Thomas
On 07/26/2012 06:44 PM, Kevin Cox wrote:
Yes yes yes. You nailed all of my requirements. Also githubs tagging
is supprisingly nice. But I think that the ability to create your own
fields is a much more organized method.
On Jul 26, 2012 12:41 PM, "Carlos Mundi" <[email protected]
<mailto:[email protected]>> wrote:
Thanks, Thomas.
As a newcomer, I would find posting of a roadmap helpful.
When selecting a solution, I see issue tracking as a key
differentiator between Gitorious and GitHub.
Gitlab, which is far less mature, has already implemented
issue-tracking. I don't know enough yet to comment on specific
implementations, but I do think a few things would be killer:
1. Having issue tracking.
2. Having one-to-many and many-to-one mapping between issues and
commits and between issues and merge requests.
3. Optional automatic updating issues (usually from Open to Fixed)
after successful completion of a linked merge request. (note.
Need collision detection. Simple but important.)
4. Choices. Let project owner control #3 above. For example some
projects like to mark issues Closed on commit. Not us. We mark
Fixed and only move to Closed after tests pass, which is still
manual for us. So basically there should be automation hooks
(ReSTful API?) for state changes. Baking that in allows Gitorious
to grow with users.
5. Extensible state machine. The project owner would be able to
add states and tweak the allowed transitions, one transition table
for each role (owner, dev, reporter, guest, ...)
6. Flags, as in bugzilla, to consistently encode searchable vital
meta-data which is not a proper state. Simple example: we use a
custom flag "expedite" to flag and pull status reports on issues
which are critical to management. This helps us be agile.
7. Again, I would emphasize integration in the views and keep the
models and controllers separate from the views with a restful API
so that vcs and tracking cores can evolve independently.
Ok, that's my wishlist. I know it's long and AFAIK no FOSS
solution does all of that...yet. GitHub seems to be in a
consolidation phase, but that could change with the recent VC
infusion. Gitlab has a headstart, but maybe not by much.
Gitorious looks like it is positioned to sieze the day.
These ideas are nothing revolutionary and I want to hear what
others want.
Thanks for providing a forum.
On Jul 26, 2012 6:26 AM, "Thomas Kjeldahl Nilsson"
<[email protected] <mailto:[email protected]>> wrote:
Hi Carlos,
AFAIK adding an integrated issue tracker is not currently on
the roadmap for Gitorious, but we certainly welcome discussion
of this if the community feels strongly about it either way. :)
cheers,
Thomas
On 07/25/2012 11:57 PM, Carlos wrote:
Hi,
I'm brand new to gitorious (today!). I really like what I
see and am thinking of whether it could integrate with what
we're already doing. I'm reading this list and anything I
can find as fast as I can.
Discussion of integrated issue tracking comes up every so
often and I see things like issues.gitorious.org
<http://issues.gitorious.org/> and
https://www.chiliproject.org/ and bugzilla and ...
My question is, what is the current state of support for
issue trackign in gitorious and does it have a place on the
official roadmap?
FYI, I am interested in common-sense issue tracking and not
so much in fancy project management tools. Gitlab has a good
start on issue tracking which could evolve into something
with the fine-grained reporting capability of bugzilla. Is
there anything like this on the horizon for gitorious?
I'm not a Rubyist, so I can't contribute code in the short
term, but I'm feeling kind of inspired by what I see of
gitorious.
Thanks!
Carlos
--
To post to this group, send email to
[email protected] <mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:[email protected]>
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to
[email protected] <mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:gitorious%[email protected]>
--
To post to this group, send email to [email protected]
<mailto:[email protected]>
To unsubscribe from this group, send email to
[email protected]
<mailto:gitorious%[email protected]>
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
--
best regards,
Thomas Kjeldahl Nilsson
http://gitorious.com
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
