Summer of Code - Getting Started: Difference between revisions

Summer of Code - Getting Started (edit)

Revision as of 06:21, 21 January 2021

1,397 bytes removed , 21 January 2021

→‎Things You'll be Expected to Know or Quickly Learn On Your Own: Strip outdated items.

Siko1056

Bureaucrats, Administrators

1,847

edits

@@ Line 35: / Line 35: @@
 *: "I'm good at this, so trust me" isn't enough.  In your proposal, you should describe which algorithms you'll use and how you'll integrate with existing Octave code.  You should also prepare a project timeline and goals for the midterm and final evaluations.
-= Things You'll be Expected to Know or Quickly Learn On Your Own =
+= What you should know about Octave =
-Octave is mostly written in C++ and its own scripting language that is mostly compatible with Matlab. There are bits and pieces of Fortran, Perl, C, awk, and Unix shell scripts here and there. In addition to being familiar with C++ and Octave's scripting language, successful applicants will be familiar with or able to quickly learn about Octave's infrastructure. You can't spend the whole summer learning how to build Octave or prepare a changeset and still successfully complete your project.
+GNU Octave is mostly written in C++ and its own scripting language that is mostly compatible with Matlab. There are bits and pieces of Fortran, Perl, C, awk, and Unix shell scripts here and there. In addition to being familiar with C++ and Octave's scripting language, you as successful applicant will be familiar with or able to quickly learn about Octave's infrastructure. You can't spend the whole summer learning how to build Octave or prepare a changeset and still successfully complete your project 😇
 * '''The Build System'''
@@ Line 53: / Line 53: @@
 *: You will be helping current and future Octave developers by using our standard style for changes, commit messages, and so on.  You should also read the same [[Contribution guidelines | contribution]] [https://hg.savannah.gnu.org/hgweb/octave/file/tip/etc/HACKING.md guidelines] we have for everyone.
 *: [[Hg_instructions_for_mentors#Mercurial_Tips_for_SoC_students | This page]] describes the procedures students are expected to use to publicly display their progress in a public mercurial repo during their work.
-* '''The Maintainers Mailing List'''
-*: We primarily use [https://lists.gnu.org/mailman/listinfo/octave-maintainers mailing lists] for communication among developers.
-*: The mailing list is used most often for discussions about non-trivial changes to Octave, or for setting the direction of development.
-*: You should follow basic mailing list etiquette. For us, this mostly means "do not [https://en.wikipedia.org/wiki/Posting_style#Top-posting top post]".
-* '''The IRC Channel'''
-*: We also have [http://webchat.freenode.net?channels=octave the #octave IRC channel in Freenode].
-*: You should be familiar with the IRC channel.  It's very helpful for new contributors (you) to get immediate feedback on ideas and code.
-*: Unless your primary mentor has a strong preference for some other method of communication, the IRC channel might be your primary means of communicating with your mentor and Octave developers.
-* '''The Octave Forge Project'''
-*: [https://octave.sourceforge.io/ Octave Forge] is a collection of contributed packages that enhance the capabilities of core Octave. They are somewhat analogous to Matlab's toolboxes.
-* '''Related Skills'''
-*: In addition, you probably should know '''some''' mathematics, engineering, experimental science, or something of the sort.
-*: If so, you probably have already been exposed to the kinds of problems that Octave is used for.
 = Suggested projects =