Re: Changes to Bugzilla API key requirements

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

 



On Fri, 2023-02-24 at 11:55 -0500, Solomon Peachy via devel wrote:
> On Fri, Feb 24, 2023 at 05:55:55AM +0100, Kevin Kofler via devel wrote:
> > Ah right, I had forgotten about that issue. I do not think I will ever 
> > understand the fascination some projects have for JIRA. It is proprietary, 
> > and IMHO the web UI for users to report bugs in JIRA is very confusing at 
> > times. (The Bugzilla one can be confusing at times as well, but at least it 
> > is familiarly confusing. ;-) )
> 
> Middle management *LOVES LOVES LOVES* Jira.

Not middle management is generally as confused as other users.

Where Jira is really helpful is project management, and when you have
many, large, interconnected sub teams and sub projects, Jira really has
tooling that helps.

Of course like all tools it has its good things, and its bad
compromises, the UI being one of them. But the data model behind it
allows a lot of functionality (it is basically an SQL database), and
the dashboards and other prepackaged widgets allow exploration of the
data to a level that bugzilla does not allow (or if it does at
considerably harder cost, so high very few ever bother trying).

> As for everyone else... let's just say that it's not repeatable in polite company.
> 
> (I admit I'm surprised that "Free Software for Everything" Red Hat is 
>  chosing to base something so fundamental to their business on a highly 
>  proprietary tool.  I suppose O365 is just a matter of time...)

One of the bad things is that Jira is not Open Source, and I think
we'll ultimately may end up regretting the choice, but not in the short
term (there is no equivalent really in the open source world) ... and
pragmatically, in the long run we are all dead, so while we wait for
something better, we will have to use the least worst.

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc


_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue




[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