GSoC 2022 application: Difference between revisions

From Octave
Jump to navigation Jump to search
(Copied 2021 page)
 
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
_NOTOC__
__NOTOC__


Octave's application for GSoC 2022.
Octave's application for GSoC 2022.
Line 11: Line 11:
Yes
Yes


=== Why does your org want to participate in Google Summer of Code? (1000 chars) ===
=== Has your organization participated in Google Summer of Code before? ===


We hope to establish collaborations with talented new contributors. We also want to raise awareness of Octave in the free software community.
Yes


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.
=== Please select all years in which your organization participated prior to 2022 ===


=== What would your org consider to be a successful summer? (500 chars) ===
2016-2021, 2014


We would consider a summer successful if we selected promising students, provided adequate mentor supervision, developed desired features in Octave, and facilitated a satisfying experience for the students and mentors. We are more interested in the quality of interactions and contributions than in quantity, although, all else being equal, we would be happy to have more talented students join us.
=== Website URL ===


=== How many potential mentors have agreed to mentor this year? ===
https://www.octave.org


11-15
=== Logo (Must be a 24-bit PNG, minimum height 256 pixels.) ===


=== How will you keep mentors engaged with their students? (1000 chars) ===
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>)


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.
=== Tagline (50 characters) ===


Each project will include at least one core Octave developer as mentor. These are proven, veteran members of the project who are familiar with the code base and with engaging the maintainer and user community. 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.
Free Your Numbers


=== How will you help your students stay on schedule to complete their projects? (1000 chars) ===
=== Primary License ===


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.
GPL 3.0


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


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.
1992


Overall, the vast majority of previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our codebase.
=== Source code location ===


=== How will you get your students involved in your community during GSoC? (1000 chars) ===
https://hg.savannah.gnu.org/hgweb/octave


Students will be urged to participate in our IRC channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which is aggregated at http://planet.octave.org


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.
=== Organization Category ===


Finally, we organize an annual developers' summit, OctConf, and have in previous years provided support for GSoC students to attend and present. In the past year, we have also held monthly online developer meetings to discuss Octave's direction and future activities, to which GSoC students would be invited. Such meetings strengthen relationships between community members and the new students.
Programming Languages, Science


=== How will you keep students involved with your community after GSoC? (1000 chars) ===


We will typically merge their code into our codebase during or soon after the summer. GNU Octave is a project with many tester-users who give constant feedback on new features and report bugs. As participants in the mailing lists and bug tracker, students get the feeling of doing something that is useful to the community from the very start.
=== Technology Tags (the primary specific technologies your organization uses) (up to 5) ===


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.
C++, hg


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.
=== Topic Tags (general topics that describe your organization) (up to 5) ===


mathematics, numerical computation, numerical methods, matlab, scientific computing




=== Has your org been accepted as a mentoring org in Google Summer of Code before? ===
=== Description ===


Yes.
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.


=== How many students did you org accept for 2020? ===
Octave is continually being upgraded. 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.


1


=== How many of your org's 2020 students have been active in the community in the past 60 days? ===
=== Contributor guidance / Idea List ===


0
https://wiki.octave.org/gsoc


=== For each year your organization has participated, provide the counts of successful and total students. ===
=== Contact methods ===


2020 1/1
Chat: https://octave.discourse.group/
2019 0/0
2018 3/3
2017 4/4
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.
Mailing list: https://lists.gnu.org/mailman/listinfo/octave-maintainers


=== If your org has applied for GSoC before but not been accepted, select the years ===
Email: octave-maintainers@gnu.org


2012, 2013, 2015
=== Why does your org want to participate in Google Summer of Code? (1000 chars) ===


=== What year was your project started? ===
We hope to establish collaborations with talented new contributors. We also want to raise awareness of Octave in the free software community.


1992
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 who have become important 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.


=== Where does your source code live? ===  
=== What would your org consider to be a successful summer? (500 chars) ===


http://hg.savannah.gnu.org/hgweb/octave
We would consider a program successful if we selected promising students, provided adequate mentor supervision, developed desired features in Octave, and facilitated a satisfying experience for the students and mentors. We are more interested in the quality of interactions and contributions than in quantity, although, all else being equal, we would be happy to have more talented students join us.


=== Is your organization part of any government? ===


No


=== Website URL ===


http://www.octave.org


=== Tagline (80 characters) ===


Free Your Numbers
=== Is your organization part of any government? ===


=== Logo (Must be a 24-bit PNG, minimum height 256 pixels.) ===
No


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>)


=== Primary License ===


GPL 3.0


=== Organization Category ===


Programming Languages and Development Tools
=== How will you keep mentors engaged with their students? (1000 chars) ===


=== Technology Tags (the primary specific technologies your organization uses) (up to 5) ===
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.


C++, hg
Each project will include at least one core Octave developer as mentor. These are proven, veteran members of the project who are familiar with the code base and with engaging the maintainer and user community. 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.


