|
|
| Line 507: |
Line 507: |
| This is one of those times where the best documentation is to read the existing code. We have three different toolkits in Octave now, so there are some examples to draw from. | | This is one of those times where the best documentation is to read the existing code. We have three different toolkits in Octave now, so there are some examples to draw from. |
|
| |
|
| =Development= | | = Development = |
|
| |
|
| ==When will feature X be released or implemented?== | | == When will feature X be released or implemented? == |
|
| |
|
| When it's ready, sooner [http://www.octave.org/get-involved.html if you help]. You can [https://savannah.gnu.org/patch/?group=octave send us patches] if you can implement feature X yourself. If you can't, some [http://www.octave.org/commercial-support.html developers may be convinced to work on your specific problem for some money]. | | When it's ready, sooner [https://www.octave.org/get-involved.html if you help]. You can [https://savannah.gnu.org/patch/?group=octave send us patches] if you can implement feature X yourself. If you can't, some [https://www.octave.org/commercial-support.html developers may be convinced to work on your specific problem for some money]. |
|
| |
|
| ==How can I get involved in Octave development?== | | == How can I get involved in Octave development? == |
|
| |
|
| Be around. Be social. Participate in our mailing lists [https://lists.gnu.org/mailman/listinfo/help-octave help@octave.org] and [https://lists.gnu.org/mailman/listinfo/octave-maintainers maintainers@octave.org]. Find things about Octave you don't like, and start thinking about how to fix them. Many people who now contribute to Octave first spent several years helping in the mailing list before they started to delve into 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.
| | :''See [[Developer FAQ]]''. |
| | |
| If you feel ready to dive right into the code, read the [[Developers]] wiki page or [http://www.octave.org/get-involved.html start here]. But do not send an email to the mailing lists listing your 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. If there is a specific short-term project you would like to work on, say so, and just 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 [http://www.octave.org/doc/interpreter/ manual]. These are also important tasks. The documentation is easy to patch, and the help text for individual functions even more so. Editing this wiki is even easier.
| |
| | |
| Accurate bug reporting is also very useful. Find and report [http://bugs.octave.org/ 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 the [https://lists.gnu.org/mailman/listinfo/octave-bug-tracker 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]], [[short projects]], and [[Summer of Code - Getting Started]] if you need specific inspiration for coding tasks that we would like to get done.
| |
|
| |
|
| [[Category:FAQ]] | | [[Category:FAQ]] |