Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
extensions w3c ehrm v3c
its about time dudes
2-3 ppl hafta validate and test plugins before they get a publishing-ok-bbq stamp.
otherwise we get this sooner or later: vanilla is the sickest (coolest) forum with the almost bug-gay-est plugins world wide.
any thoughts?... nilla needs a consortium.
2-3 ppl hafta validate and test plugins before they get a publishing-ok-bbq stamp.
otherwise we get this sooner or later: vanilla is the sickest (coolest) forum with the almost bug-gay-est plugins world wide.
any thoughts?... nilla needs a consortium.
0
This discussion has been closed.
Comments
You'll need guidelines, procedures, policies and a clear testing scope and sequence matrix.
Not to mention clear and accurate record-keeping and accountability.
Having said that, I agree with your premise.
Posted: Tuesday, 20 February 2007 at 5:52PM (AEDT)
Posted: Tuesday, 20 February 2007 at 6:19PM (AEDT)
yeah guys you're right who cares vanilla let's talk about abc. brilliant
other than that .. wanderer you're right, it's a bunch of work, no doubt ... but hey?
ps @ adrian : the use of such abbreviations are allmost normal in the www , and by the way www is also such a wondrous abbreviation sparky.
so you prefer oxford business english flavoured with honorific speech ? c'mon!
I suggest, if you wish to be taken seriously, you put a little more effort into communicating your (in my humble opinion, excellent) suggestion. Maybe then I'll award you my famous elephant stamp!
Posted: Tuesday, 20 February 2007 at 6:51PM (AEDT)
so back to topic.
"tested extensions"... thats the whole message wanderer.
Its one thing when your work is measured, analyzed and reviewed for your (hopefully well paying) job, and its another when it happens for something you do in your spare time whenever you can catch a spare hour. I'm all for constructive feedback, but pass/fail/try again fosters discouragment and raises the bar to beginners. (Joe Schmoe programmer says, 'Why bother? I've never done anything for this software before, It won't even make it through testing, and the testers will just laugh.')
But I believe in quantity over quality, and let the end administrators rate, improve, adapt, provide feedback, make feature requests, and submit the improved add-ons that don't fit the bill. We don't want to impede this process at all.
That being said, Mozilla has a review process for their partially-Vanilla-based add-ons: http://blog.fligtar.com/2006/11/21/reviewing-the-review-process/
They also have a much broader user base and a much higher incentivised developer base.
And mate, quality is always preferable to quantity, every time, no exception.
Posted: Tuesday, 20 February 2007 at 9:01PM (AEDT)
The thing is, any extension which is pre v1 should be understood by people to be a beta or even an alpha. Is that so hard?
Not hard, I understand it, but many sporting version 1.x stink, they don't work or conflict badly with others that do!
Actually they should have a b in the version number if they are beta and not released generally at all if they are alpha!
Posted: Tuesday, 20 February 2007 at 9:32PM (AEDT)