Re: Moving ring-kde to unmaintained (was: Re: Shift for parts of the CI system to Qt 5.15)
On Sat, Jun 20, 2020 at 10:40 PM Friedrich W. H. Kossebau wrote: > > Am Samstag, 20. Juni 2020, 12:25:42 CEST schrieb Ben Cooksley: > > On Sat, Jun 20, 2020 at 8:13 PM Volker Krause wrote: > > > On Saturday, 20 June 2020 08:20:18 CEST Ben Cooksley wrote: > > > > - ring-kde > > > > > > build errors seem to be in stuff downloaded by cmake!? > > > > Indeed, this seems to be a bit concerning. > > > > I'm wondering if we should discontinue the CI support for this project? > > Seems ring-kde is unmaintained, it has not seen any development since March > 2019, also missed to follow the renaming of GNU Ring to Jami on 18 December > 2018 (by what wikipedia tells). > > So +1 for tagging the repo as unmaintained, and thus also removing from CI. If nobody has any objections to the above, i'd like to action this in 24 hours time. > > Cheers > Friedrich > > Cheers, Ben
Gitlab Turn-off Issues
Can we remove the Issues feature on all invent projects? We're starting to see more and more people adding Issues. For KOrganizer, bshah replaced Issues with Bugzilla. I very much doubt we want or are ready to replace Bugzilla.
Re: Gitlab Turn-off Issues
On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: > > Can we remove the Issues feature on all invent projects? > We're starting to see more and more people adding Issues. > > For KOrganizer, bshah replaced Issues with Bugzilla. > > I very much doubt we want or are ready to replace Bugzilla. As has been discussed *far too many times* already, we have NO INTENTION to replace Bugzilla at this stage. This matter has been discussed on many threads, including on this list in the past. Issues on Gitlab is intended to be the replacement for Phabricator Tasks. Disabling them would leave projects with no developer task management functionality, which would be highly undesirable as they are heavily used by a number of projects. Your request to disable them for all KDE projects is therefore declined. Regards, Ben Cooksley KDE Sysadmin
Re: Gitlab Turn-off Issues
On 6/28/20 12:28 PM, Ben Cooksley wrote: On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: Can we remove the Issues feature on all invent projects? We're starting to see more and more people adding Issues. For KOrganizer, bshah replaced Issues with Bugzilla. I very much doubt we want or are ready to replace Bugzilla. As has been discussed *far too many times* already, we have NO INTENTION to replace Bugzilla at this stage. This matter has been discussed on many threads, including on this list in the past. Issues on Gitlab is intended to be the replacement for Phabricator Tasks. Disabling them would leave projects with no developer task management functionality, which would be highly undesirable as they are heavily used by a number of projects. Your request to disable them for all KDE projects is therefore declined. The problem with this approach is that users familiar with GitHub or GitLab in other projects will not stop submitting bug reports using GitLab issues as long as it's turned on in its current form, because how we're proposing to use GitLab issues does not match the typical usage of the feature. I could see this situation being improved if we could rename "Issues" to "Developer Tasks" or something like that in the UI, and additionally deploy a template to every repo with a warning to submit bug reports using Bugzilla. However the issue (har har) of users submitting bug reports and feature requests using GitLab issues is not likely to disappear without some kind of change. Nate
Re: Gitlab Turn-off Issues
El dom., 28 de jun. de 2020 a la(s) 16:47, Nate Graham (n...@kde.org) escribió: > > On 6/28/20 12:28 PM, Ben Cooksley wrote: > > On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: > >> > >> Can we remove the Issues feature on all invent projects? > >> We're starting to see more and more people adding Issues. > >> > >> For KOrganizer, bshah replaced Issues with Bugzilla. > >> > >> I very much doubt we want or are ready to replace Bugzilla. > > > > As has been discussed *far too many times* already, we have NO > > INTENTION to replace Bugzilla at this stage. > > This matter has been discussed on many threads, including on this list > > in the past. > > > > Issues on Gitlab is intended to be the replacement for Phabricator Tasks. > > Disabling them would leave projects with no developer task management > > functionality, which would be highly undesirable as they are heavily > > used by a number of projects. > > > > Your request to disable them for all KDE projects is therefore declined. > > The problem with this approach is that users familiar with GitHub or > GitLab in other projects will not stop submitting bug reports using > GitLab issues as long as it's turned on in its current form Hmm... Users familiar with GitHub in other projects will not stop submitting pull requests on the KDE GitHub mirror as long as that's turned on, and GitHub doesn't even let us turn off pull requests. Should we get rid of the GitHub mirror? Or should we keep closing pull requests and telling people to send their patches to Invent instead? (This is only half-rhetoric, I actually wouldn't mind getting rid of the GitHub mirror :P) > However the issue (har har) of users submitting bug reports and feature > requests using GitLab issues is not likely to disappear without some > kind of change. We can't easily change the label of the sidebar button. But what about a banner like this: https://invent.kde.org/games/kbounce/-/issues/new Do you think this would help? -- Nicolás
Re: Gitlab Turn-off Issues
El dom., 28 de jun. de 2020 a la(s) 17:29, Nicolás Alvarez (nicolas.alva...@gmail.com) escribió: > El dom., 28 de jun. de 2020 a la(s) 16:47, Nate Graham (n...@kde.org) > escribió: > > However the issue (har har) of users submitting bug reports and feature > > requests using GitLab issues is not likely to disappear without some > > kind of change. > > We can't easily change the label of the sidebar button. But what about > a banner like this: > https://invent.kde.org/games/kbounce/-/issues/new > > Do you think this would help? Okay, this was a banner showing: "Issues on KDE Invent are for developers to keep track of ongoing work. If you want to report a bug or request a feature, please go to the KDE bug tracker [link]". I restricted it to only appear on kbounce's "new issue" page to test it. However I just found that the banner text appears on the output of "git push" to any repository (after the "This commit is available at:" message), even if I restrict it to a single page on the web, so I just turned the banner back off >_< -- Nicolás
Re: Gitlab Turn-off Issues
El diumenge, 28 de juny de 2020, a les 22:29:06 CEST, Nicolás Alvarez va escriure: > El dom., 28 de jun. de 2020 a la(s) 16:47, Nate Graham (n...@kde.org) > escribió: > > > > On 6/28/20 12:28 PM, Ben Cooksley wrote: > > > On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: > > >> > > >> Can we remove the Issues feature on all invent projects? > > >> We're starting to see more and more people adding Issues. > > >> > > >> For KOrganizer, bshah replaced Issues with Bugzilla. > > >> > > >> I very much doubt we want or are ready to replace Bugzilla. > > > > > > As has been discussed *far too many times* already, we have NO > > > INTENTION to replace Bugzilla at this stage. > > > This matter has been discussed on many threads, including on this list > > > in the past. > > > > > > Issues on Gitlab is intended to be the replacement for Phabricator Tasks. > > > Disabling them would leave projects with no developer task management > > > functionality, which would be highly undesirable as they are heavily > > > used by a number of projects. > > > > > > Your request to disable them for all KDE projects is therefore declined. > > > > The problem with this approach is that users familiar with GitHub or > > GitLab in other projects will not stop submitting bug reports using > > GitLab issues as long as it's turned on in its current form > > Hmm... Users familiar with GitHub in other projects will not stop > submitting pull requests on the KDE GitHub mirror as long as that's > turned on, and GitHub doesn't even let us turn off pull requests. > Should we get rid of the GitHub mirror? Or should we keep closing pull > requests and telling people to send their patches to Invent instead? > (This is only half-rhetoric, I actually wouldn't mind getting rid of > the GitHub mirror :P) > > > However the issue (har har) of users submitting bug reports and feature > > requests using GitLab issues is not likely to disappear without some > > kind of change. > > We can't easily change the label of the sidebar button. But what about > a banner like this: > https://invent.kde.org/games/kbounce/-/issues/new > > Do you think this would help? When creating an issue in gitlab.com you get a long wall of text saying what you have to do https://i.imgur.com/ly2mU3M.png Could we have something like that by default saying "this is for developer tasks for bugs/issues use bugs.kde.org" ? Cheers, Albert > > -- > Nicolás >
Re: Gitlab Turn-off Issues
On 6/28/20 2:29 PM, Nicolás Alvarez wrote: > El dom., 28 de jun. de 2020 a la(s) 16:47, Nate Graham (n...@kde.org) > escribió: >> >> On 6/28/20 12:28 PM, Ben Cooksley wrote: >>> On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: Can we remove the Issues feature on all invent projects? We're starting to see more and more people adding Issues. For KOrganizer, bshah replaced Issues with Bugzilla. I very much doubt we want or are ready to replace Bugzilla. >>> >>> As has been discussed *far too many times* already, we have NO >>> INTENTION to replace Bugzilla at this stage. >>> This matter has been discussed on many threads, including on this list >>> in the past. >>> >>> Issues on Gitlab is intended to be the replacement for Phabricator Tasks. >>> Disabling them would leave projects with no developer task management >>> functionality, which would be highly undesirable as they are heavily >>> used by a number of projects. >>> >>> Your request to disable them for all KDE projects is therefore declined. >> >> The problem with this approach is that users familiar with GitHub or >> GitLab in other projects will not stop submitting bug reports using >> GitLab issues as long as it's turned on in its current form > > Hmm... Users familiar with GitHub in other projects will not stop > submitting pull requests on the KDE GitHub mirror as long as that's > turned on, and GitHub doesn't even let us turn off pull requests. > Should we get rid of the GitHub mirror? Or should we keep closing pull > requests and telling people to send their patches to Invent instead? > (This is only half-rhetoric, I actually wouldn't mind getting rid of > the GitHub mirror :P) Personally I wouldn't object, if we really can't turn off the pull request feature. I don't see what the GitHub mirror is accomplishing, other than confusing potential new contributors and wasting the time of actual contributors who have to perform maintenance and close pull requests. >> However the issue (har har) of users submitting bug reports and feature >> requests using GitLab issues is not likely to disappear without some >> kind of change. > > We can't easily change the label of the sidebar button. But what about > a banner like this: > https://invent.kde.org/games/kbounce/-/issues/new > > Do you think this would help? Yes, I think it definitely would! Could we also customize the banner per-project so that it pointed to the correct Bugzilla URL for that project? That would be rad. Nate
Re: Gitlab Turn-off Issues
El dom., 28 de jun. de 2020 a la(s) 19:02, Albert Astals Cid (aa...@kde.org) escribió: > > El diumenge, 28 de juny de 2020, a les 22:29:06 CEST, Nicolás Alvarez va > escriure: > > El dom., 28 de jun. de 2020 a la(s) 16:47, Nate Graham (n...@kde.org) > > escribió: > > > > > > On 6/28/20 12:28 PM, Ben Cooksley wrote: > > > > On Mon, Jun 29, 2020 at 4:28 AM Allen Winter wrote: > > > >> > > > >> Can we remove the Issues feature on all invent projects? > > > >> We're starting to see more and more people adding Issues. > > > >> > > > >> For KOrganizer, bshah replaced Issues with Bugzilla. > > > >> > > > >> I very much doubt we want or are ready to replace Bugzilla. > > > > > > > > As has been discussed *far too many times* already, we have NO > > > > INTENTION to replace Bugzilla at this stage. > > > > This matter has been discussed on many threads, including on this list > > > > in the past. > > > > > > > > Issues on Gitlab is intended to be the replacement for Phabricator > > > > Tasks. > > > > Disabling them would leave projects with no developer task management > > > > functionality, which would be highly undesirable as they are heavily > > > > used by a number of projects. > > > > > > > > Your request to disable them for all KDE projects is therefore declined. > > > > > > The problem with this approach is that users familiar with GitHub or > > > GitLab in other projects will not stop submitting bug reports using > > > GitLab issues as long as it's turned on in its current form > > > > Hmm... Users familiar with GitHub in other projects will not stop > > submitting pull requests on the KDE GitHub mirror as long as that's > > turned on, and GitHub doesn't even let us turn off pull requests. > > Should we get rid of the GitHub mirror? Or should we keep closing pull > > requests and telling people to send their patches to Invent instead? > > (This is only half-rhetoric, I actually wouldn't mind getting rid of > > the GitHub mirror :P) > > > > > However the issue (har har) of users submitting bug reports and feature > > > requests using GitLab issues is not likely to disappear without some > > > kind of change. > > > > We can't easily change the label of the sidebar button. But what about > > a banner like this: > > https://invent.kde.org/games/kbounce/-/issues/new > > > > Do you think this would help? > > When creating an issue in gitlab.com you get a long wall of text saying what > you have to do https://i.imgur.com/ly2mU3M.png > > Could we have something like that by default saying "this is for developer > tasks for bugs/issues use bugs.kde.org" ? Apparently that's not available in GitLab's free edition: https://docs.gitlab.com/ee/user/project/description_templates.html#setting-a-default-template-for-merge-requests-and-issues--starter -- Nicolás
