On Monday 12 October 2020 08:33:47 pm Felix Miata wrote: 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? 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!” Best, Michael

Dne út 13. října 2020 Michael via tde-users napsal(a): 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. 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. Thank you for your opinion! That was helpful. Cheers -- Slávek

Slávek Banko via tde-users composed on 2020-11-07 01:21 (UTC+0100): One more, FWIW. Since searching for existing bugs on trackers other than Bugzilla and actually finding what I'm looking for is so rare, most likely I won't be bothering to search when I find a problem, but simply file a report and let others figure out if it's a duplicate or not. Historically I've tried to keep triagers from having to do this, since triage is what I used to do a lot of. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

Michele Calgaro via tde-users composed on 2020-11-07 14:07 (UTC+0800): Time will tell. Simplicity is the usual problem with non-Bugzilla trackers - limited or non-existent ability to narrow a search to a period or user or group or package but more particularly a combination two or more of the above and other criteria. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

On Saturday 07 of November 2020 08:19:47 Felix Miata wrote: Yes, of course, Bugzilla has more extensive search options, because there are many more items in the search form ... on the other hand, there are items that are rarely used and items that users do not fill in correctly. The question is what items are really useful and whether TGW provides sufficient options. One example of an item that is significantly different between Bugzilla and TGW is the Component selection. In Bugzilla, this is just one of the form items, for which we have to maintain a list of offered items. The current list is incomplete - there are no individual applications, so the usefulness of this item is reduced for now. At the same time, adding items would probably result in a long, not very clear list. In TGW, the approach is quite the opposite. Each component is a GIT repository and each GIT repository actaully has its own list of Issues. Therefore, there is no need to maintain a list of components - this is done automatically. At the same time, it does not limit the search for issues across components. Yes, this method limits the ability to move issues between components. However, it is possible to solve it easily and as a result very clearly. If an issue is reported in one of the components - for example in main 'tde' component and the analysis specifies that the root of cause is in another component, new issues will be created in the relevant component, and this new issue will reference / follow up on the issue in the originally reported component. As a result, the information will continue to be traceable in the original component. I think other useful items are usually just the title and comments. And for these items, there is no fundamental difference in the search between Bugzilla and TGW. Therefore, the more comprehensive search options in Bugzilla do not seem to me to be a very strong argument. Therefore, the goal remains to replace Bugzilla with Isuses in TGW. Cheers -- Slávek