Except it is not, it is a closed beta.ghettosynth wrote:I don't know, you tell me? Their web site says "we're beta testing, sign up to our newsletter if you want to test."JoeCat wrote:Was Bitwig not offering a free/discounted copy to beta testers who participated fully? (not a snarky implication, but an honest questionghettosynth wrote:So, when I agree to beta something, I'm not agreeing to take on a part time job. I'm agreeing to use it in the way that I'm using my existing software and I'm agreeing to try out the new features as I would normally. If I encounter problems I'm agreeing to report the bugs and/or not complain if you capture logs from my usage.Kriminal wrote:Didnt apply, so, no. Its a big job testing a Host properly. Much bigger than a synth. Dont have the time (or the inclination...i only test stuff that im interested in) so wouldnt be much use.
Always amazes me the amount of ppl who join beta teams full of promises and cant deliver....
If you want me to test YOUR software like I test MY software, then you MUST offer to pay me what my time is worth. In my opinion, beta testers are getting something of very limited value so to expect much from them is simply unrealistic. As a dev you should be gathering logs and you should be doing analysis of those logs to see what kind of coverage across different hardware/software configurations that you're getting as well as using them to help validate/refute known bug reports.
In short, I think that me offering to use your "buggy" software for a few weeks for nothing more than the privilege of using your "buggy" software for a few weeks is a great deal for you!)
I've almost never seen this to be the case with "open betas", which, to me, make the most sense. For my efforts, which have been minimal, I've received no compensation of any sort for beta testing. To be clear, I'm perfectly ok with that. I view the beta test as an open minded extended demo. That is, I'm seeing if I want to switch/upgrade and I'm willing to help you with any issues that I find. The thing is, I do this anyway even if I'm not beta-testing. I have almost always found that the bugs that I know about have already been reported, but, I go out of my way to report bugs in products that I like. If you're asking for detailed reporting that doesn't really sound like "beta" testing to me, that sounds like you're still working out the bugs in your alpha.I've been on a few beta test teams before and that was usually the case - but you did need to fully participate (utilize the software quite fully, document and report bugs, assist in verification, etc.)
Sure, I agree that if you are getting a free license worth several hundred dollars or more then your obligation is more than what should be expected in an open beta. By open here, I really mean semi-open. That is, anyone can participate, but you still have to wait until you're asked to help to download. So, in other words, like what Bitwig is doing.Otherwise, yeah. Pay me to be part of the Q/A team.
Just because they fill their pool with an open application doesn't mean the actual beta is open.
It is no different than having a company and listing jobs on Monster.com
You fill the positions through an open request. It doesn't mean they hire just anyone who fills a job application.
