#613 Point Bugzilla users to the FCOS upstream tracker
Closed: Fixed 4 years ago by kparal. Opened 4 years ago by kparal.

Inform people looking in Bugzilla for Fedora/CoreOS component that they should file issues at fedora-coreos-tracker github project instead. At least for actual FCOS issues, which should be the majority of them. The use case for filing directly into Bugzilla could be to propose a blocker bug/freeze exception. (Note that FCOS release cycle will be delayed by ~a month behind the standard Fedora release cycle. But we might still want to use the same/similar process, just specific for FCOS. This needs to get clarified.)

The implementation can be a new coreos component under the Fedora project that uses a custom description template to inform the user. Of course we need to figure out if such custom templates are supported. Or perhaps there is some other way to redirect users from Bugzilla to an external place. The purpose of this ticket is to find out possible solutions, discuss them, pick the best one and implement it.

@coremodule @sumantrom Can one of you please grab this?


Metadata Update from @sumantrom:
- Issue assigned to sumantrom

4 years ago

@kparal this should'nt be hard, do we know someone who has access to the "Fedora" product section ?

I am hunting for folks, if you happen to know anyone just let me know. :)

Referred to me by @sumantrom. I added the request to my Taiga board of doom.

@kparal this should'nt be hard, do we know someone who has access to the "Fedora" product section ?

Unfortunately I don't, but I guess @bcotton or @adamwill might help you find someone.

I talked to @bcotton about this some. I think maybe it's best to defer any big changes here until after the outcome of CPE's gitforge plans, because depending on the outcome we might want to do different things with issue tracking.

@mattdm so what I hear you say is we use CoreOS's tracking for now and report bugs mostly there?

I talked to @bcotton about this some. I think maybe it's best to defer any big changes here until after the outcome of CPE's gitforge plans, because depending on the outcome we might want to do different things with issue tracking.

Sure, but this is not even a medium change, it won't be a 100-man-hours project. We simply want to help users who currently can't find FCOS in Bugzilla, and adding a template forwarding them elsewhere sounds as a simple task. I expect the git forge decision will take some time and the implementation even longer, I don't expect seeing anything tangible from it sooner than in 6 months. In the mean time, we can either do a poor job or a better job forwarding people to the right place to report issues. If I'm misunderstanding something, please tell me :-)

Part of the issue is that there's a bit of a policy question at this point. Pointing people toward the GitHub tracker doesn't work well if they bug they're filing is actually against the kernel or systemd or glibc or... If bugs are in Bugzilla, you can easily reassign them as appropriate. If they're in GitHub, you're bouncing users back to another system (that, as requested, they'd originally have been redirected from).

So there may be two separate issues here:
1. A request to create a Fedora CoreOS component in Bugzilla.
2. A request to tell people when they file a FCOS BZ that they should go to GitHub instead.

The first is no problem, I did it for IoT already. This gives users a convenient, unambiguous location to report bugs that people who know details can assign correctly.

The second is a larger question that involves potential distro-wide policy decisions ("do whatever" being a possible outcome, but one that should be arrived at intentionally) and is influenced by things like "how many bugs are against components in FCOS versus the packaging and distribution of FCOS itself?" and "is FCOS a distinct project in itself or is it a particular way we distribute the Fedora operating system?"

So the implementation is trivial, but the policy behind it is the hard part.

