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