Re: Migration of services - 5. bugzilla

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

 



Dne út 13. října 2020 Michael via tde-users napsal(a):
> On Monday 12 October 2020 08:33:47 pm Felix Miata wrote:
> > Slávek Banko via tde-users composed on 2020-10-13 03:07 (UTC+0200):
> > > First of all, we need to discuss and decide whether we want to
> > > continue using Bugzilla.
> >
> > Mozilla's bug tracking software is the best bar none. The original.
> > Lots of thought over more than two decades has gone into building into
> > what it is.
> >
> > I have nothing but trouble no matter what I'm trying to do with all
> > the other trackers.
> >
> > Google can't even tell me what a TGW tracker is, thinks it's all about
> > golf.
>
> Felix brings up a point I wouldn’t have considered, how usable the
> software is by the primary users of the software.
>
> The bug reporting software won’t be used very often by most people who
> are only on this, the users list.  So asking us seems, to me, to be the
> wrong people to ask.
>
> My opinion?  You developers decide.  What’s best for you?
>

As Michele mentioned, we have been using TDE Gitea Workspace (TGW) since 
May 2018 and it has proven to be very successful.

Because Issues is an integral part of Gitea, it is a very well integrated 
part of the development process and therefore as developers we prefer 
Issues in TGW. After all, pull-requests are also processed as Issues.

Therefore, it is certain that Issues in TGW will be used, and the question 
is, is there any really good reason to use Bugzilla as a second system for 
the same purpose? I'm aware that Bugzilla has more years of experience 
with bug tracking systems, while Issues in TGW may be less mature, but, 
sorry Felix, that's not enough reason.


> We the users will basically have to learn the software the first time we
> want to create a bug report.  So, what software that is, seems pretty
> much irrelevant to us???
>
> I guess all I’d ask for is a clearly labeled, “Noobs start here” link so
> if/when I do need to file a bug report, I have a well defined checklist
> of what exactly to do to file it so it’s useful.  And really well
> defined! Start with the basics like, “install package debug-xyz,” “run
> the program by ???,” “copy/paste the output of xyz,” “stuff!”
>

Michele posted a link to a wiki page with instructions. However, here it 
may be a good idea to split this one page into multiple pages according to 
purpose - common information, for users and for developers. From the 
previous discussion about the web server, here is a plan to improve the 
Get Involved page so that it contains essential information and links - 
instructions for reporting issues are one of these things.

As Michele mentioned, here we will also have to change the integration into 
TDE applications - the Report a bug/enhancement menu item. So more work 
will be needed here.


> Best,
> Michael
> ____________________________________________________

Thank you for your opinion!
That was helpful.

Cheers
-- 
Slávek

Attachment: signature.asc
Description: This is a digitally signed message part.

____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx

[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux