[linux-distros-dev] How to tackle bugs in another bug tracking system?

["Remy Chi Jian Suen" <remy.suen@xxxxxxxxx>]

Hi everyone,

There are some issues filed for the ChangeLog plug-in in Red Hat's
bugzilla that I would like to tackle but am unsure on what's the
agreed-upon protocol here (if any).

If something migrates from one place to another, do we want to create
fresh bugs in Eclipse's bugzilla that mirrors those bugs or do we want
to comment/clean them up in the original bug tracking system? There
are of course pros and cons with both solutions.

The former would ensure that all communications are done within
Eclipse.org and that our users don't need to jump around elsewhere. It
is, of course, rather frustrating, to have a bug marked as a duplicate
and then have to sign-up for another account elsewhere to take part in
that discussion. On the other hand, it is similarly odd to have the
discussion suddenly move elsewhere. That is like making a posting on a
mailing list and then everyone suddenly continues it on another list.
The people from the first system would have to get Eclipse.org
bugzilla accounts.

Similar arguments (but the other way around) could be had for the latter case.

So what are we doing (if something was decided between the different
distro representatives when the project was proposed)? Or if not, what
do we want to do?

I vote for the former since I think we should just "get things over
with" while our project is still young. If our users starts getting
redirected to Eclipse.org now, we will have less communication
problems in the future, and that is a huge roadblock, or possibly a
bane, to any open source project.

Regards,
Rem