Changes between Version 1 and Version 2 of SponsoringPrograms/Outreachy/2016-05


Ignore:
Timestamp:
Feb 9, 2016, 1:31:58 AM (3 years ago)
Author:
llogan
Comment:

add everything except project ideas

Legend:

Unmodified
Added
Removed
Modified
  • SponsoringPrograms/Outreachy/2016-05

    v1 v2  
    1 Page to be filled for this round of Outreachy
    2 please help fill this page, see https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2015-05 and https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2015
     1
     2{{{
     3#!div style="border: 1pt dotted; margin: 1em; background-color: #ddf;"
     4'''Note:''' Page to be filled for this round of Outreachy. Please help fill this page, see [[SponsoringPrograms/Outreachy/2016-05]] and [[SponsoringPrograms/GSoC/2015]].
     5}}}
     6
     7[[PageOutline(1-3)]]
     8
     9= Introduction =
     10
     11FFmpeg is the universal multimedia toolkit: a complete, cross-platform solution to record, convert, filter and stream audio and video. It is used by a number of media players (including VLC, MPlayer, and Totem through GStreamer), video distribution websites (including !YouTube and Vimeo), Internet browsers (including Google !Chrome/Chromium), and lots of other software projects in the multi-media field and beyond.
     12
     13[https://www.gnome.org/outreachy/ Outreachy] is a program that helps underrepresented people to get involved in free and open source software. Through the guidance of mentors, interns gain valuable experience interacting with and coding for open source projects like FFmpeg. Additionally, the project and its users benefit from code created from applicants who often continue contributing as developers.
     14
     15This is our landing page for the current round of the program, which will formally start in May, 2016. Please also see our [[SponsoringPrograms/GSoC/2015| Google Summer of Code Page]] for ideas–most are all also eligible.
     16----
     17
     18= Information for Applicants =
     19
     20== Getting Started ==
     21
     221. '''Get to know FFmpeg.''' If you are an applicant interested in contributing to FFmpeg, it is recommended to start by subscribing to the [http://ffmpeg.org/mailman/listinfo/ffmpeg-devel ffmpeg-devel] mailing-list, visiting our !FreeNode IRC channels (''#ffmpeg-devel'' and ''#ffmpeg'' although you will find most developers on the first one), and exploring both the codebase and the development workflow. Feel free to [#ContactingFFmpeg contact us] if you have any questions.
     23
     242. '''Find a project.''' This page will eventually list mentored and un-mentored projects. Mentored projects are well-defined and mentor(s) have already volunteered. Un-mentored projects are additional ideas you may want to consider, but you will have to contact us to find a mentor. You can also propose your own project, if you can think of one that better fits your interest and skill level. If a project description is unclear or you have any questions, please get in touch with its mentor and/or send an email to the program admins at [opw@ffmpeg.org].
     25
     263. '''Contact us.''' If you decide on a project, get in touch with the community and let us know. If you want to work on a qualification task, let the respective mentor know so we can avoid duplicated efforts.
     27
     284. '''Apply.''' Interns should apply by April 7 at the very latest. The "work" period begins May 25 and ends the same day in August. Take a look at [https://gnome.org/outreachy/#apply] for additional information.
     29
     30{{{
     31#!div style="border: 1pt dotted; margin: 1em; background-color: #fffff9;"
     32'''Note''': A friendly reminder that while the application to Outreachy is important for you and Outreachy, FFmpeg mentors will not base their decision solely on the Outreachy application. We will judge the applicant based on their abilities in coding, learning the tools, communication skills etc. So please do not worry about your application being perfect for us. Although it is very important to follow Outreachy's application rules so they can pay you.
     33}}}
     34
     35== Qualification Tasks ==
     36
     37In order to get accepted you normally have to complete a small qualification task. FFmpeg development can be quite challenging and the qualification task helps us figure out whether you are motivated enough and have the potential to deliver successfully.
     38
     39Contact us for assistance on selecting a qualification task. You can also browse the [https://trac.ffmpeg.org FFmpeg Bug Tracker] for qualification task ideas. In general qualification tasks should include submitting a patch to the ffmpeg-devel mailing list which passes review and is accepted into the FFmpeg codebase. It will be common for such patches to need multiple iterations of submissions and reviews, so do not wait too long with the first submission!
     40
     41{{{
     42#!comment
     43#!div style="border: 1pt dotted; margin: 1em; background-color: #fffff9;"
     44'''Note''': Assigned qualification tasks are being tracked [https://trac.ffmpeg.org/wiki/SponsoringPrograms/OPW/2015-05-Qualis here].
     45}}}
     46
     47== Contacting FFmpeg ==
     48
     49If you have questions or comments feel free to contact us via our mailing list, IRC channel, or e-mail one of the FFmpeg Outreachy admins:
     50
     51* '''Mailing-list:''' [http://ffmpeg.org/mailman/listinfo/ffmpeg-devel ffmpeg-devel]
     52* '''IRC:''' ''#ffmpeg-devel'' on [http://freenode.net/ Freenode]
     53* '''FFmpeg Outreachy Admin:''' Kieran Kunhya  (''kierank'' in #ffmpeg-devel on Freenode IRC, kieran at kunhya dot com)
     54* '''FFmpeg Outreachy Backup Admins:''' Michael Niedermayer (''michaelni'' in #ffmpeg-devel on Freenode IRC, michael at niedermayer dot cc), Lou Logan (''llogan'' in #ffmpeg-devel on Freenode IRC, lou at lrcd dot com)