Mercurial > web-octave

comparison support-expectations.md @ 49:d01bb705165e kai

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Markdownify pages.
author Kai T. Ohlhus <k.ohlhus@gmail.com>
date Wed, 28 Sep 2016 11:29:58 +0200
parents 171ca967fcc9
children d1b6335e9c5d
comparison
equal deleted inserted replaced
48:aa0c5c467963 49:d01bb705165e
1 --- 1 ---
2 layout: default 2 layout: default
3 title: Support Expectations 3 title: Support Expectations
4 permalink: /support-expectations/
5 menu: false 4 menu: false
6 --- 5 ---
7 6
8 <p> 7 Octave is a capable free software system for numerical computing
9 Octave is a capable free software system for numerical computing 8 developed primarily by a community of volunteers. As good as it
10 developed primarily by a community of volunteers. As good as it 9 is, there are certainly some flaws and a lot of room for
11 is, there are certainly some flaws and a lot of room for 10 improvement. Most people who use Octave understand these things
12 improvement. Most people who use Octave understand these things 11 and know that if they work together with the community bugs will
13 and know that if they work together with the community bugs will 12 be fixed, features will be added, and Octave will improve over
14 be fixed, features will be added, and Octave will improve over 13 time. Working with people who have this kind of attitude is fun
15 time. Working with people who have this kind of attitude is fun 14 and rewarding.
16 and rewarding.
17 </p>
18 15
19 <p> 16 Unfortunately, there are a few people who behave as though the
20 Unfortunately, there are a few people who behave as though the 17 community owes them support as well as a 100% Matlab compatible
21 community owes them support as well as a 100% Matlab compatible 18 system, all at zero cost. It shouldn't really be necessary, but
22 system, all at zero cost. It shouldn't really be necessary, but 19 we'll say it anyway: working with these people is no fun. If you
23 we'll say it anyway: working with these people is no fun. If you 20 approach the Octave community this way, you are sure to be
24 approach the Octave community this way, you are sure to be 21 disappointed. You should also not be surprised when your requests
25 disappointed. You should also not be surprised when your requests 22 for help are ignored.
26 for help are ignored.
27 </p>
28 23
29 <h1>Development Group</h1>
30 <p>
31 People sometimes think that Octave is developed by some
32 large team of well-paid programmers. Nothing could be further
33 from the truth. Most of the initial development of Octave was
34 done by one person over several years. Since then, there have
35 been at most a half-dozen or so volunteers working on Octave at
36 any one time. You can see who has done most of the work by
37 looking through
38 the <a href="http://hg.savannah.gnu.org/hgweb/octave">development
39 history</a> (prior to February 2008 it is best to look in the
40 old <tt>ChangeLog</tt> files). Currently, none of the Octave
41 developers are paid to work on Octave directly.
42 </p>
43 24
44 <p> 25 ## Development Group
45 If you would like to see Octave moving forward more quickly, then
46 contribute to its development, either by working on the project
47 yourself, or by donating funds. With sufficient funding, we would
48 be able to pay a few developers to work on Octave full time.
49 </p>
50 26
51 <h1>Help</h1> 27 People sometimes think that Octave is developed by some large team
52 <p> 28 of well-paid programmers. Nothing could be further from the truth.
53 When asking for help on the mailing list or IRC channel, or 29 Most of the initial development of Octave was done by one person
54 reporting a bug, remember that the people helping you are Octave 30 over several years. Since then, there have been at most a half-dozen
55 users just like you who are volunteering their time. They are not 31 or so volunteers working on Octave at any one time.
56 paid support staff. Use meaningful subject lines. Try to ask 32 You can see who has done most of the work by looking through the
57 clear questions. Be precise about the problems you are having. 33 [development history](http://hg.savannah.gnu.org/hgweb/octave)
58 </p> 34 (prior to February 2008 it is best to look in the old `ChangeLog` files).
35 Currently, none of the Octave developers are paid to work on Octave directly.
59 36
60 <h1>Bugs</h1> 37 If you would like to see Octave moving forward more quickly, then
61 <p> 38 contribute to its development, either by working on the project
62 No software is perfect, and Octave is no exception. You can 39 yourself, or by donating funds. With sufficient funding, we would
63 search the list of bug reports to see what problems have been 40 be able to pay a few developers to work on Octave full time.
64 reported. In looking at the list, you might also noticed the
65 number of problems that have been <emph>fixed</emph>. Nearly all
66 of these problems have been fixed by volunteers. If you find a
67 problem, you are encouraged
68 to <a href="bugs.html">report it</a>. Your report can help to
69 improve Octave, but you should not think of the bug tracker as
70 your personal support line.
71 </p>
72 <p>
73 If you depend on Octave and absolutely must have prompt responses
74 to problem reports, you should consider paying
75 for <a href="commercial-support.html">commercial support</a>.
76 </p>
77 41
78 <h1>Features</h1>
79 <p>
80 When we say that Octave is "mostly compatible" with Matlab, we
81 mean that the language that it accepts is similar enough that a
82 substantial amount of code written for Matlab can also run in
83 Octave without needing to be changed. But Octave does not have
84 all the features of Matlab, and it is unlikely that it ever will.
85 Given that Matlab is developed in secret and Octave developers
86 only find out about new Matlab features when new versions of
87 Matlab are released, it is clearly impossible for Octave to have
88 new Matlab features as soon as they are available in Matlab.
89 </p>
90 <p>
91 In most cases, Octave has the features that it does because
92 someone decided to add them becuase they needed them. If you have
93 the programming skills perhaps you can add the features you need.
94 If you not, then consider paying for someone to implement the
95 feature for you. Most people who
96 provide <a href="commercial-support.html">commercial support</a>
97 services for Octave will also take on custom programming projets.
98 </p>
99 <p>
100 Even if you don't have the expertise required to implement new
101 features or can't pay for someone to do the work for you, you may
102 submit feature requests to the bug tracker. But you should
103 understand that unless you are paying for someone to to add the
104 feature, no one is obligated to do it for you.
105 </p>
106 42
107 <h1>Releases</h1> 43 ## Help
108 <p> 44
109 The Octave project currently provides source releases only. We 45 When asking for help on the mailing list or IRC channel,
110 simply don't have the volunteer resources to provide executable 46 or reporting a bug, remember that the people helping you
111 versions of Octave packaged for different types of systems. If 47 are Octave users just like you who are volunteering their time.
112 you'd like to see this situation change, volunteer to help us, or 48 They are not paid support staff. Use meaningful subject lines.
113 donate to the project so that an Octave developer can spend the 49 Try to ask clear questions. Be precise about the problems you are having.
114 time needed to do the job. 50
115 </p> 51
52 ## Bugs
53
54 No software is perfect, and Octave is no exception.
55 You can search the list of bug reports to see what
56 problems have been reported. In looking at the list,
57 you might also noticed the number of problems that have been *fixed*.
58 Nearly all of these problems have been fixed by volunteers.
59 If you find a problem, you are encouraged to
60 [report it]({{ "/bugs.html" | prepend: site.baseurl }}).
61 Your report can help to improve Octave,
62 but you should not think of the bug tracker as your personal support line.
63
64 If you depend on Octave and absolutely must have prompt responses
65 to problem reports, you should consider paying
66 for [commercial support][].
67
68
69 ## Features
70
71 When we say that Octave is "mostly compatible" with Matlab,
72 we mean that the language that it accepts is similar enough that a
73 substantial amount of code written for Matlab can also run in
74 Octave without needing to be changed. But Octave does not have
75 all the features of Matlab, and it is unlikely that it ever will.
76 Given that Matlab is developed in secret and Octave developers
77 only find out about new Matlab features when new versions of
78 Matlab are released, it is clearly impossible for Octave to have
79 new Matlab features as soon as they are available in Matlab.
80
81
82 In most cases, Octave has the features that it does because
83 someone decided to add them becuase they needed them. If you have
84 the programming skills perhaps you can add the features you need.
85 If you not, then consider paying for someone to implement the
86 feature for you. Most people who provide [commercial support][]
87 services for Octave will also take on custom programming projets.
88
89
90 Even if you don't have the expertise required to implement new
91 features or can't pay for someone to do the work for you, you may
92 submit feature requests to the bug tracker. But you should
93 understand that unless you are paying for someone to to add the
94 feature, no one is obligated to do it for you.
95
96
97 ## Releases
98
99 The Octave project currently provides source releases only.
100 We simply don't have the volunteer resources to provide executable
101 versions of Octave packaged for different types of systems.
102 If you'd like to see this situation change, volunteer to help us,
103 or donate to the project so that an Octave developer can spend the
104 time needed to do the job.
105
106 [commercial support]: {{ "/commercial-support.html" | prepend: site.baseurl }}