We wouldn't have the time nor staff available to audit code.
I should just note that it will be some time before any sort of preview build would be available (I have no time frames to give at this point). Not to explicitly say "it's too early", but just to put things in perspective.
End users are the least qualified to make such a decision.
TrueEnd users are the least qualified to make such a decision.
Many of them use add-ons which are poorly developed yet rate them highly, simply because they know no better.
Just thinking aloud, here.
Some companies use it as a revenue stream. e.g. Apple
But, of course, I don't think really it is seen as any big source of income for Apple. What it does do, though, is filter out those people who want to be part of it, just because they want to be part of it.
£100 isn't a lot of money. Yet, despite always wanting to be involved in beta testing things like OS X and iOS builds, I would never pay it. But, if it was access to a XenForo development programme then I absolutely would. Possibly even more than £100.
Why "especially" ? A paid resource can also be poorly coded and a free resource can be coded as well as a paid resource...Downloads are no guarantee of anything, especially when it comes to free resources.
Not really the company's problem. If you're unable to legally agree to any legal terms, you just don't get to participate. Not just for this, but for a lot of things.The issue being, I'm always sidelined when it comes to early access, due to age limits. NDA's are out the window, due to the fact that contract law doesn't apply to under 18's (although a parent can sign to get around this).
And then there's the fact that if there was to be a charge, what about those that can't afford it but could really do with having early access? Like I said above, £100 is a lot of money to me. I rarely see that...
I agree, and this where the applicaton process comes about. Instead of expecting people to arbitrarily be chosen, make everyone fill out an application. If XenForo representatives agree, then go for it, if they don't, sit out and wait.Then of course there's the fact that choosing people is bad
We then just accept that in the early days of 2.0 it'll be a while before the major add-ons are working.
It's not as if 1.x will be redundant.
It might not help 100%, but it definetely increases the likelihood.So giving advance access to x or y developer/designer may not be any help at all in a lot of cases.
Where is the dislike button?End all be all solution: Give it to staff first, then developers and designers... with the rest of the customers with the release of beta 1.
Who do you deem important? How do you deem important? I agree with a limit from a management standpoint (of the people that is), but that classification of "important" seems silly.25 Seems like a pretty good estimate to the important add-on developers and the few designers we have.
Where is the dislike button?
Where is the dislike button?
Who do you deem important? How do you deem important? I agree with a limit from a management standpoint (of the people that is), but that classification of "important" seems silly.
Indeed. Even giving all add-on developers early access doesn't mean that they will sort out their add-ons in time for a 2.0 final release.If anyone is reliant on add-ons for their site then they will require all add-ons to be updated for 2.0, before they can upgrade.
So giving advance access to x or y developer/designer may not be any help at all in a lot of cases.
We use essential cookies to make this site work, and optional cookies to enhance your experience.