FAQ: Difference between revisions

14 bytes added ,  9 July 2015
m
→‎How can I get involved in Octave development?: if paragraph is too long for meaningful diff, break by sentences, not at 80 char columns.
(→‎How do I make Octave use more precision?: remove note about symbolic being useless. It's currently working fine via sympy)
m (→‎How can I get involved in Octave development?: if paragraph is too long for meaningful diff, break by sentences, not at 80 char columns.)
Line 120: Line 120:
==How can I get involved in Octave development?==
==How can I get involved in Octave development?==


Be around. Be social. Participate in the [https://mailman.cae.wisc.edu/listinfo/help-octave help]
Be around. Be social. Participate in the [https://mailman.cae.wisc.edu/listinfo/help-octave help] and [https://mailman.cae.wisc.edu/listinfo/octave-maintainers maintainers] mailing lists.   
and [https://mailman.cae.wisc.edu/listinfo/octave-maintainers maintainers]
Find things about Octave you don't like, and start thinking about how to fix them.  
mailing lists.  Find things about Octave you don't like, and start thinking
Many people who now contribute to Octave first spent several years helping in the mailing list before they started to delve into
about how to fix them. Many people who now contribute to Octave first spent
the code.  
several years helping in the mailing list before they started to delve into
A good way to learn Octave is to understand the problems other people are having with it, so being helpful in the mailing lists not only helps Octave as a whole, but it also prepares you to be a better Octave contributor.
the code. A good way to learn Octave is to understand the problems other
people are having with it, so being helpful in the mailing lists not only
helps Octave as a whole, but it also prepares you to be a better Octave
contributor.


If you feel ready to dive right into the code, read [[Hacking | here]]
If you feel ready to dive right into the code, read [[Hacking | here]] and [http://www.gnu.org/software/octave/get-involved.html here] for guidance.   
and [http://www.gnu.org/software/octave/get-involved.html here] for
But do not send an email to the mailing lists listing your skills and offering to help.   
guidance.  But do not send an email to the mailing lists listing your
We won't just suggest things for you to do.
skills and offering to help.  We won't just suggest things for you to do.
We lack volunteers and we do need your help, but because of that, we also lack the time to provide good guidance and mentoring.   
We lack volunteers and we do need your help, but because of that, we also
If there is a specific short-term project you would like to work on, say so, and just do it.   
lack the time to provide good guidance and mentoring.  If there is a
Then ask for help or advice when you're doing it.   
specific short-term project you would like to work on, say so, and just
It is a lot more important that you do something that you're actually interested on than something we suggested because it only matches your skills.
do it.  Then ask for help or advice when you're doing it.  It is a lot
more important that you do something that you're actually interested on
than something we suggested because it only matches your skills.


We also need help with this wiki and the
We also need help with this wiki and the [http://www.gnu.org/software/octave/doc/interpreter/ manual].  
[http://www.gnu.org/software/octave/doc/interpreter/ manual]. These are
These are also important tasks.  
also important tasks. The documentation is easy to patch, and the help text
The documentation is easy to patch, and the help text for individual functions even more so.  
for individual functions even more so. Editing this wiki is even easier.
Editing this wiki is even easier.
Accurate bug reporting is also very useful.
Find and report [http://www.gnu.org/software/octave/bugs.html bugs], making an attempt to diagnose them.
Eventually, you will also know how to fix them.
If you want to help with bug reports or patches, subscribe to [https://savannah.gnu.org/mail/?group=octave the bug tracker mailing list].
You'll get updates on all bug activity, and you can jump in when you see something you can help with.


Accurate bug reporting is also very useful. Find and report
Look at our [[Projects]] and [[Summer of Code Project Ideas]] if you need specific inspiration for coding tasks that we would like to get done.  
[http://www.gnu.org/software/octave/bugs.html bugs], making an attempt to
See also the list of [[short projects]].
diagnose them. Eventually, you will also know how to fix them. If you want
to help with bug reports or patches, subscribe to
[https://savannah.gnu.org/mail/?group=octave the bug tracker mailing list].
You'll get updates on all bug activity, and you can jump in when you see
something you can help with.
 
Look at our [[Projects]] and [[Summer of Code Project Ideas]] if you need
specific inspiration for coding tasks that we would like to get done. See
also the list of [[short projects]].


=Licensing issues=
=Licensing issues=
115

edits