comparison support.md @ 94:e8fc61e077fc

Merged closed branch "kai" into default.
author Kai T. Ohlhus <k.ohlhus@gmail.com>
date Tue, 01 Nov 2016 01:06:10 +0100
parents 7609e2a6faef
children 25149c27c794
comparison
equal deleted inserted replaced
92:7609e2a6faef 94:e8fc61e077fc
1 --- 1 ---
2 layout: page 2 layout: page
3 title: Support 3 title: Help/Support
4 permalink: /support/
5 menu: true 4 menu: true
6 --- 5 ---
7 6
8 If you need help using Octave, you have many options, from reading the Octave manual, asking for help on the mailing lists, chatting online with other Octave users, or paying for commercial support. 7 If you need help using Octave, you have many options, from reading
8 the Octave manual, asking for help on the mailing lists, chatting
9 online with other Octave users, or paying for [commercial support][1].
9 10
10 <div class="panel callout"> 11 The Octave community is a loosely organized association of
12 volunteers. Your interactions with the community will be better
13 if you have the [right expectations about the support options][2]
14 available to you.
11 15
12 The Octave community is a loosely organized association of volunteers. Your interactions with the community will be better if you have the right expectations about the support options available to you. Please read the <a href="{{ "/support-expectations/" | prepend: site.baseurl }}">Support Expectations</a> page. 16 [1]: {{ "commercial-support.html" | relative_url }}
17 [2]: {{ "support-expectations.html" | relative_url }}
13 18
14 </div>
15 19
16 #### Commercial Support
17 20
18 Community support can be great, and with the Octave community it often is, but sometimes you need to know that your question will be answered. We maintain a [list of people and organizations]({{"/commercial-support/" | prepend: site.baseurl}}) who offer commercial support contracts for Octave. This list is available as a service to the community and the support providers. The Octave project does not provide endorsements or recommendations. 21 # Documentation
19 22
20 #### User Community 23 There is an [{% octicon book class:"octicon-book-manual" %} Online Manual][3]
24 and a [{% octicon file-pdf class:"octicon-pdf-manual" %} PDF Version][4] of
25 the comprehensive ~800 page manual. This full documentation of Octave is
26 generated directly from the Texinfo source files that are distributed along
27 with every copy of the Octave source code. The complete text of the manual
28 is also available at the Octave prompt using the `doc` command.
21 29
22 There is an active user community centered around Octave. Please understand that the people answering your question on the mailing list or IRC channel, or helping to fix the bug you reported are doing so as volunteers. 30 A printed version of the Octave manual may be ordered from
31 [Network Theory, Ltd.][5]. Any money raised from the sale of this book
32 will support the development of free software. For each copy sold $1
33 will be donated to the GNU Octave Development Fund.
23 34
24 ### Documentation 35 [3]: {{ site.docs_url }}
36 [4]: http://www.octave.org/octave.pdf
37 [5]: http://www.network-theory.co.uk/octave/manual
25 38
26 #### Reference Manual
27 39
28 Octave is fully documented by a comprehensive 800 page [manual]({{site.docs_url}}). 40 # Octave Wiki and FAQ
29 41
30 The on-line [HTML](http://www.gnu.org/software/octave/doc/interpreter/index.html) and [PDF](http://www.gnu.org/software/octave/octave.pdf) versions of the manual are generated directly from the Texinfo source files that are distributed along with every copy of the Octave source code. The complete text of the manual is also available at the Octave prompt using the doc command. 42 The [Octave Wiki][6] is a great place to look for information about
43 things that are not covered in the manual, or other transient topics
44 (Google Summer of Code, Octave Conferences, etc.).
31 45
32 A printed version of the Octave manual may be ordered from [Network Theory, Ltd](http://www.network-theory.co.uk/octave/manual). Any money raised from the sale of this book will support the development of free software. For each copy sold $1 will be donated to the GNU Octave Development Fund. 46 Additionally, the wiki contains a list of
47 [frequently asked questions (FAQ)][7]
33 48
34 #### Frequently Asked Questions 49 [6]: {{ site.wiki_url }}
50 [7]: {{ site.faq_url }}
35 51
36 If you are new to Octave, you may have some questions that have been asked (and answered) a few times before. See the [FAQ](http://www.octave.org/wiki/FAQ) on the wiki.
37 52
38 #### Wiki 53 # Contacting the user community
39 54
40 The Octave Wiki is a great place to look for information about things that are not covered in the manual, or other transient topics (Google Summer of Code, Octave Conferences, etc.). 55 - **Mailing List**:
56 If your question isn't answered in the FAQ, the manual, or the Wiki,
57 the [**`{{ site.help_email }}`**][8] mailing list is a good resource.
41 58
42 ### Contacting Other Users for Help 59 You can also [subscribe][9] to `{{ site.help_email }}` or try to search in the
60 mailing list archive for an answer:
61 <form action="http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp">
62 <input type="hidden" name="macro" value="search_page" />
63 <input type="hidden" name="node" value="1599825" />
64 <input id="query" name="query" size="25" />
65 <select name="days">
66 <option value="0" selected>all dates</option>
67 <option value="1">past 24 hours</option>
68 <option value="7">past week</option>
69 <option value="30">past month</option>
70 <option value="90">past 3 months</option>
71 <option value="180">past 6 months</option>
72 <option value="365">past year</option>
73 </select>
74 <input type="submit" value="Search" />
75 </form>
43 76
44 #### Mailing List
45 77
46 If your question isn't answered in the FAQ, the manual, or the Wiki, the [help@octave.org](https://lists.gnu.org/mailman/listinfo/help-octave) mailing list is a good resource. 78 <p>
79 <div class="alert">
80 {% octicon stop class:"octicon-stop-octave" %}
81 Please do <strong>not</strong> send any bug reports to the
82 <samp>{{ site.help_email }}</samp> mailing list.
83 Most Octave users do not want to receive bug reports.
84 </div>
85 </p>
47 86
48 <div class="row"> 87 - **IRC Chat**:
49 <div class="columns medium-8"> 88 Too impatient for email? You can find Octave developers and users on the
50 <form action="http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp"><input name="macro" value="search_page" type="hidden"> 89 [`{{ site.irc_channel }}` channel][10] at [`{{ site.irc_network }}`][11].
51 <input name="node" value="1599825" type="hidden"> 90 The atmosphere is relaxed and chat isn't restricted to matters strictly
52 <div class="row collapse"> 91 pertaining to Octave.
53 <div class="columns small-7">
54 <input id="query" name="query" size="25">
55 </div>
56 <div class="columns small-3">
57 <select name="days">
58 <option value="0" selected="">all dates</option>
59 <option value="1">past 24 hours</option>
60 <option value="7">past week</option>
61 <option value="30">past month</option>
62 <option value="90">past 3 months</option>
63 <option value="180">past 6 months</option>
64 <option value="365">past year</option>
65 </select>
66 </div>
67 <div class="columns small-2">
68 <input class="button postfix" value="Search" type="submit">
69 </div>
70 </div>
71 92
72 </form> 93 [8]: mailto:{{ site.help_email }}
73 </div> 94 [9]: https://lists.gnu.org/mailman/listinfo/help-octave
74 </div> 95 [10]: http://webchat.freenode.net/?channels=octave&amp;uio=MT1mYWxzZSYyPXRydWUmMTI9dHJ1ZQda
75 96 [11]: http://freenode.net
76 [Advanced Search](http://octave.1599824.n4.nabble.com/template/NamlServlet.jtp?macro=adv_search_page&node=1599825)
77
78 #### Chat
79
80 Too impatient for email? You can find Octave developers and users on the [#octave channel at irc.freenode.net](http://webchat.freenode.net/?channels=octave&uio=MT1mYWxzZSYyPXRydWUmMTI9dHJ1ZQda). The atmosphere is relaxed and chat isn't restricted to matters strictly pertaining to Octave.
81
82 ### Reporting Bugs
83
84 If you think you've found a bug, you are encouraged to [report it]({{ "/bugs/" | prepend: site.baseurl }}).