2020-01-03 08-42-38 PST Nathan Lee I definitely have! You can't go through many launchpad issues without seeing them. 2020-01-03 08-35-21 PST Nathan Lee [ ](https://chat.inkscape.org/direct/ede123?msg=vjsemcFPpC54SwAhL) Okay, that's good :sweat_smile: :thumbsup: It's a bit odd, since as you said, we don't have a large team atm. Really, everyone active in gitlab while I've been here, who is also in the bug wrangles list, is a developer or contributed bug-fixing commits afaik, maybe with the exception of Maren if you don't count her as a developer :stuck_out_tongue_winking_eye: and b3u () 2020-01-03 07-24-05 PST Nathan Lee [ ](https://chat.inkscape.org/direct/ede123?msg=DpwQinbRXFKRkg5dW) And all the other questions I thought of revolve around this question really () 2020-01-03 08-30-53 PST Nathan Lee Re: backtrace, I recall someone (I think Bryce?) asking for a full backtrace before moving the issue. That was a while ago, so intentions may have changed (or maybe its cause people were available to collect it). That's where my belief came from. 2019-07-19 17-39-42 PDT Nathan Lee Sorry, I made a mistake with CI and cancelled the wrong job. Restarted it and looking over it. 2020-01-03 08-28-21 PST Nathan Lee [ ](https://chat.inkscape.org/direct/ede123?msg=RN5oHRvqDkMvxJgek) I think that's the central issue with what I've been doing. I've generally held issues until there is some understanding of the issue, i.e. a specific bug, rather than just a confirmation that the steps create unexpected behavior and cleanup of the issue. I think I could quickly move a lot of issues if we just need to confirm that it happens and tidy up the issue (i.e. reliable steps to reproduce + all the info you stated above). Its never been a problem since I wasn't specifically tasked with triaging :sweat_smile: () 2020-01-03 06-43-50 PST Nathan Lee Thanks for granting me extra permissions. (and sorry for having a blank period of no response/no action on the bug documentation. I'll get back to it soon!). Should we ask bug migrators if they want to join bug wranglers? I'm thinking of asking Jonathan Hofinger (edit: jhofinger in Gitlab), at least so he can label/link issues inside inbox (I don't think I have permissions to just add him to Inbox, so I'm asking you ;) ) Also got some questions regarding bug triaging for #bug_migration; will post once I write them. 2019-12-10 00-39-30 PST Nathan Lee Alright, that sounds fair :+1: Thanks for the info. 2020-01-22 08-22-57 PST Nathan Lee Thanks Patrick. It seems like everyone has suggestions for new labels (including me)! I'll send a message to team_vectors tomorrow (don't want to ask questions that might require back and forth without vanishing). Just to clarify, we would really only need permissions to gitlab.com/inkscape/vectors/general (and only maybe, will ask!). 2020-01-25 21-41-12 PST Nathan Lee oh, almost forgot! The vectors issue was resolved. After asking in team_vectors, Martin and Maren gave us permissions for vectors (just most of the members of the team instead of the whole group). Since its rare that content/general issues end up in Inbox, I think this will do for now. Thanks again for helping me out :smiley: 2019-03-02 13-55-52 PST Nathan Lee Thank you Patrick, I'll do my best to help out :smiley: 2020-01-03 06-56-28 PST Nathan Lee Also a bit basic, should some of the "diagnosis" be happening in Inbox, or can issues be moved as soon as they are confirmed? E.g. problem always occurs in this file v problem is with this line in the file. A lot of the bottle-neck in sorting is probably here. In line with the policy "backtraces for crashes", I tend to be conservative and do as much "diagnosis" as plausible for a non-developer in Inbox. 2019-12-09 16-31-05 PST Nathan Lee Do you think Victor is ready to access inkscape/inkscape and inkscape/extensions for moving issues? I'm not sure what permissions this grants (also I can't do it myself :monkey: ) but I had assumed he already had those rights. 2020-01-03 08-54-34 PST Nathan Lee Thanks for the clarification, Patrick. This should really speed up managing the inbox. I've got to go (to sleep) now, hope you have a good weekend! 2020-01-18 08-39-41 PST Nathan Lee Hi, throwing out a couple questions

Could you add some permissions for moving issues to Vectors (Jonathan brought up moving https://gitlab.com/inkscape/inbox/issues/318)

and

Are you okay w/ me adding/editing labels to inkscape/inkscape after discussion in bug_migration? e.g. Adam's suggestion to add a label: Canvas UI, maybe filling the description to some of those labels. 2020-01-03 07-21-46 PST Nathan Lee The other question: can you add inkscape-docs to the shared projects for bug wranglers? 2020-01-03 07-21-02 PST Nathan Lee Hmm... Typing it out, I'm afraid its all questions for you. *No rush to answer*, and the only thing I'm posting in bug_migration is some label proposals. 2019-12-10 00-30-03 PST Patrick I've granted him rights for inbox only so we can give some direction (I think that was a good decision). 2020-01-03 08-36-26 PST Patrick Yes - it's hard to recruit people who are interested in "only" triaging bugs - but I don't mind if triagers become developers either ;-) 2020-01-03 10-11-10 PST Patrick Good night! Have a nice weekend as well. 2019-03-02 09-34-06 PST Patrick Hi Nathan, welcome to the bug team! 2019-03-02 09-38-59 PST Patrick One additional job you should be able to do now is moving confirmed bugs from https://gitlab.com/inkscape/inbox to a more suitable sub-project tracker (e.g https://gitlab.com/inkscape/inkscape). The idea is that only confirmed bugs with reliable steps to reproduce end up in the sub-project trackers. 2020-01-20 14-07-42 PST Patrick Hi Nathan, I could add permissions for gitlab.com/inkscape/vectors/general/ and/or gitlab.com/inkscape/vectors/content/ but not for the actual group gitlab.com/groups/inkscape/vectors . Also I have to admit that I'm not really familiar with how those repos are used and how issues should be filed for them. Maybe you could quickly confirm with #team_vectors which access level to which parts of the group would be most desirable? (if we add the bug wranglers teams as a members to the vectors group we need somebody with owner permissions on that group, anyway)

As for labels: Yes certainly. Maybe we could actually have a general "canvas" label instead of a "canvas UI" label? Problem with these "combined labels" is that you might end up with a bunch of "$some_component UI" labels that will then potentially be used in parallel to plain "$some_component" labels. Then you need "canvas performance", "canvas UX", etc and before you know it you have dozens of co-existing labels for similar things. So maybe instead of "canvas UI" we could just use "canvas" and "UI" to label UI issues of the canvas itself? This way is also easier to filter, as you can search for issues that have "canvas" and "UI" if you want to find all canvas UI issues, but you also will still find them in both the list of "UI" issues and the list of "canvas" issues. 2020-01-03 08-29-40 PST Patrick Basically you're a developer already ;-) 2019-12-11 14-12-40 PST Patrick Btw, feel free to decide how to proceed going forward (both with Victor and with bug wrangling in general). You did a great job wrangling bugs in the past and are probably the most active bug wrangler right now. I'd be comfortable with you taking the lead in this. I just gave you "Owner" permissions in gitlab.com/groups/inkscape/bug-wranglers so you can add new members. At the same time I don't want to burden you with anything, so do as much as you want, but don't burn yourself out with anything. I'm always happy to help as long as time permits and I also think that teams work best if they're just that - teams. So ideally we can share the workload and fall-back on each other if there are questions we feel uncomfortable deciding on our own. 2020-01-03 08-38-14 PST Patrick (but unfortunately retired) 2020-01-03 08-30-38 PST Patrick The main idea for the bug wrangling team was that it should *not* require developers to be able to properly triage a bug 2019-03-02 09-36-52 PST Patrick As we're in the process of migrating from LaunchPad to GitLab for issue tracking we currently have no established "bug wrangling guidelines" yet, but you're basically doing everything right already ;-) 2020-01-03 08-29-30 PST Patrick Yes, you've done a lot more than we can expect from the average bug wrangler! 2019-12-10 00-31-06 PST Patrick We can grant rights for the Bug wrangler group going forward, then he can move issues into subproject and relabel and also close them there 2020-01-03 08-36-54 PST Patrick The problem is that we know developers are usually too busy to triage bugs :-D 2020-01-03 08-27-03 PST Patrick [ ](https://chat.inkscape.org/direct/nathanal?msg=PogyfSLDujmhnMgdy) Sure, I've added the membership to https://gitlab.com/inkscape/inkscape-docs/documentation (I don't have the required accesss level to the other parts of inkscape-docs either). Let me know if the membership is missing anywhere else - as there are not many active bug-wranglers yet, it's not always obvious when we've missed it somewhere and group management is rather new to everyone in the project. () 2020-01-03 08-33-06 PST Patrick Usually it takes more time to explain to the average user how to create one, than to create it oneself, so I don't think that's efficient. 2020-01-03 08-32-17 PST Patrick Yes, it certainly does not hurt to have a backtrace, but I think Bryce expected a bit too much. If we can slowly teach everybody in the bug wrangling team how to create a bakctrace that'd be a good compromise I think. 2020-01-03 08-01-00 PST Patrick Hi Nathan, no problem at all. We're all doing this in our spare time, so it progresses at fast as it progresses. Better to take it slow and at a pace that is fun, than to try to do it all at once and force it... 2020-01-03 08-38-44 PST Patrick Alvin is still helping a bit but less active than before. 2020-01-03 08-15-34 PST Patrick [ ](https://chat.inkscape.org/direct/nathanal?msg=sRgeSZEKAsxpJnPfG) Yes! One of the main ideas / hopes of the bug migration game was that we might attract people who are able and willing to do some bug wrangling. If you think somebody does a good job at migrating, you can offer them reporter permissions for inbox early on, so they can label the migrated issues (and possibly others). If they're doing a good job overall, we can also add them to the bug-wranglers team (which should give them reporter permissions in all relevant subprojects and therefore the possibility to move issues). I've just changed maximum permissions of the bug-wranglers team in inbox, so you should have inherited maintainer permissions there and be able to add new members (let me know if that did not work for some reason). () 2020-01-03 08-38-04 PST Patrick I'm sure you've seen the name "suv" somewhere and maybe "jazzynico" - they were extremely good at triaging! 2020-01-26 06-08-23 PST Patrick Yeah, I read that, great to know it's resolved. We should probably add the group after all - at some point in the past we actually decided to use groups for managing permissions wherever possible (I guess Martin missed that memo...), but for now it's obviously fine. 2020-01-03 08-19-03 PST Patrick [ ](https://chat.inkscape.org/direct/nathanal?msg=DpwQinbRXFKRkg5dW) I'm not quite sure what you meant by "diagnosis". Ideally a bug should be verified (i.e. reproduced) in inbox and then moved to a subproject (with suitable labelling, a good title, reliable steps to reproduce, and - if the original report ended up very convoluted - a summarized description of the issue, possibly even as a new issue to replace the old convoluted one). I'd not make a back-trace a requirement (simply because some users won't know how to create one and it's just as easy to create one for developers once they have reliable steps to reproduce). () 2019-03-02 09-39-44 PST Patrick Also you can assign labels now - we've not decided on final labeling yet (any help in that regard is welcome, too!), but you're welcome to use what's already there.