On Sun, Oct 27, 2013 at 9:39 AM, Andrea Pescetti <[email protected]> wrote: > Quick reminder: unless at least three volunteers available to mentor several > small tasks, in any area, show up before the weekend is over, and propose > 5-10 small tasks each, I won't ask Apache to apply on behalf of OpenOffice.
Am I understanding the Google page correctly? It sounds like we need tasks in all 5 areas (Coding, Documentation/Training, Outreach/Research, Quality Assurance and User Interface.). We can't just have, say, documentation tasks. Is that correct? It also sounds like tasks should be "bite sized", things that can be done in 2 hours by an experienced project member, or 3-6 hours by a newbie. Some ideas (maybe others have ideas also that they can add): ==Documentation/Training== 1) Write content for the user guide on the wiki 2) Update existing documentation, e.g., get new screen captures to show the AOO 4.0 UI 3) Create a Youtube video to demo a task like mail merge (could be repeated with different topics) 4) Review questions on the support forum and write FAQ's that address the most-common issues ==Outreach/Research== 1) Design a brochure targeted to this age group that explains the benefits of open source and OpenOffice. 2) Find stories related to OpenOffice and write up short summaries for the home page. 3) Create a Youtube video promoting OpenOffice. ==Quality Assurance== 1) Reviewing incoming defect reports and try to confirm them 2) Review old defect reports 3) Run test cases on AOO 4.0.1 and MacOS Mavericks 4) Test case development for Base ==User Interface== ??? Not sure what can be done here/ ==Coding==? For a 13 year old?? How much C++ would they know? Even getting a build is a challenge. Maybe QA automation? Regards, -Rob > Regards, > Andrea. > > > On 24/10/2013 Andrea Pescetti wrote: >> >> Google is organizing the Google Code-in 2013 project, aimed at involving >> 13-17 year old students in free and open source projects. >> >> You can read more at >> https://code.google.com/p/google-code-in/wiki/GCIMentorInfo2013 >> Application deadline: 28 October. >> >> To participate, an organization (it would be Apache, but the other >> Apache projects have, reasonably, difficulties in finding suitable >> tasks) needs to have small tasks (maximum 6 hours of work) available in >> 5 categories: Coding, Documentation/Training, Outreach/Research, Quality >> Assurance and User Interface. >> >> Well, think if you believe this is feasible for us, and think if you >> personally can help! Translation is explicitly banned, but finding small >> tasks is easy (some examples, one for each category: update dictionaries >> and test them, document the new Calc functions, insert a language >> drop-down on the website, write a Calc test with Herbert's new system, >> propose -no implementation- a better layout for the Tools - Customize - >> Keyboard dialog). >> >> Note that this kind of tasks can perfectly be handled by committers who >> are not familiar with the source code. Well, we have plenty of >> committers, we have teachers who are used to managing young people, we >> cover a lot of native languages in case communication in English is >> problematic... If a reasonable number of volunteers show up here, and do >> it soon, we can consider to apply (through Apache). >> >> For the Apache-wide discussion see the relevant messages in >> http://mail-archives.apache.org/mod_mbox/community-dev/201310.mbox/browser >> >> Regards, >> Andrea. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
