Freelancer
Well-known member
Issue: With third party developers support forums (a thread for each add-on) there are many things mixing up: Bug reports, user feedback, questions – which makes it difficult to track and distinguish between "this button color is so ugly – how can I change it?" requests from "the template xyz misses certain classes at id=abc". This leads to a chaotic cross-post-communication and users as well as developers being frustrated by the other ones' lack of response. The process is too general. You wait for response, then the other one waits for response, if he has seen your post... making progress takes longer than needed or is good for the add-ons.
Proposal: Create a (closed – with limited access) "Beta Testing" forum in the "Development Help" category with a sub-forum per add-on where only a group of assorted beta testers (in a special user group) can help developers find bugs and fixes in a straight forward process. Let developers pick the Beta Testers and help add them to the add-on forum. That distinguishes dedicated testers from the random users that have more general questions and knowledge. Then let the one-thread-support in the Resources Manager be just for general questions and help. But have the Beta Testers be working directly with the developer on making progress with the add-on.
Why not using the developers' support site? Well, for example, I have about 90+ add-ons and I do not want to register on 50 support websites. A centralized approach helps developers to fix inter-add-on-incompatibilites (or features). Developers can track what's going on with other add-ons and tag other developers. Beta Testers might be the "usual suspects" over the add-ons range most of the time. Having everything scattered across numerous boards does slow down the process of information sharing too.
With a dedicated Beta Test Forum, developers will have the certainty that there are responsive testers with particular knowledge that take developing seriously and who are available without loss of friction because developers do not have to wait too long for feedback. A win/win for everybody and it pushes the XF community.
Proposal: Create a (closed – with limited access) "Beta Testing" forum in the "Development Help" category with a sub-forum per add-on where only a group of assorted beta testers (in a special user group) can help developers find bugs and fixes in a straight forward process. Let developers pick the Beta Testers and help add them to the add-on forum. That distinguishes dedicated testers from the random users that have more general questions and knowledge. Then let the one-thread-support in the Resources Manager be just for general questions and help. But have the Beta Testers be working directly with the developer on making progress with the add-on.
Why not using the developers' support site? Well, for example, I have about 90+ add-ons and I do not want to register on 50 support websites. A centralized approach helps developers to fix inter-add-on-incompatibilites (or features). Developers can track what's going on with other add-ons and tag other developers. Beta Testers might be the "usual suspects" over the add-ons range most of the time. Having everything scattered across numerous boards does slow down the process of information sharing too.
With a dedicated Beta Test Forum, developers will have the certainty that there are responsive testers with particular knowledge that take developing seriously and who are available without loss of friction because developers do not have to wait too long for feedback. A win/win for everybody and it pushes the XF community.
Last edited: