Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Hi, sajolida: > - Redmine issues are sometimes referenced with '#' and sometimes > without. ACK, filed https://salsa.debian.org/tails-team/gitlab-migration/issues/18 > - The color scheme of some tags is not accessible. For example white on > neon green (definitely) and white on orange (probably). ACK, filed https://salsa.debian.org/tails-team/gitlab-migration/issues/19 > But I guess that's easy to change afterwards :) Technically it's easy but in my experience, one gets used to these colors and it's hard to change habits, so better pick colors that work ASAP. I'm not sure the current GitLab team is the best placed to do that by ourselves so we may need help. > - I don't understand the labels that are only numbers (eg. 165) and they > lead to empty lists. This is a known issue. > - Some embedded images are broken. ACK, filed https://salsa.debian.org/tails-team/gitlab-migration/issues/20 Cheers, -- intrigeri ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Hi, segfault: > intrigeri: >> segfault: >>> I would very much prefer to keep the original authors. >> >> Heard and noted. Would you like to elaborate a tiny bit wrt. to why >> you think it'll make a difference for you? It will help me triage & >> classify your feedback. > Sure. For a start, it wouldn't be possible to filter issues by @author, > instead you would have to search for "Original created by @intrigeri" - > which might be acceptable. Indeed. IMO it would be acceptable for ticket creation, but: > I think more UX impact has the authorship of the comments. For example > when I'm reading up on a ticket with long comments, for each comment I > read, I first have to scroll down to the bottom to see who the author is > - which of course is important information when you're trying to follow > a discussion. And since we're reading from top to bottom, it's generally > harder to see that information, which makes it harder to quickly skim > through comments. Got it! So I did two things: - I've requested that this info is moved to the top of the notes: https://salsa.debian.org/tails-team/gitlab-migration/issues/17 This will mitigate the problem you're describing if we import data without admin rights on GitLab. - I've updated the hosting comparison to make it clearer that avoiding this problem entirely would be a point in favour of choosing a GitLab instance on which we have admin credentials. Cheers, -- intrigeri ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Hi, intrigeri: >>> Known problems that we *might* be able to solve later >>> = >>> >>> - All issues appear to have been created by the user account that did >>> the migration. We could fix that if we're migrating to a GitLab >>> instance on which we have admin credentials so we can impersonate >>> other users. Else, this problem will remain and the best we will >>> have is the free-form annotation in the issue description, e.g. >>> "Original created by @intrigeri on 17117 (Redmine)". > >> I would very much prefer to keep the original authors. > > Heard and noted. Would you like to elaborate a tiny bit wrt. to why > you think it'll make a difference for you? It will help me triage & > classify your feedback. Sure. For a start, it wouldn't be possible to filter issues by @author, instead you would have to search for "Original created by @intrigeri" - which might be acceptable. I think more UX impact has the authorship of the comments. For example when I'm reading up on a ticket with long comments, for each comment I read, I first have to scroll down to the bottom to see who the author is - which of course is important information when you're trying to follow a discussion. And since we're reading from top to bottom, it's generally harder to see that information, which makes it harder to quickly skim through comments. Cheers ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Wow, it super cool to see that you already have an automated import process :) Things I could spot within 20 minutes of browsing through it: - Redmine issues are sometimes referenced with '#' and sometimes without. For example: https://0xacab.org/intrigeri/redmine-import-1/issues/17227 Without: Original created by @sajolida on 17227 (Redmine) With: Blocks #16711 I wonder whether it might make it harder to use the internal search. - The color scheme of some tags is not accessible. For example white on neon green (definitely) and white on orange (probably). But I guess that's easy to change afterwards :) - I don't understand the labels that are only numbers (eg. 165) and they lead to empty lists. For example: https://0xacab.org/intrigeri/redmine-import-1/issues?label_name%5B%5D=165 - Some embedded images are broken. For example: https://0xacab.org/intrigeri/redmine-import-1/issues/17068 -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Hi, segfault: >> Known problems that we plan to solve later >> == > With "later" do you mean after the migration? No, before the final migration. I was unclear indeed! > I think at least a few of those problems should be solved before > the migration. Absolutely. >> Known problems that we *might* be able to solve later >> = >> >> - All issues appear to have been created by the user account that did >> the migration. We could fix that if we're migrating to a GitLab >> instance on which we have admin credentials so we can impersonate >> other users. Else, this problem will remain and the best we will >> have is the free-form annotation in the issue description, e.g. >> "Original created by @intrigeri on 17117 (Redmine)". > I would very much prefer to keep the original authors. Heard and noted. Would you like to elaborate a tiny bit wrt. to why you think it'll make a difference for you? It will help me triage & classify your feedback. > Would this also be possible for comments (which currently also all > appear to be made by the same user)? I believe it's exactly the same problem for comments: if we can impersonate users for issue creation, then we can also impersonate them for notes creation. If we can't do the former, then we can't do the later. Note that in the worst case, if we can't impersonate folks, IMO we should do the migration using a special purpose migration bot user, and definitely *not* as mine :) Cheers, -- intrigeri ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
Re: [Tails-project] Call for feedback: proof-of-concept of our issues in GitLab
Hi, intrigeri: > please provide early feedback about the first proof-of-concept import > of our public Redmine data into GitLab: > >https://0xacab.org/intrigeri/redmine-import-1/issues Awesome, thanks! > Known problems that we plan to solve later > == With "later" do you mean after the migration? I think at least a few of those problems should be solved before the migration. > Known problems that we *might* be able to solve later > = > > - All issues appear to have been created by the user account that did > the migration. We could fix that if we're migrating to a GitLab > instance on which we have admin credentials so we can impersonate > other users. Else, this problem will remain and the best we will > have is the free-form annotation in the issue description, e.g. > "Original created by @intrigeri on 17117 (Redmine)". I would very much prefer to keep the original authors. Would this also be possible for comments (which currently also all appear to be made by the same user)? Cheers ___ Tails-project mailing list Tails-project@boum.org https://www.autistici.org/mailman/listinfo/tails-project