@dustymabe Please see the discussion above. Can you please figure out together with @bcotton and @mattdm what policy should Fedora+FCOS follow here? (It doesn't necessarily need to be in this ticket). We'll make this ticket stalled until a decision is reached.

(Note that we/I already forward people to upstream trackers like the GNOME Gitlab when e.g. a GNOME bug is discovered, unless it looks specific to Fedora or it needs proposed as a blocker. This makes it much more likely that GNOME developers will notice the report and fix the bug. With FCOS, their upstream and downstream is the same thing, so there's a slight difference.)

I'll set up a meeting with Dusty and Matthew so that we can have a high-bandwidth discussion about this and one of us will report back. Thanks for your patience.

4 years ago

@dustymabe , @mattdm, and I spoke yesterday. We agreed that the original proposal will work and we can revisit if it becomes a problem. For the user's sake, we'd like to see the team handle creating BZs on behalf of the user where appropriate.

I've developed the following draft for the custom template. I'll wait a week and then work with the Bugzilla admins to implement this:

Fedora CoreOS bugs and feature requests should be filed in the coreos-tracker GitHub project:
https://github.com/coreos/fedora-coreos-tracker/issues

If you know the issue is with a particular component (e.g. glibc), you can file a bug against that component in Bugzilla instead.

For general help or support you can post to:
- Forum: https://discussion.fedoraproject.org/c/server/coreos
- Mailing list: coreos@lists.fedoraproject.org

If you do not have a GitHub account or believe this is the best venue for your bug report, please >ignore the above and continue submitting your report here.

@dustymabe , @mattdm, and I spoke yesterday. We agreed that the original proposal will work and we can revisit if it becomes a problem. For the user's sake, we'd like to see the team handle creating BZs on behalf of the user where appropriate.

LGTM. One comment:

I've developed the following draft for the custom template. I'll wait a week and then work with the Bugzilla admins to implement this:

Fedora CoreOS bugs and feature requests should be filed in the coreos-tracker GitHub project:
https://github.com/coreos/fedora-coreos-tracker/issues
If you know the issue is with a particular component (e.g. glibc), you can file a bug against that component instead.

You may want to specifically state "in bugzilla" here so they know to file the bug against that component in bugzilla and not somehow think we mean GitHub.

For general help or support you can post to:
- Forum: https://discussion.fedoraproject.org/c/server/coreos
- Mailing list: coreos@lists.fedoraproject.org
If you do not have a GitHub account or believe this is the best venue for your bug report, please >ignore the above and continue submitting your report here.

You may want to specifically state "in bugzilla" here so they know to file the bug against that component in bugzilla and not somehow think we mean GitHub.

Good point. I updated the text to reflect that.

If you know the issue is with a particular component (e.g. glibc), you can file a bug against that component in Bugzilla instead.

@dustymabe In these cases, you'll not be aware of such bugs. We can create a CoreOS tracker bug and then ask users to also add Blocks: CoreOS into such filed bugs. Then your team can watch the tracker and be notified of new FCOS-related bugs. For example, see the IoT tracker. Does this sound like a good idea to you and should we make it happen, or do you prefer to keep it as it is for now (no tracker bug)?

If you know the issue is with a particular component (e.g. glibc), you can file a bug against that component in Bugzilla instead.

@dustymabe In these cases, you'll not be aware of such bugs. We can create a CoreOS tracker bug and then ask users to also add Blocks: CoreOS into such filed bugs. Then your team can watch the tracker and be notified of new FCOS-related bugs. For example, see the IoT tracker. Does this sound like a good idea to you and should we make it happen, or do you prefer to keep it as it is for now (no tracker bug)?

I'm not sure. From your description it sounds like if someone opens a bug that they observe in FCOS but is actually a bug in a different component (say systemd) then they'll add Blocks: CoreOS to the systemd bug? That could be useful, but I think I'd rather just manage the relationship myself rather than having users do that.

I'd say for now let's leave things like they are and we can revisit what is working and what isn't working in 3 or 4 months.

4 years ago

@dustymabe , @mattdm, and I spoke yesterday. We agreed that the original proposal will work and we can revisit if it becomes a problem. For the user's sake, we'd like to see the team handle creating BZs on behalf of the user where appropriate.
I've developed the following draft for the custom template. I'll wait a week and then work with the Bugzilla admins to implement this:

Fedora CoreOS bugs and feature requests should be filed in the coreos-tracker GitHub project:
https://github.com/coreos/fedora-coreos-tracker/issues
If you know the issue is with a particular component (e.g. glibc), you can file a bug against that component in Bugzilla instead.
For general help or support you can post to:
- Forum: https://discussion.fedoraproject.org/c/server/coreos
- Mailing list: coreos@lists.fedoraproject.org
If you do not have a GitHub account or believe this is the best venue for your bug report, please >ignore the above and continue submitting your report here.

@bcotton is this stuff implemented ? I was waiting on this for this and test cases (Which I am working on) to call for a test day.

@bcotton is this stuff implemented ? I was waiting on this for this and test cases (Which I am working on) to call for a test day.

@sumantrom not yet. I was traveling last week and couldn't get to it. I'll start the process tomorrow.

@sumantrom The component is created and I have opened PNT0793910 with the Bugzilla admins to create the template.

@dustymabe I set you as the default assignee of bugs in the component for now. Is there a better Bugzilla account to use?

The Bugzilla component now uses a template that points folks to the GitHub tracker. Dusty is the default assignee of bugs for now, I'll work on getting that updated to a mailing list in the background, but I believe for the purposes of this ticket, the work is done.

@bcotton++ :cookie:

The template looks good! Thanks everyone, I'm closing this ticket as done.

Metadata Update from @kparal:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata