Shawn O. Pearce wrote:
BTW, as another developers are getting involved in jgit/egit coding,
maybe we could use (update) some wiki page for marking who is working on
some topic currently? Now it's not obvious for me, and as we're not so
numerous it would be pity to waste our time and do some redundant stuff
one day.
I've thought about starting a code.google.com project just to use
the issue tracking system there. I'm using an internal tool to
keep of issues for myself, but that's not fair to the end-users or
other contributors...
That seems to be nice idea.
The only downside I see is that using code.coogle.com with Mylyn may be
hard[1]. As if we start to use issues system, it may be nice opportunity
to start using Mylyn - if anybody want to?
[1] http://www.jroller.com/alexRuiz/entry/using_mylyn_with_google_code
--
Marek Zawirski [zawir]
marek.zawirski@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
