153
edits
Summer of Code - Getting Started: Difference between revisions
Jump to navigation
Jump to search
m
→Suggested projects: really fixed the link this time
Pr0m1th3as (talk | contribs) (→Suggested projects: added project) Tags: Mobile edit Mobile web edit Advanced mobile edit |
m (→Suggested projects: really fixed the link this time) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
# 😉💬 '''We want to get to know you (before the deadline). Communicate with us.''' | # 😉💬 '''We want to get to know you (before the deadline). Communicate with us.''' | ||
#* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]]. Using a nickname is fine. | #* Join [https://octave.discourse.group/ '''Octave Discourse'''] or [[IRC]] for general discussion and to ask questions (Please do not use the bug tracker for general GSOC inquiries unrelated to specific bugs found with Octave.) Using a nickname is fine. | ||
#* Show us that you're motivated to work on Octave 💻. There is no need to present an overwhelming CV 🏆; evidence of involvement with Octave is more important. | #* Show us that you're motivated to work on Octave 💻. There is no need to present an overwhelming CV 🏆; evidence of involvement with Octave is more important. | ||
#* '''<span style="color:darkblue;">If you never talked to us, we will likely reject your proposal</span>''', even it looks good 🚮 | #* '''<span style="color:darkblue;">If you never talked to us, we will likely reject your proposal</span>''', even it looks good 🚮 | ||
| Line 58: | Line 58: | ||
The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC participants. You can also look at our [[Summer of Code|completed past projects]] for more inspiration. | The following suggested projects are distilled from the [[Projects]] page for the benefit of potential SoC participants. You can also look at our [[Summer of Code|completed past projects]] for more inspiration. | ||
{{Note|Do you use Octave at your working place or university? Do you have some numerical project in mind? You are always welcome to '''propose your own projects'''. If you are passionate about your project, it will be easy to find an Octave developer to mentor and guide you.}} | {{Note|Do you use Octave at your working place or university? Do you have some numerical project in mind? You are always welcome to '''propose your own projects'''. If you are passionate about your project, it will be easy to find an Octave developer to mentor and guide you. Please note that for such a proposal to be successful it will almost certainly involve initiating pre-proposal discussion over at the [https://octave.discourse.group Octave Discourse forum].}} | ||
== Adding regression GAM and kNN classification functionality in statistics package == | == Adding regression GAM and kNN classification functionality in statistics package == | ||
| Line 81: | Line 81: | ||
* '''Required skills''' | * '''Required skills''' | ||
: Perl, Octave, Texinfo, HTML | : Perl, Octave, Texinfo, HTML | ||
* '''Potential mentors''' | |||
: [https://octave.discourse.group/u/pr0m1th3as Andreas Bertsatos] | |||
== A function search index website for all Octave Packages == | |||
Develop additional functionality for the pkg-octave-doc package than will search all pkg compatible packages listed in Octave Packages, enumerate the available functions from each package, and built a website with search capability that will list all functions’ names and their respective package(s). The function list should have links corresponding to their documentation or/and source code. This could be integrated in the current Octave Packages website and the implemented tool can be part of the current CI (used for testing a package before merging a new release) and automatically update the website with every package release. Alternatively, it can be a stand alone service which will monitor Octave Packages repository for any merged PR and update the function search index website accordingly. | |||
* '''Project size''' [[#Project sizes | [?]]] and '''Difficulty''' | |||
: ~350 hours (medium) | |||
* '''Required skills''' | |||
: Octave, Bootstap 5 framework | |||
* '''Potential mentors''' | * '''Potential mentors''' | ||
: [https://octave.discourse.group/u/pr0m1th3as Andreas Bertsatos] | : [https://octave.discourse.group/u/pr0m1th3as Andreas Bertsatos] | ||
| Line 103: | Line 114: | ||
== PolarAxes and Plotting Improvements == | == PolarAxes and Plotting Improvements == | ||
Octave currently provides | Octave currently provides support for polar axes by using a Cartesian 2-D axes and adding a significant number of properties and callback listeners to get things to work. What is needed is the implementation of a dedicated "polaraxes" object in C++. This will require creating a new fundamental graphics object type, and programming in C++/OpenGL to render the object. When "polaraxes" exists as an object type, then m-files will be written to access them, including polaraxes.m, polarplot.m, rticks.m, rticklabels.m, thetaticks, thetaticklabels.m, rlim.m, thetalim.m. This relates to bug {{bug|49804}}. | ||
* '''Project size''' [[#Project sizes | [?]]] and '''Difficulty''' | * '''Project size''' [[#Project sizes | [?]]] and '''Difficulty''' | ||