Just an idea since Lieve is always repeating herself to provide more information – perhaps we could come up with some sort of submission guideline template to help the great commenters on this forum diagnose the problems you all are having. It could start like
OS
OS Version Number
Captivate Version Number
Mobile/Desktop/Both
Expected Behavior
Barrier
Information found so far
Description of problem or question
Kind of like a bug report template. Ive been reading these comments all day and it seems like the common theme is Lieve never has enough information to start troubleshooting and always has to guess. In addition, bug reporting is a great skill for an ID to have – maybe we can come up with something on this forum. Please contribute.
Not everyone has the same experience. Not everyone has the experience to use the “correct terminology” all the time. People are here to learn. To gain skills. To gain experience. In my opinion it is counter intuitive to restrict how people ask questions and how they can interact with their own available knowledge.
The idea of a community it to share learning, to learn from each other, and to interact. We all rely on the expertise of those that came before us. We all appreciate the help. But we need to be included and welcomed. Not chastised and run out of contributing because we’re not as experienced.
This has been tried already in many ways on the Adobe forums, without result.
Since you mentioned me, one of the issues is use of wrong terminology. It has been years since I pleaded to add a Glossary with ‘official’ terminology to this portal. Tags based on that terminology would help a lot. I could mention multiple examples. Most users just want to get a quick answer, but often ‘invent’ personal terminology. Sometimes it takes days before understanding a question..
You must be logged in to post a comment.