flux reports: we should give the players a w ... #1358
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/petz
3. source/testserver
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/QA main
4. step/QA NOK
4. step/QA OK
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1358
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
This is an interesting idea! I don't think the votes are enforceable though. I think that players would expect they are binding, we cannot guarantee that though. No one here is getting paid, so no one here can be held accountable/treated as if this was a paid job. We avoid giving promises for solid deadlines for the same reason. Life happens and we all need to take care of other responsibilities, too. When my freelance work picks up, my dev speed here slows down. This is at least my take.
Hm. I also don't like the idea of the vote being "enforcable", but I would like some measure of what players' priorities are. I don't think it'd make sense to ask players about individual bugs, but more along the lines of things like this:
Perhaps we could have a submissions box to add more things I'm not even thinking about.
I also don't want this sort of thing to get in the way of e.g. development of
yl_seasons
or the major milestones.Since we have a mature and eager-to-be-engaged audience, I think it's a good idea to ask them their wishes.
We could at least ask them their most pressing wish. If someone is queried for ALL their wishes, they most likely start thinking about new mapgens and other fancy, but hard-to-do stuff. But if we ask them to submit ONE really really neccessary change, maybe the can agree on something?
We could even show this issue to the folks and ask their input?
Then again, I'm already heads deep in bugfixing and doing stuff, I couldn't spare the time for some major out-of-line feature. For me, it's cities update all along.
Okay, maybe we could make a test run of this.
If we just throw the gitea link at people to comb through issues non devs might be overwhelmed. So maybe we should make an assortment of 3-5 things and then let people vote.
I'd definitely consider player wishes, there's always more to fix than I have time and capacity, but then I could at least do something players really urgently desire.
Also I'm going to be honest, by now I don't know whether I can fix petz at all.
I should just set up an NPC in haven who can list a few possible bugfixes, updated weekly, and use that to gauge player interest in various things. And I really want to do this only for my own priorities, not anyone else's. Like a "what should flux work on next" kinda thing.
I'd rather have "what should development solve next" decided by the Next milestone and the general roadmap, but setting up an NPC sounds like a good idea. We could ask more general questions even, provided there are anonymous answering methods.
"How did you find out about Minetest?"
"Why did you choose YL instead of a different server?"
"What made you play a server instead of singleplayer?"
"Where do you think YL should focus on improving?"
"Is there a bug that you think should be fixed most urgently?"
"Is there a feature that was not turned down in the past, but you feel should be considered adding?"
"What other games do you play?"
"What device are you playing YL on?"
"Would you use a VR headset, if Minetest supported it?"
"How long have you been playing YL and what's your level?"
"What aspects of YL do you enjoy the most?"
"Do you think the server rules are clear and fair?"
"Are you using other YL aligned services like discord, website or gitea?"
...
Feel free to add yours.
The more detailed the question, the finer the answers will be and possibly more wishes will be awakened, the implementation of which will have to wait all the longer.
Why not start small, as flux suggested? With an NPC and "few" concrete questions, without being enslaved ("updated weekly") in terms of time. You can always expand this later.