GNOME Bugzilla – Bug 699402
ModemManager is all grown up and needs to move away from home
Last modified: 2015-03-03 14:11:47 UTC
In the last year, the number of MM-specific bugs in bugzilla, and MM-specific messages on networkmanager-list has gone up dramatically. I think we're at the point where it should get its own bugzilla product and mailing list. Since it's not particularly GNOMEy, and not hosted on git.gnome.org, it probably makes more sense for those to be freedesktop-based? It is possible to dump bugs from one bugzilla and then load them into another, though this would require admin assistance on both sides. The other possibility would be to screenscrape the existing bugs and create new bugs manually, which I bet someone has a script for somewhere...
(In reply to comment #0) > In the last year, the number of MM-specific bugs in bugzilla, and MM-specific > messages on networkmanager-list has gone up dramatically. I think we're at the > point where it should get its own bugzilla product and mailing list. > > Since it's not particularly GNOMEy, and not hosted on git.gnome.org, it > probably makes more sense for those to be freedesktop-based? > > It is possible to dump bugs from one bugzilla and then load them into another, > though this would require admin assistance on both sides. The other possibility > would be to screenscrape the existing bugs and create new bugs manually, which > I bet someone has a script for somewhere... I don't really have any major objection to this.
> Since it's not particularly GNOMEy, and not hosted on git.gnome.org, it > probably makes more sense for those to be freedesktop-based? > > It is possible to dump bugs from one bugzilla and then load them into another, > though this would require admin assistance on both sides. The other possibility > would be to screenscrape the existing bugs and create new bugs manually, which > I bet someone has a script for somewhere... The only problem I see, now that I think twice about this, is that there will for sure be MM issues reported to NM; and it's easier to just change the bugzilla product/component than re-reporting it in some other bugzilla... Also, fd.o is probably the best place for both NM and MM, but I doubt moving the whole NM product to fd.o bugzilla is something we want to do... Regarding the mailing list; we will also get issues reported in the NM mailing list, basically because not everyone knows that MM is below NM. Not sure if redirecting all those to a new mailing list would be ideal... But anyway, most of the MM related traffic these days is patches, and those sending patches would be aware of the new mailing list... If we do this change, though, we should probably do it along with the 0.8.x release all together.
See https://bugs.freedesktop.org/show_bug.cgi?id=64325
All ModemManager open bugs have now been moved to freedesktop.org, so please consider removing the "ModemManager" component from NetworkManager's bugzilla alltogether (unless keeping that makes sense e.g. to keep track of already closed bugs that were for MM). For reference, all new ModemManager bugs need to be reported at: https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager List of open ModemManager bugs can be checked at: https://bugs.freedesktop.org/buglist.cgi?product=ModemManager&resolution=--- Closing this bug as resolved/fixed.
You can't delete a component without moving all of its bugs to another component first, but you can disable it for new bugs, which I've done now.
(In reply to Dan Winship from comment #5) > You can't delete a component without moving all of its bugs to another > component first, but you can disable it for new bugs, which I've done now. That is more than enough, thanks!