We need a category for reporting problems specifically

gnydick

There are currently 20 categories. If you were dc42, would you rather watch all 20 categories, looking for something that is high priority, i.e. all posts. Or would you rather have a dedicated place, CLEARLY MARKED, not as "high priority", but as "i think my thing is broken" or "i can't get this to work after following all of the docs."

Unless you believe that all posts will miraculously appear in that new area, rather than in the 20 other categories, I think it's pretty clear that giving priority to a category like the ones mentioned and reviewing it more diligently than the others for things that dc42 deems high priority, which I'm assuming is firmware issues, would be much less work.

The math adds up no matter how you look at it. Even with a 99% false positive rate for the questions in that new category, they would still not amount to the volume of the entire forum.

fcwilt

@gnydick

I would that dc42 simply process on a first come/first serve basis.

I think you are being too kind of you think the system won't be abused.

Phaedrux

@gnydick said in We need a category for reporting problems specifically:

If you were dc42, would you rather watch all 20 categories, looking for something that is high priority, i.e. all posts.

We don't have to imagine what it would be like to be DC42 and answer for him. The man has answered for himself.

@dc42 said in We need a category for reporting problems specifically:

This is why I don't want a bug reporting catagory, but I am open to a "Firmware behaviour" category.

gnydick

@phaedrux exactly. He could see having a firmware category.

gnydick

@fcwilt I'm out with talking to you. I acknowledged that it would be abused IF it were given to people as, "please put your high priority stuff here". But that's not what I said...

I said, make some category, that IS the high priority, like "firmware related issues", or "I've followed all the docs, but I still can't get it to work", which are implicitly high priority.

Again, I'm not saying make it like the toggle on email that lets you set priority. To dc42, firmware issues are high priority. If I post something in "firmware issues", like the other day, my machine magically created a 3rd tool, he would want to see that before answering a general question like "how do I attach a mosfet to trigger led lights?".

If you still want to respond with the same thing "it'll be abused", please don't respond because you're not digesting what I'm saying.

deckingman

@gnydick What you are proposing won't work and here is why.

The Duet team know what would help them. I've met them all and can confirm that they are all fully grown up adults, more than capable of making their own decisions.

To this end, they have tried to get users of these forums to do things which would make it easier to solve their issues. A fairly recent example is this sticky https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

Hardly anyone takes any notice of this - YOU INCLUDED - I've just had a quick gander at threads that you have started which confirms this.

So if hardly anyone follows the guidelines that the Duet team have asked for (you included), why do you expect that other users will follow the recommendations that you are proposing?

fcwilt

@gnydick said in We need a category for reporting problems specifically:

I acknowledged that it would be abused IF it were given to people as, "please put your high priority stuff here"

I said, make some category, that IS the high priority, like "firmware related issues".

Again, I'm not saying make it like the toggle on email that lets you set priority.

I understand what you are saying.

BUT simply making some special category that IS high priority is the same as saying "put your high priority stuff here" or being able to mark the post as "high priority".

Folks will know that that special category gets processed first and they will put their posts there. Then dc42, after determining the posts are NOT high priority, will have to either delete them or move them to the correct category.

I fail to see why you object to first come/first serve - it is fair and equitable.

Anyway that's enough on this topic.

Have a great day.

Edgars Batna

@deckingman said in We need a category for reporting problems specifically:

@gnydick What you are proposing won't work and here is why.

The Duet team know what would help them. I've met them all and can confirm that they are all fully grown up adults, more than capable of making their own decisions.

To this end, they have tried to get users of these forums to do things which would make it easier to solve their issues. A fairly recent example is this sticky https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help

All things described in that topic should be mandatory. There shouldn't be any free-form threads when dealing with problems.

deckingman

@edgars-batna said in We need a category for reporting problems specifically:

All things described in that topic should be mandatory. There shouldn't be any free-form threads when dealing with problems.

Exactly so. But how do you enforce it?

It's just human nature that some people don't read or follow written instructions. Maybe what is needed is that people have to fill in some sort of form whenever a new thread is started? That might work but there will always be people who jump in on an existing thread and say "I have a similar problem" but those people may not be using the same hardware or firmware or whatever. So then it becomes necessary for users to fill in a form whenever they make a post, which just isn't going to work.

Edgars Batna

@deckingman Yes, a form. Something like a JIRA bugtracker, Bugzilla, Redmine, etc. There are various tools around that are used for software projects that would apply here quite well. Github is not ideal as it's too free-for-all and applies to software only, the forums being a total one-shot-kill deathmatch in comparison.

Maybe the forum software can be extended to support mandatory fields... but why reinvent all the wheels.

fcwilt

@edgars-batna said in We need a category for reporting problems specifically:

Yes, a form. Something like a JIRA bugtracker, Bugzilla, Redmine, etc.

dc42 has already ruled out a "bug reporting" category.

Structured bug reporting is fine for programmers and beta testers and the like, but for end users it is not going to be pretty.

gnydick

@fcwilt I don't object to first come, first serve. I object to dc42 having to scour all categories equally. Even if the one category was abused, it would still be less than having to worry about missing something hi-pri because it was buried somewhere innocuous.

fcwilt

@gnydick said in We need a category for reporting problems specifically:

@fcwilt I don't object to first come, first serve. I object to dc42 having to scour all categories equally. Even if the one category was abused, it would still be less than having to worry about missing something hi-pri because it was buried somewhere innocuous.

Hmm...

I may have made a invalid assumption. I was thinking that dc42 could view them not by category but by date so it would just be a matter of starting at the oldest post not yet viewed and working towards newer posts.

I will have to ask him.

Phaedrux

@fcwilt said in We need a category for reporting problems specifically:

starting at the oldest post not yet viewed and working towards newer posts.

That would be the unread posts view. That's what I use anyway.

fcwilt

@phaedrux said in We need a category for reporting problems specifically:

@fcwilt said in We need a category for reporting problems specifically:

starting at the oldest post not yet viewed and working towards newer posts.

That would be the unread posts view. That's what I use anyway.

Thanks for that info. It seemed likely there was a way.

Frederick

gnydick

Ahhhh, that's handy

dc42

I use the unread posts view. When I am short of time, I ignore posts whose titles appear to relate to printer construction, print quality issues and similar issues that are not obviously related to the Duet, its firmware and configuration.