Editing GSoC 2016 application

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 2: Line 2:


Octave's application for GSoC 2016.
Octave's application for GSoC 2016.


=== Why does your org want to participate in Google Summer of Code? ===
=== Why does your org want to participate in Google Summer of Code? ===
Line 11: Line 12:
=== How many potential mentors have agreed to mentor this year? ===
=== How many potential mentors have agreed to mentor this year? ===


6-10
We have about 10 contributors who are potential mentors. They have participated in previous SoC projects, either as students or mentors, and are all active participants in the Octave community. All have previously contributed code, have commit access to either the Octave or Octave Forge source tree, and are active in the mailing lists. Many also keep a constant presence in the IRC channel.


We have about 10 contributors who are potential mentors. They have participated in previous SoC projects, either as students or mentors, and are all active participants in the Octave community. All have previously contributed code, have commit access to either the Octave or Octave Forge source tree, and are active in the mailing lists. Many also keep a constant presence in the IRC channel.
Each project will include at least one core Octave developer as mentor. These are proven, veteran members of the project, active in its development, and familiar with the code base. GNU Octave is a project with applications in very diverse domains so each project should also include a mentor with expertise in the relevant field.


=== How will you keep mentors engaged with their students? ===
=== How will you keep mentors engaged with their students? ===


We will select mentors with proven involvement in Octave and free software and align project topics with the priorities of the core developer team. The vast majority of our mentors have been involved in Octave development for several years, and new mentors will be paired with more experienced ones.
We will select mentors with proven involvement in Octave and free software and align project topics with the priorities of the core developer team. The vast majority of our mentors have been involved in Octave development for several years, and new mentors will be paired with more experienced ones.
Each project will include at least one core Octave developer as mentor. These are proven, veteran members of the project, active in its development, and familiar with the code base. GNU Octave is a project with applications in very diverse domains so each project should also include a mentor with expertise in the relevant field.


=== How will you help your students stay on schedule to complete their projects? ===
=== How will you help your students stay on schedule to complete their projects? ===
Line 25: Line 24:
Previous contributions to Octave by the student will be a condition for acceptance. In this way, we hope to select students who are familiar with the Octave codebase and able to start with their project quickly.
Previous contributions to Octave by the student will be a condition for acceptance. In this way, we hope to select students who are familiar with the Octave codebase and able to start with their project quickly.


A tentative project timeline is required as part of the application, and is checked by mentors for realism as part of the applicant evaluation process. Once a student is selected, the mentor will work with them to come up with a more detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods.
Once a student is selected, the mentor will work with them to come up with a detailed summer timeline, including clear expectations for progress by the midterm and final evaluation periods.


During the summer, mentors will check in with students at least weekly to make sure they are staying on schedule and help with any obstacles that might arise. Students are also expected to regularly update their mentors and the Octave maintainers community on their progress via e-mails and blog posts.
During the summer, mentors will check in with students at least weekly to make sure they are staying on schedule and help with any obstacles that might arise. Students are also expected to regularly update their mentors and the Octave maintainers community on their progress via e-mails and blog posts.  
 
Overall, about 80% of previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our code base.


=== How will you get your students involved in your community during GSoC? ===
=== How will you get your students involved in your community during GSoC? ===
Line 49: Line 46:
=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===


Yes. We have a nice trajectory mentoring projects since 2011 (both as an independent organization and as part of GNU). [http://wiki.octave.org/Summer_of_Code This page] lists the successful projects that have been executed under our mentoring.
Yes. We have a nice trajectory mentoring projects since 2011 (both as an independent organization and as part of GNU). [http://wiki.octave.org/Summer_of_Code This page] list the successful projects that have been executed under our mentoring.


=== Are you part of a foundation/umbrella organization? ===
=== Are you part of a foundation/umbrella organization? ===
Line 57: Line 54:
=== What year was your project started? ===
=== What year was your project started? ===


1992
The main development of Octave began in 1992, with Version 1.0 released in 1994.


=== Organization ID ===
=== Organization ID ===
Line 67: Line 64:
GNU Octave
GNU Octave


=== Tagline (80 characters) ===
=== Tags ===


Free Your Numbers
c++, mathematics, math, numerical, matlab, scientific, computing


=== Technology Tags (the primary specific technologies your organization uses) ===
=== Organization home page url ===
 
C++, hg
 
=== Topic Tags (general topics that describe your organization) ===
 
mathematics, math, numerical, matlab, scientific, computing
 
 
=== Proposal Tags (for applicants to use) ===
 
New feature, Performance, Matlab compatibility, Octave Forge
 
=== Description (180 chars) ===
 
GNU Octave is a high-level interpreted language, primarily intended for numerical computations.
 
=== Description (2000 chars) ===
 
GNU Octave is a high-level interpreted language, primarily intended for numerical computations. It provides capabilities for the numerical solution of linear and nonlinear problems, and for performing other numerical experiments. It also provides extensive graphics capabilities for data visualization and manipulation. Octave is normally used through its interactive command line interface, but it can also be used to write non-interactive programs. The Octave language is quite similar to Matlab so that most programs are easily portable.
 
Octave is continually being upgraded. The current version 4.0 includes a graphical user interface, support for classdef object-oriented programming, and many new and improved functions. SoC projects may also involve developing or upgrading Octave Forge packages, which can be loaded by users to provide additional specialized functions that supplement those provided in Core Octave.
 
=== Organization urls ===


http://www.octave.org
http://www.octave.org
Line 103: Line 77:


Feed: http://planet.octave.org/atom.xml
Feed: http://planet.octave.org/atom.xml
IRC Channel: http://webchat.freenode.net/?channels=octave&uio=MT1mYWxzZSYyPXRydWUmMTI9dHJ1ZQda
Mailing List: http://wiki.octave.org/FAQ#How_can_I_get_involved_in_Octave_development.3F
General Email: help@octave.org
Ideas: http://wiki.octave.org/Summer_of_Code_Project_Ideas
Application instructions: http://wiki.octave.org/Summer_of_Code_Project_Ideas#Steps_Toward_a_Successful_Application
[[Category:Summer of Code]]
[[Category:2016]]
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)