OutreachProgramForWomen: Difference between revisions

From KDE Community Wiki
m (added category: mentoring)
(→‎Source Code and Junior Jobs: Link to Artikulate junior jobs)
Line 101: Line 101:
===== Source Code and Junior Jobs =====
===== Source Code and Junior Jobs =====
* http://techbase.kde.org/Projects/Edu/Artikulate
* http://techbase.kde.org/Projects/Edu/Artikulate
* Junior Jobs: coming soon!
* Junior Jobs: [https://bugs.kde.org/buglist.cgi?keywords=junior-jobs&bug_status=UNCONFIRMED&product=Artikulate&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&list_id=570087 can be found at bugs.kde.org]


=====Contact Information=====
=====Contact Information=====

Revision as of 16:56, 31 March 2013


We are currently participating in the Free and Open Source Outreach Program for Women, which runs two editions every year.

Introduction

2013 will be the first time KDE will take part, sponsored by KDAB. Round 6 will run from June to September 2013

Program details
Event Date
Application deadline May 1
Dates June 17 - September 23
Number of Internships 1 (sponsored by KDAB)


Goals

The KDE community is participating in this initiative because we aim to:

  • Make strong connections with a few talented people who will stick around
  • Encourage people to work on testing, design, documentation, marketing, and other areas as well as code
  • Increase the number and proportion of women in an open source community
  • Promote age diversity as well


How to contribute

KDE has an extensive wiki documentation on how to contribute to KDE as well as a very convenient KDE Guide in e-book and pdf format.


How to apply

1. Choose a project

2. Make a contribution

3. Send your application

Please see the details here: https://live.gnome.org/OutreachProgramForWomen#Application_Process

Contact details

Mailing lists: KDE has two main lists intended for mentoring programs:


IRC: The IRC counterparts of the mailing lists on irc.freenode.net:

  • #kde-soc
  • #kde-women


Program coordinators:


Tasks

We are currently collecting tasks submissions and ask you to Spread the Word

Software Projects

All software projects also require design, documentation, marketing and translation. If you are interested in these tasks, you can learn about both the project and the activities of the relevant team to figure out how to best approach it.

For coding tasks please refer to the GSoC Ideas page. All of them are eligible for the Outreach Program for Women as well.

Design, Documentation, Marketing, etc.

Project: Artikulate

Artikulate is a young language software project that aims helping people to improve their foreign language pronunciation skills. The essential idea is that Artikulate shall provide a set of phrases and corresponding recordings, which are recorded by native speakers. By recording their own attempts and comparing them to the original recordings, students can correct and improve their own pronunciation. The main goal of this task will be to assist in the first release of Artikulate. Since the project is still young, there are still a lot of tasks open in different areas. Your own project proposal will surely reflect this by concentrating only on a subset of the following tasks, tailored to the three months period.

Your project, if you will take it, consists of the following three tasks and an Add-On task from the appended list.

Task 1: Course Files This is the most important one of all tasks! Artikulate already provides an editor and a specific mechanism how to create a course skeleton that is used as a blueprint for courses of other languages. But neither the course skeleton is filled (the goal is to have a set of about 1000 phrases in the end), nor are there courses that provide this set of phrases in other languages. The goal of this subtask is to extend the course skeleton with useful units and phrases (e.g., think about a unit with sentences a tourist needs when visiting a town, or sentences that are used in a restaurant) and provide (besides the skeleton that gives us already an English language course) a translation of one other language. Obviously, it is not possible for you to record every phrase (and not event wanted, since we want to have different voices!) or maybe even a prepare a translation of the course skeleton into another language (if you are an English native and do not speak another language well enough, for example). But no problem! As the internet is full of helpful people (and the KDE community in particular), it will be also part of this task to write blog posts, asking at mailing lists, or even asking friends and teachers to provide recordings or help you with the translations.

Task 2: Documentation As every project, also Artikulate needs a handbook. This handbook must describe for users how to use the program, but also for contributors how to contribute new languages and course files. The handbook will be created at the Userbase Wiki (this also allows later integration into the program).

Task 3: Workflow Planning We need to think about a reliable workflow on how to update and provide course files. A lot of ideas are already partially implemented or drafted. But it needs a written plan to remember those ideas. Also, when writing things down, usually the pitfalls will be discovered that weren't visible before.

The Add-On Tasks:

Add-On Task a: User Interface If you want to dig into QML and QtQuick (this is more a describing language to tell how the user interface shall look than a programming language!) and improve the user interface, this could be a nice subtask for you. If not, it is at least equally good to provide a concept with mockups and sketches how the user interfaces shall be changed to allow better usage for users and language contributors.

Add-On Task b: Implement Highscore System Currently no highscores are saved that remind the user at which phrases or phonemes she/he was good and which she/he still needs to improve. A highscore system will help here. And it will not be that hard to implement it, though it will require coding knowledge in C++.

Add-On Task c: Quality Assurance Protocol Most of the core functionality is implemented or will be implemented when this project starts. But to be sure that everything works as expected, we need a testing protocol that states what functionality we have, what needs to be tested to verify the functionality, and that can be used for every release to test the quality of our software.

Source Code and Junior Jobs
Contact Information

Mentors: Andreas Cord-Landwehr and Myriam Schweingruber

Contact:

Translation