Hi AmpForWP,
By “Development Process”, I meant what your plugin team does to develop the plugin.
Your development process clearly involves work at other websites such as github.com and magazine3.com, as well as your activities on this website www.remarpro.com.
I am happy to be involved in this process, but only what can be done via this www.remarpro.com website.
The guidelines that you refer to for this www.remarpro.com website are satisfactory for us, and keeping activity to this site means we do not need to acquaint ourselves with other sites, systems, methods, etc.
We are happy to download through this site, and provide feedback and suggestions through this site.
If we start getting involved in other websites, then we can very quickly end up being all over the place, trying to keep up with each matter we are involved with.
We are not so enthusiastic to be dealing with many bookmarks for sites, logins, etc, and methods of keeping track of progress.
I understand that it is the norm for the developers to be the ones who have chosen how they want to interact with beta test users. But there are probably other ‘would be’ beta test users out there, that would be involved, if there were more favourable options for them to get involved (easy, more reliable on safety/security, no extra stuff to learn, familiar feedback system, etc).
You may take what I have said here as a kind of user feedback on developer systems.
I have tried to think of some ways that this might be possible.
And as a plugin developer team, you might be able to tell me how we can work together via this www.remarpro.com website to test your beta plugin.
Thank you for your assistance.