=== Topic Tags (general topics that describe your organization) (up to 5) ===
=== How will you help your students stay on schedule to complete their projects? (1000 chars) ===


mathematics, numerical computation, numerical methods, matlab, scientific computing
Previous contributions to Octave (which can be small) 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.


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


https://wiki.octave.org/Summer_of_Code_-_Getting_Started#Suggested_projects
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, the vast majority of our over 30 previous SoC students have finished successfully, making substantive contributions to Octave that have been integrated into our codebase.


=== Description (180 chars) ===
=== How will you get your students involved in your community during GSoC? (1000 chars) ===


GNU Octave is a high-level interpreted language, primarily intended for numerical computations.
Students will be urged to participate in our chat channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which will be aggregated at http://planet.octave.org


=== Description (2000 chars) ===
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.
 
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 6.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) ===
 
(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) or [Discourse](https://octave.discourse.group/) 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.
 
Complete your GSoC application as per Google guidelines.
 
For more details, please see the [Octave Wiki](https://wiki.octave.org/Summer_of_Code_-_Getting_Started).


</code>
Finally, we organize an annual developers' summit, OctConf, and have in previous years provided support for GSoC students to attend and present. We also hold monthly online developer meetings to discuss Octave's direction and future activities, to which GSoC students would be invited. Such meetings strengthen relationships between community members and the new students.


=== Proposal Tags (for applicants to use) (up to 10) ===


Numerical, Infrastructure, Octave Forge, Image analysis, Machine learning, GUI, Graphics, New feature, Performance, Matlab compatibility


=== Contact methods ===


Chat: https://octave.discourse.group/


Mailing list: https://lists.gnu.org/mailman/listinfo/octave-maintainers


General Email: octave-maintainers@gnu.org


Blog: https://planet.octave.org/


[[Category:Summer of Code]]
[[Category:Summer of Code]]
[[Category:2022]]
[[Category:2022]]

Latest revision as of 01:29, 9 February 2022


Octave's application for GSoC 2022.

Organization name[edit]

GNU Octave

OSI approved license?[edit]

Yes

Has your organization participated in Google Summer of Code before?[edit]

Yes

Please select all years in which your organization participated prior to 2022[edit]

2016-2021, 2014

Website URL[edit]

https://www.octave.org

Logo (Must be a 24-bit PNG, minimum height 256 pixels.)[edit]

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 inkscape -z -e octave-logo.png -w 256 -h 256 octave-logo.svg)

Tagline (50 characters)[edit]

Free Your Numbers

Primary License[edit]

GPL 3.0

What year was your project started?[edit]

1992

Source code location[edit]

https://hg.savannah.gnu.org/hgweb/octave


Organization Category[edit]

Programming Languages, Science


Technology Tags (the primary specific technologies your organization uses) (up to 5)[edit]

C++, hg

Topic Tags (general topics that describe your organization) (up to 5)[edit]

mathematics, numerical computation, numerical methods, matlab, scientific computing


Description[edit]

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. 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.


Contributor guidance / Idea List[edit]

https://wiki.octave.org/gsoc

Contact methods[edit]

Chat: https://octave.discourse.group/

Mailing list: https://lists.gnu.org/mailman/listinfo/octave-maintainers

Email: octave-maintainers@gnu.org

Why does your org want to participate in Google Summer of Code? (1000 chars)[edit]

We hope to establish collaborations with talented new contributors. We also want to raise awareness of Octave in the free software community.

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 who have become important 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.

What would your org consider to be a successful summer? (500 chars)[edit]

We would consider a program successful if we selected promising students, provided adequate mentor supervision, developed desired features in Octave, and facilitated a satisfying experience for the students and mentors. We are more interested in the quality of interactions and contributions than in quantity, although, all else being equal, we would be happy to have more talented students join us.




Is your organization part of any government?[edit]

No



How will you keep mentors engaged with their students? (1000 chars)[edit]

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 who are familiar with the code base and with engaging the maintainer and user community. 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? (1000 chars)[edit]

Previous contributions to Octave (which can be small) 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 during the applicant evaluation process. Once a student is selected, the mentors will work with them to come up with a more detailed timeline, including clear expectations for progress by the midterm and final evaluation periods.

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, the vast majority of our over 30 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? (1000 chars)[edit]

Students will be urged to participate in our chat channel and mailing list. We will set clear expectations on the minimum frequency of email progress updates, typically every two to three days. Students will also set up a blog for longer, weekly, updates which will be aggregated at http://planet.octave.org

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. We also hold monthly online developer meetings to discuss Octave's direction and future activities, to which GSoC students would be invited. Such meetings strengthen relationships between community members and the new students.

Retrieved from "https://wiki.octave.org/wiki/index.php?title=GSoC_2022_application&oldid=14195"