Re: RHEL moving to issues.redhat.com only long term

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Mar 22, 2022 at 08:06:49PM -0700, Adam Williamson wrote:
> On Tue, 2022-03-22 at 11:55 -0400, Matthew Miller wrote:
> > On the first part: yes, there's a long, slow sunset, but I think
> > realistically we're going to see business-side attention drop significantly,
> > and we'll have correspondingly worse and worse service. Right now, there are
> > basically only two people keeping it all going, which is heroic. I don't
> > think it's too much pulling-back-the-corporate-curtain to guess that if one
> > or both get tired of that and decide to go start a yak farm, Red Hat won't
> > prioritize hiring backfill dedicated in the same way.
> 
> There is one thing I worry about here - and maybe we need to take this
> up internally within Red Hat, but whatever - I strongly believe that
> *at a minimum*, going to
> https://bugzilla.redhat.com/show_bug.cgi?id=NNN should show you the
> report, comments, and attachments for bug NNN. *Forever*. RH Bugzilla
> is effectively a huge, 20-year long knowledge base at this point.
> Probably hundreds of thousands of places on the internet link to RH
> bugs. Taking that offline would be effectively an act of vandalism.

It would be an act of massive self-harm to Red Hat too, not merely
community projects using it.

As a RHEL package maintainer, I frequently consult old bugs, from
links we have embedded in patches / changelogs / mailing lists /
commits. It is not unknown for me to look at bugs *10-15* years old
to understand the history of why something was done the way it is.

IOW, even if RHEL changes to use Jira for all future bug tracking
tomorrow, the need to reference bugzilla tickets could remain for
literally decades to come. Jira has been mirroring some bugzilla
content for a while, but that's by no means a complete archive
of relevant history, and still leaves the problem if figuring out
the matching link.

> It may not need to keep actually working as a dynamic web app if we do
> retire BZ - we could reduce it to a server that just serves up static
> snapshots of the content - but I'd really hate to see the content lost.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux