On Nov 7, 2012, at 9:31 PM, Rob Weir <[email protected]> wrote:
> On Tue, Nov 6, 2012 at 10:15 PM, Kevin Grignon > <[email protected]> wrote: >> Rob, >> >> Beyond functional test and unit testing, can we perform some system >> testing, based on core usage scenarios? >> > > > How we divide things is somewhat arbitrary but I think this kind of > scenario testing is most typically a product design function. For > example, you could the some of the same kind of testing with a paper > prototype. > > But one idea, if you want to push the UX/design side of this forward > is to follow the model we're doing with QA and Localization: > > 1) Ask yourself, if in 1 week you could have 5 new UX volunteers, of > various skill levels, what could they do *now*? > > 2) Prepare one or more pages on the website or wiki that list things > they could get involved in. > > 3) Since most would be new to Apache you probably also wold want to > connect this into the Orientation work: > http://incubator.apache.org/openofficeorg/orientation/ > > 4) Maybe it is time for a UX-specific mailing list? > > 5) Prepare a blog post that we can promote a UX Call for Volunteers > > Key observation: when we do a call for volunteers, people will > volunteer in a staggered pattern, some on day one, some on day 2, some > a week later, some two weeks later, etc. You will go crazy if you > have explain the same basic things on the list, over and over again. > So getting the common questions that everyone will have onto the > website is key. That is the purpose of orientation. > > I'm hoping we can take this general approach and refine it based on > experience with QA and L10N then apply it more broadly to other areas > of the project, including UX, Market, Dev, Website, etc. > > -Rob > > Good stuff. Thanks for sharing. This aligns with my initial thoughts and provides some great recommendations to move forward. > >> This is a great way to get more non-technical people involved. Validating >> the system's ability to realize our core usage scenarios is really >> important. >> >> This also means we need to crank up the survey effort, where I was working >> on deploying a top task validation survey. Ultimately, we need to capture >> our core usage scenarios in a single, trusted source for all stakeholders >> to reference moving forward. >> >> Regards, >> Kevin >> >> >> >> On Wed, Nov 7, 2012 at 6:31 AM, Kay Schenk <[email protected]> wrote: >> >>> On Tue, Nov 6, 2012 at 8:32 AM, Rob Weir <[email protected]> wrote: >>> >>>> >>> https://blogs.apache.org/preview/OOo/?previewEntry=you_can_help_us_improve >>>> >>>> If anyone has other ideas for the list of reasons to help with QA, let me >>>> know. >>>> >>>> But in general it looks like we're ready to start a major recruitment >>>> effort for QA. We can probably do something similar for localization >>>> soon as well. >>>> >>>> -Rob >>>> >>> >>> oK, this is good. My one comment would be to link to *some page* on "Apache >>> OpenOffice 4.0" that contains information on what this release will >>> provide. I would think the more volunteers felt it was worthwhile, the >>> more likely they would be to help with QA. >>> >>> Looking forward to the final draft. >>> >>> -- >>> >>> ---------------------------------------------------------------------------------------- >>> MzK >>> >>> "Anyone who considers protocol unimportant has never >>> dealt with a cat." >>> -- Robert Heinlein >>>
