This sounds intriguing to me. Am I understanding this correctly that it shouldn't need to directly involve the mobile engineering team? It sounds like this could be achieved primarily with QA (Michelle/Chris), product (cc'd Howie and Maryana directly), and participants. If so, this could potentially happen in parallel with one or some of our regular engineering iterations. I suspect QA and product in particular are the most crucial for providing guidance on this.
On Thu, Dec 13, 2012 at 6:00 PM, Quim Gil <[email protected]> wrote: > Hi there, > > > SUMMARY > > Does it make sense to organize a sprint for mobile users and developers to > identify and process mobile use examples to feed our QA & automated > regression tests? > > If so, I can help connecting the dots and getting things done. > > > EXTENDED PLAY > > There have been different conversations that could (theoretically) > converge in a single line of events: > > - One of the goals of the Wikimedia Foundation Engineering team is to > organize a "First substantive systematic outreach to potential testers" > https://www.mediawiki.org/**wiki/Wikimedia_Engineering/** > 2012-13_Goals#Milestones_by_**quarter_17<https://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals#Milestones_by_quarter_17> > > - Testing / QA pilot with the Mobile team, an idea briefly discussed with > Michelle Grover and Tomasz Finc that I'm happy to help making it happen. > > - Polishing some pages written mainly by Chris McMahon and Ċ½eljko Filipin, > connecting them with an actual short term plan: > > * > http://www.mediawiki.org/wiki/**QA/Strategy#Test_automation<http://www.mediawiki.org/wiki/QA/Strategy#Test_automation> > * http://www.mediawiki.org/wiki/**Browser_testing/community_** > automated_browser_testing<http://www.mediawiki.org/wiki/Browser_testing/community_automated_browser_testing> > * > http://www.mediawiki.org/wiki/**QA/test_backlog<http://www.mediawiki.org/wiki/QA/test_backlog> > > - Creating a MediaWiki Group to help the people interested in browser QA > stick together and reach to new contributors and similar communities out > there: > http://www.mediawiki.org/wiki/**Groups<http://www.mediawiki.org/wiki/Groups> > > > > Because I'm lazy ;) I'd rather connect all these activities in one > stream: > > 1. Have a first go through the documentation until it can be digested by > mobile users and QA experts willing to help. > > 2. Decide a mobile area to focus, a way to run the sprint and a date for > it. Define also the goals and how to measure the success of the sprint. > > 3. Create a MediaWiki group at least with Chris, Michelle and the next > three people joining. Start listing the right resources. Let newcomers sign > up. > > 4. Advertise the sprint and the group. > > 5. Keep polishing the docs as the sprint approaches and people shows up > with new questions. > > 6. Run the sprint. Have fun. Meet the goals. > > 7. Process the data generated. Distribute barnstars to contributors. > Publish a blog post summarizing the whole thing. > > 8. Another round of polishing and completion to the docs based on the > experience accumulated. Leave everything as ready as possible to organize > the next activity without needing e.g. someone like me. > > How does this sound? > > -- > Quim Gil > Technical Contributor Coordinator @ Wikimedia Foundation > http://www.mediawiki.org/wiki/**User:Qgil<http://www.mediawiki.org/wiki/User:Qgil> > > ______________________________**_________________ > Mobile-l mailing list > [email protected] > https://lists.wikimedia.org/**mailman/listinfo/mobile-l<https://lists.wikimedia.org/mailman/listinfo/mobile-l> > -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
