Closed Bug 481161 Opened 15 years ago Closed 15 years ago

enable launchpad plugin for bugzilla.mozilla.org

Categories

(bugzilla.mozilla.org :: General, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: asac, Unassigned)

Details

As previously discussed during UDS, one thing to help bringing the ubuntu community and the mozilla project closer together would be to enable the launchpad plugin - which should be available in bugzilla upstream already.

I am not sure if and what is blocking this rollout, so lets discuss this here.
As I've said before, I'd like to wait until Launchpad is open source before doing this.
OS: Linux → All
Hardware: x86 → All
(In reply to comment #1)
> As I've said before, I'd like to wait until Launchpad is open source before
> doing this.

Another half a year more before this occurs, ref https://dev.launchpad.net/OpenSourcing
Launchpad will be open sourced in july, which was communicated quite prominently by Kiko during UDS in MTV. 

Problem is that the problems this bug would address exist _now_ and they are more pressing than ever. Also, its not only my request, but I got asked from mozilla side to help getting the ubuntu user base closer to the mozilla project. This plugin would mean a big step in that direction.

Please reconsider to make this happen earlier! Thanks!
launchpad's licensing here is EDONTCARE for me.  reed has some other concerns (related to audit and perf test of the code, plus making sure we migrate to upcoming core features that enable this stuff better) that I think we should make sure to address, but as long as the plugin for bugzilla is open source and meets our usual other standards, this is fine with me.
* What does the plugin do?  What implications are there for b.m.o.?
* What do we need to do for the security/performance audits?
* Is the plugin itself already open source?  I agree with shaver, $some_other_system's licensing doesn't matter, just what we hook into our system.
* What problems is this expected to solve?
(In reply to comment #5)
> * What does the plugin do?

  The plugin allows Launchpad to say that a particular bmo bug and a particular Launchpad bug are linked. It can add comments from the linked bug to this Bugzilla and add comments from the bug to the Launchpad bug.

> * What do we need to do for the security/performance audits?

  For security, I suspect nothing. For performance, you can install it on a staging server and test.

> * Is the plugin itself already open source?

  Yes, it's licensed under the MPL.
Curious, what would be the next steps to make this happen? Do you need more information?
Some more questions:

* Is the comment sharing required and automatically bidirectional?  It seems like the biggest benefit (users of either system can comment) is potentially the biggest drawback, since I don't know how to stop an abusive user from spamming a bug if they don't have a bugzilla account.  (I seem to have to do this myself a couple of times a month.)  It's also a little hard to require people using a different tracker to respect our rules.
* What other data is shared?
* How does the plugin handle group-restricted bugs?
** Related: how does the plugin handle insidergroup (private attachments/comments)?

What are the expected outcomes, beyond nebulous bringing-the-projects-closer goals?
Now that bmo is Bugzilla 3.4, the plugin is not needed. Launchpad is already pulling comments from bmo to launchpad, and the reverse will be set up in the next few days, as per my discussion with Graham earlier today.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
When you setup the reverse, will it address mconnor's concerns in comment 8?
(In reply to comment #8)
> * Is the comment sharing required and automatically bidirectional?

It's not required, but I think it would be useful to try, at least to see how it goes.

> It seems
> like the biggest benefit (users of either system can comment) is potentially
> the biggest drawback, since I don't know how to stop an abusive user from
> spamming a bug if they don't have a bugzilla account.  (I seem to have to do
> this myself a couple of times a month.) 

Disabling the Launchpad bugzilla user would stop that temporarily, but really, issues like that would have to be taken up with the Canonical Launchpad admins to have the user blocked on their side. I doubt this will happen often.

> It's also a little hard to require
> people using a different tracker to respect our rules.

Sure... not sure how best to deal with this one.

> * What other data is shared?

Not sure, but it's only data available via the API, so nothing that some other user couldn't already get.

> * How does the plugin handle group-restricted bugs?

Since this is now using the API, the Launchpad user is just a normal user without access to private bugs (unless the user gets CC'd or something weird).
So... We'll have to wait and see, but IMO there's a chance we'll end up disabling the launchpad user, since I have no intention of giving LP users a free pass on ignoring our rules of behaviour... but I'm willing to wait and see.
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.