1,864
edits
(copy from last year) |
(Add categories.) |
||
(7 intermediate revisions by one other user not shown) | |||
Line 11: | Line 11: | ||
=== How many potential mentors have agreed to mentor this year? === | === How many potential mentors have agreed to mentor this year? === | ||
11-15 | |||
=== How will you keep mentors engaged with their students? === | === How will you keep mentors engaged with their students? === | ||
Line 23: | Line 21: | ||
=== 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? === | ||
Previous contributions to Octave | Previous contributions to Octave are a condition for acceptance. In this way, we hope to select students who are familiar with the codebase and able to start 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. | 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. | ||
During the summer, mentors will check | During the summer, mentors will check 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, | Overall, the vast majority of previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our codebase. | ||
=== 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 45: | Line 43: | ||
Many of our GSoC students use Octave during the academic year or in their professional careers. As such, they are prone to stay involved with its development, even if at a lower level than during the summer. | Many of our GSoC students use Octave during the academic year or in their professional careers. As such, they are prone to stay involved with its development, even if at a lower level than during the summer. | ||
Several previous | Several previous students have continued with regular contributions to GNU Octave, and many remain available to help with any problems related to the code they wrote for the project. | ||
=== 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? For each year your organization has participated, provide the counts of successful and total students. === | ||
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 (2014 and 2016). | ||
2016 5/5 | |||
2014 3/3 | |||
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. | |||
=== Are you part of a foundation/umbrella organization? === | === Are you part of a foundation/umbrella organization? === | ||
Line 66: | Line 69: | ||
GNU Octave | GNU Octave | ||
=== Organization Category === | |||
Programming Languages and Development Tools | |||
=== Tagline (80 characters) === | === Tagline (80 characters) === | ||
Line 71: | Line 78: | ||
Free Your Numbers | Free Your Numbers | ||
=== Technology Tags (the primary specific technologies your organization uses) === | === Primary License === | ||
GPL 3.0 | |||
=== Technology Tags (the primary specific technologies your organization uses) (up to 5) === | |||
C++, hg | C++, hg | ||
=== Topic Tags (general topics that describe your organization) === | === Topic Tags (general topics that describe your organization) (up to 5) === | ||
mathematics, numerical computation, numerical methods, matlab, scientific computing | |||
=== Proposal Tags (for applicants to use) === | === Proposal Tags (for applicants to use) (up to 10) === | ||
New feature, Performance, Matlab compatibility | Numerical, Infrastructure, Octave Forge, New feature, Performance, Matlab compatibility | ||
=== Description (180 chars) === | === Description (180 chars) === | ||
Line 90: | Line 100: | ||
=== Description (2000 chars) === | === 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 | 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. | Octave is continually being upgraded. The current version 4.2 includes a graphical user interface, support for classdef object-oriented programming, and many new and improved functions. Student projects may also involve developing or upgrading Octave Forge packages, which can be loaded to provide additional specialized functions that supplement those provided in Core Octave. | ||
=== Application instructions (1500 chars) === | |||
(Markdown for links) | |||
<code> | |||
Post on our [mailing list](https://lists.gnu.org/mailman/listinfo/octave-maintainers) or chat on [IRC](https://webchat.freenode.net/?channels=#octave) to get feedback on your ideas, and help with any questions. | |||
Familiarize yourself with using and building Octave, and with any other skills needed to carry out your proposed project. Demonstrate this familiarity by contributing [bug fixes](https://savannah.gnu.org/bugs/?group=octave) or [patches](https://savannah.gnu.org/patch/?group=octave) before the end of the application period. | |||
[Make an account](http://wiki.octave.org/Special:CreateAccount) on our Wiki and then copy and fill out Octave's [application template](http://wiki.octave.org/Template:Student_application_template_public) on your Wiki user page. Also complete your GSoC application on Melange as per Google guidelines. | |||
For more details, please see the [Octave Wiki](http://wiki.octave.org/Summer_of_Code_Project_Ideas#Steps_Toward_a_Successful_Application). | |||
</code> | |||
=== Organization urls === | === Organization urls === | ||
Line 98: | Line 124: | ||
http://www.octave.org | http://www.octave.org | ||
Logo: http://hg.savannah.gnu.org/hgweb/octave/raw-file/155d8e90ee1f/doc/icons/octave-logo.svg (generate 256x256 PNG with | Logo: http://hg.savannah.gnu.org/hgweb/octave/raw-file/155d8e90ee1f/doc/icons/octave-logo.svg (generate 256x256 PNG with <code>inkscape -z -e octave-logo.png -w 256 -h 256 octave-logo.svg</code>) | ||
Blog: http://planet.octave.org/ | Blog: http://planet.octave.org/ | ||
Line 104: | Line 130: | ||
Feed: http://planet.octave.org/atom.xml | Feed: http://planet.octave.org/atom.xml | ||
IRC Channel: | IRC Channel: https://webchat.freenode.net/?channels=#octave | ||
Mailing List: | Mailing List: https://lists.gnu.org/mailman/listinfo/octave-maintainers | ||
General Email: | General Email: octave-maintainers@gnu.org | ||
Ideas: http://wiki.octave.org/Summer_of_Code_Project_Ideas | 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 | Application instructions: http://wiki.octave.org/Summer_of_Code_Project_Ideas#Steps_Toward_a_Successful_Application | ||
[[Category:Summer of Code]] | |||
[[Category:2017]] |