| Time |
Nick |
Message |
| 01:14 |
|
qur joined #minetest-dev |
| 02:02 |
|
appguru joined #minetest-dev |
| 03:29 |
|
YuGiOhJCJ joined #minetest-dev |
| 04:30 |
|
diceLibrarian joined #minetest-dev |
| 05:00 |
|
MTDiscord joined #minetest-dev |
| 05:45 |
|
fluxionary joined #minetest-dev |
| 07:18 |
|
diceLibrarian joined #minetest-dev |
| 08:23 |
|
calcul0n joined #minetest-dev |
| 09:14 |
|
lionkor joined #minetest-dev |
| 11:39 |
|
appguru joined #minetest-dev |
| 12:28 |
|
imi joined #minetest-dev |
| 12:44 |
|
lionkor joined #minetest-dev |
| 15:47 |
|
Desour joined #minetest-dev |
| 15:47 |
|
appguru joined #minetest-dev |
| 16:22 |
[MTMatrix] |
<Zughy> is any core dev against triagers labelling issues as "High priority" at their own discretion? |
| 16:41 |
MTDiscord |
<warr1024> What criteria would you use? Would it be more like "based on the content of the issue it sounds serious" or more like "based on my external knowledge of the ecosystem and community I know this has significant impact"? |
| 16:45 |
[MTMatrix] |
<Zughy> I'd say the latter, e.g. fixes to the annoying hacks the community have been using for years because X doesn't really work |
| 16:49 |
MTDiscord |
<warr1024> I guess if you were to describe the situation in a comment on the issue thread then the latter would become also the former. |
| 16:51 |
MTDiscord |
<warr1024> I guess there is a bit of a meta question about who should be in charge of prioritizing the backlog, e.g. is there like a "product owner" role or something, or do we have some kind of voting or other community driven system. That all may be moot of course considering that items get worked on based on what people want to work on more than backlog priorities. |
| 16:52 |
MTDiscord |
<warr1024> We could just give it a try and see what its effects are. Maybe it helps clear some big blockers. Or maybe the community misinterprets its significance and starts a bunch of fights over it and we just scrap it. I could see it going both ways 😅 |
| 19:32 |
|
Desour joined #minetest-dev |
| 21:04 |
|
appguru joined #minetest-dev |
| 21:17 |
|
lionkor joined #minetest-dev |
| 21:39 |
[MTMatrix] |
<Zughy> well, I'll start |
| 21:49 |
MTDiscord |
<luatic> I'd like to see some feature requests labeled high priority actually |
| 21:51 |
[MTMatrix] |
<Zughy> feel free to suggest them. If you don't want to spam here, please pm me on Matrix |
| 21:52 |
MTDiscord |
<luatic> I was hoping you knew a few popular ones 😅 |
| 21:53 |
[MTMatrix] |
<Zughy> By the way: basically I'm labelling "high priority" those issues that make games unplayable and/or force modders to implement convoluted hacks to do something that should be really simple. I do not have the knowledge to evaluate very technical engine things, so I'll pass on those |
| 21:53 |
[MTMatrix] |
<Zughy> luatic: I can probably find some, let's see (ofc I'll try to be as much impartial as I can) |
| 21:56 |
MTDiscord |
<warr1024> The idea of labeling feature requests as high priority makes me wonder whether there would then be bugs and feature requests, some of which are high priority, or whether there'd be high priority items, some of which are bugs and some of which are feature requests. The difference in the semantic meaning comes about in terms of whether a high priority feature request is always higher or lower priority than a low priority bug, or |
| 21:56 |
MTDiscord |
whether there's some ambiguity and it would still need to be handled case by case. |
| 21:56 |
MTDiscord |
<warr1024> As long as there are high priority bugs, though, then it seems like high priority feature requests will always be at least a little moot 😄 |
| 21:57 |
MTDiscord |
<warr1024> It would be nice if I had at least some way of labeling my own bugs. Some of the things I report, I do so because they're major issues for me, but others are just things I merely noticed and thought deserved to be known, but if nobody else concurs on them, I'd be fine with letting them slide for a while. |
| 21:58 |
MTDiscord |
<warr1024> In particular, issues that have known workarounds or mitigations are less urgent than ones that leave certain folks SOL. |
| 22:01 |
[MTMatrix] |
<Zughy> Changed my mind: there are 204 feature requests that are also supported by core devs and, basically what warr1024 says about bugs being prioritised anyway. You can still do (limited) stuff with a missing feature, but if the bug breaks the game (whether is a crash, an immersion issue etc) is a horse of a different colour |
| 22:02 |
[MTMatrix] |
<Zughy> Reminder, you can help us by listing your 3 most annoying bugs on #14004 |
| 22:02 |
ShadowBot |
https://github.com/minetest/minetest/issues/14004 -- :bug: Name the 3 most annoying bugs you'd like to see fixed |
| 22:02 |
MTDiscord |
<warr1024> Lol, you can unless you have reported more than 3 critical bugs yourself. |
| 22:04 |
[MTMatrix] |
<Zughy> If I change that rule, we'll probably end up having people reporting their own bugs because everyone thinks their own stuff is more important. I don't wanna take that risk |
| 22:05 |
MTDiscord |
<warr1024> Figuring out which of peoples' own bugs are the ones they actually care most about is valuable information too. And not everybody has actually filed their own bug reports, so you'll still get some useful data. |
| 22:06 |
MTDiscord |
<warr1024> Maybe the sanest thing to do is just use the standard bug upvoting systems that most issue trackers offer, though in the case of GH I'm not sure how good their system is or whether it's just 👍 reacts on the issue OP or something. |
| 22:07 |
MTDiscord |
<warr1024> tbf if GH allows the poster to 👍 react their own issue, and some do but not all do, then you might have to adjust for that if it came down to small differences like that, but you'd probably be able to grab at least like 3 to 5 issues fairly before you'd get that far down anyone's list. |
| 22:07 |
sfan5 |
i dont think there's a way to sort issues by reactions however |
| 22:08 |
rubenwardy |
There is, it's in the sort menu |
| 22:08 |
rubenwardy |
It's by specific reaction though |
| 22:08 |
sfan5 |
oh |
| 22:08 |
MTDiscord |
<warr1024> I mean if you want to really do it properly it might end up being an export-and-analyze kind of process, of course, but I don't think that's insurmountable if we're serious about it. |
| 22:10 |
MTDiscord |
<warr1024> The "list your top 3 bugs" thread isn't necessarily problematic if you just assume that every issue already has a nomination from its original poster, but it doesn't allow us to sort order among our own issues, and the fact that I'm listing say issues #12, 13, and 14 off my own list makes listing them as 1, 2 and 3 on the thread seem disingenous. |
| 22:10 |
ShadowBot |
https://github.com/minetest/minetest/issues/12 -- Jack O Lantern for Halloween ! by Myu-Unix |
| 22:10 |
MTDiscord |
<warr1024> oh argh dammit bot |
| 22:10 |
MTDiscord |
<wsor4035> https://github.com/minetest/minetest/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc assuming thumbs up are the most cared for |
| 22:11 |
MTDiscord |
<warr1024> I don't know if we can/should make that assumption yet, but we could definitely start to establish it as a standard. |
| 22:11 |
MTDiscord |
<warr1024> We need to let people know that they should use the reaction and how it will be interpreted before we can expect really good data from it. |
| 22:13 |
MTDiscord |
<warr1024> Also, the inability to give unequal amounts of upvote to different things is kind of irksome. There are times I would like to elevate an issue above the "noise floor", but not necessarily above a handful of other more urgent issues, and I don't know how to express that using this system. |
| 22:14 |
[MTMatrix] |
<Zughy> Different "Dimensions" as low priority: ....mm. |
| 22:15 |
[MTMatrix] |
<Zughy> oh, Paramat, of course |
| 22:16 |
MTDiscord |
<wsor4035> typical |
| 22:17 |
MTDiscord |
<wsor4035> well, sorry, i retract that, typical would be closing it |
| 22:18 |
MTDiscord |
<wsor4035> if you want some interesting viewing, cross compare hearts vs thumbs up ratings |
| 22:20 |
[MTMatrix] |
<Zughy> it's also interesting how people don't usually use many thumbs down, unless it's a discussion about MT future |
| 22:25 |
MTDiscord |
<warr1024> People probably most 👎 discussions about the future less in an "I disagree with this proposal" sense and more in an "I'm tired of hearing about this can we just fix some of the existing issues instead" sense. |
| 22:36 |
MTDiscord |
<warr1024> Looking at all the upvoted stuff, it's pretty much all feature requests and such ... I wonder what it looks like for bugs, but it seems like it's kind of a pain to filter by the multiple tags that make up the set of bugs (or filter OUT the multiple tags that represent known non-bugs) |
| 22:46 |
|
imi joined #minetest-dev |
| 23:28 |
|
loggingbot_ joined #minetest-dev |
| 23:28 |
|
Topic for #minetest-dev is now Minetest core development and maintenance. Chit-chat goes to #minetest. https://dev.minetest.net/ https://irc.minetest.net/ https://github.com/minetest |
| 23:32 |
|
panwolfram joined #minetest-dev |
