Editing GSoC 2021 application
Jump to navigation
Jump to search
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 2021. | Octave's application for GSoC 2021. | ||
=== Why does your org want to participate in Google Summer of Code? (1000 chars) === | === Why does your org want to participate in Google Summer of Code? (1000 chars) === | ||
Line 16: | Line 8: | ||
Google Summer of Code represents a unique opportunity to bring new perspectives to the Octave community. As a somewhat older project, we benefit from having new and younger contributors among our developers. We have been able to retain several GSoC participants as contributors to the Octave project and we hope to continue this in the future by engaging effectively with students during both the application and mentoring processes, setting clear standards for what is required for acceptance, and maintaining those standards throughout the project. | Google Summer of Code represents a unique opportunity to bring new perspectives to the Octave community. As a somewhat older project, we benefit from having new and younger contributors among our developers. We have been able to retain several GSoC participants as contributors to the Octave project and we hope to continue this in the future by engaging effectively with students during both the application and mentoring processes, setting clear standards for what is required for acceptance, and maintaining those standards throughout the project. | ||
=== How many potential mentors have agreed to mentor this year? === | === How many potential mentors have agreed to mentor this year? === | ||
Line 48: | Line 35: | ||
Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list. | Everything should be completely open. Almost all interactions with the student should be public, e.g. contacting the mentor should happen in the public IRC channel or copy the maintainers mailing list. | ||
Finally, we organize an annual developers' summit, OctConf, and have in previous years provided support for GSoC students to attend and present. | Finally, we organize an annual developers' summit, OctConf, and have in previous years provided support for GSoC students to attend and present. This strengthens relationships between community members and the new students. | ||
=== How will you keep students involved with your community after GSoC? (1000 chars) === | === How will you keep students involved with your community after GSoC? (1000 chars) === | ||
Line 58: | Line 45: | ||
A number of GSoC alumni have continued making regular contributions to GNU Octave, including volunteering to serve as GSoC mentors, and many remain available to help with any problems related to the code they wrote for the project. | A number of GSoC alumni have continued making regular contributions to GNU Octave, including volunteering to serve as GSoC mentors, 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? For each year your organization has participated, provide the counts of successful and total students. === | |||
=== Has your org been accepted as a mentoring org in Google Summer of Code before? === | |||
Yes. | Yes. | ||
2019 0/0 | 2019 0/0 | ||
2018 3/3 | 2018 3/3 | ||
Line 86: | Line 60: | ||
2012, 2013, 2015 | 2012, 2013, 2015 | ||
=== Are you part of a foundation/umbrella organization? === | |||
Yes, we are affiliated with GNU. | |||
=== What year was your project started? === | === What year was your project started? === | ||
Line 91: | Line 69: | ||
1992 | 1992 | ||
=== | === Organization ID === | ||
octave | |||
=== Organization name === | |||
GNU Octave | |||
=== | === OSI approved license? === | ||
Yes | |||
=== | === Organization Category === | ||
Programming Languages and Development Tools | |||
=== Tagline (80 characters) === | === Tagline (80 characters) === | ||
Free Your Numbers | Free Your Numbers | ||
=== Primary License === | === Primary License === | ||
GPL 3.0 | GPL 3.0 | ||
=== Technology Tags (the primary specific technologies your organization uses) (up to 5) === | === Technology Tags (the primary specific technologies your organization uses) (up to 5) === | ||
Line 127: | Line 101: | ||
mathematics, numerical computation, numerical methods, matlab, scientific computing | mathematics, numerical computation, numerical methods, matlab, scientific computing | ||
=== | === Proposal Tags (for applicants to use) (up to 10) === | ||
Numerical, Infrastructure, Octave Forge, Image analysis, Machine learning, GUI, Graphics, New feature, Performance, Matlab compatibility | |||
=== Description (180 chars) === | === Description (180 chars) === | ||
Line 140: | Line 113: | ||
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. | 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 | Octave is continually being upgraded. The current version 5.1 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) === | === Application instructions (1500 chars) === | ||
Line 148: | Line 121: | ||
<code> | <code> | ||
Post on our [mailing list](https://lists.gnu.org/mailman/listinfo/octave-maintainers) or chat on [IRC](https://webchat.freenode.net/?channels=#octave | 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. | 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](https://wiki.octave.org/Special:CreateAccount) on our Wiki and then copy and fill out Octave's [application template](https://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](https://wiki.octave.org/Summer_of_Code_-_Getting_Started). | For more details, please see the [Octave Wiki](https://wiki.octave.org/Summer_of_Code_-_Getting_Started). | ||
Line 158: | Line 131: | ||
</code> | </code> | ||
=== | === Organization urls === | ||
http://www.octave.org | |||
Logo: https://upload.wikimedia.org/wikipedia/commons/thumb/6/6a/Gnu-octave-logo.svg/283px-Gnu-octave-logo.svg.png (or generate 256x256 PNG from http://hg.savannah.gnu.org/hgweb/octave/raw-file/155d8e90ee1f/doc/icons/octave-logo.svg with <code>inkscape -z -e octave-logo.png -w 256 -h 256 octave-logo.svg</code>) | |||
Blog: http://planet.octave.org/ | |||
Feed: http://planet.octave.org/atom.xml | |||
IRC Channel: https://webchat.freenode.net/?channels=#octave | |||
Mailing | Mailing List: https://lists.gnu.org/mailman/listinfo/octave-maintainers | ||
General Email: octave-maintainers@gnu.org | General Email: octave-maintainers@gnu.org | ||
Ideas: https://wiki.octave.org/Summer_of_Code_-_Getting_Started#Suggested_projects | |||
Application instructions: http://wiki.octave.org/Summer_of_Code_Project_Ideas#Steps_Toward_a_Successful_Application | |||
Source code: http://hg.savannah.gnu.org/hgweb/octave | |||
[[Category:Summer of Code]] | [[Category:Summer of Code]] | ||
[[Category:2021]] | [[Category:2021]] |