Editing OctConf TODO

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
* Should we have this meeting annually?
* Rename core dump to workspace save
*:Yes
* Enable warnings locally?
** Where should it be?
* More demos in documentation (code sprint?)
**:europe. In 3--4 months europeans will start talking to each other and in 6 months have decided where.
* More help on readline
** Can we get sufficient funding for travel and meeting space?
* '''DONE''' Enable warnings locally? What does this mean? [jwe]
*:function calls may want to change and we want to do this locally without having to use unwind statements. KaKiLa suggested to do this.
* More demos in documentation (code sprint?). Copy @example into demo blocks and some %!test blocks into the documentation?
*:not all should tests should be moved to demos. No examples may be better than too many.
* More help on readline [Jordi]
*:Jordi suggested to write this though it's not clear yet where to put in a way for users to find it easily
* Storage of debug control in the terminal (anything to do there or just use history_control)? GUI doesn't store them.
* Storage of debug control in the terminal (anything to do there or just use history_control)? GUI doesn't store them.
*:should we do like matlab and collapse multiple calls to same command into one. readline can already avoid duplicates but we want to keep it because order of commands is important.
* How to clear functions defined in the interpreter (or script file)?
* '''DONE''' How to clear functions defined in the interpreter (or script file)? [max]
* Copy @example into demo blocks and some @test into the documentation.
*:Max already has an idea where this is and will take a look and there's is a coment on code about this
* Add to the wiki short itemized list of steps and tools for [[debugging Octave]] (gdb,emacs, anjuta?, ddd?).
*: already done
*:only developers care about this. However, this will make easier for non-developers to become developers too
* '''DONE''' Move non-DLD functions out of DLD-FUNCTIONS directory.  Change to DEFUN blocks and move to new directory
*: many of this functions are only dependent on liboctave. This used to be to save memory. jwe suggested to do this and no one opposed. This will make it slightly faster now.
* '''IN PROGRESS''' Change comment string in DEFUN blocks from double-quoted string to C++ comment string to get rid of excessive backslashing. [jwe, Rik?]
*:is it worth the effort? Pending investigation and how much work this will really do, this seems like a goood thing.
* Audit FIXME tags in code?
*: talk about this on roadmap. Where do we want to go? Cleaning code, implementing new stuff, etc... Currently there's 1378 FIXME tags on core
* Should Octave prompt when displaying large matrices or other objects?
*: should we ask the user before displaying large things? Most of the times is due to a forgotten ; and no one is going too look at them and it takes a few seconds to show them.
* Should the Octave project distribute "official" binaries for Windows and OS X?
*: consensus is the project to distribute them. Seems we decided to not sell them but to have a pay what you want option. Shall not be a pay for support by the project since it complicates how to distribute the money after. Instead, a page on octave with list of people willing to be paid to give support (jwe welcomes people to add their names and contacts there).
** Who will build them?
** Should we sell them?
* Should we have a list of release goals for the next few releases on the web (wiki)?
*:might be better to have a static page. We don't everyone being able to edit this. This is not a contract.
* create some kind of octave newsletter.
*: every couple of months, send a news, teasers with news. This could get an idea of how many people care about the project.
* socialize project
*: use Google+, twitter, and the like of them. rms is not going to like this and will object for a GNU project to use this. We could use things like identi.ca but only 5 people will see it. There's in an octave facebook page but was created automatically from wikipedia and is dead. Can't be official, and jwe is not against it but it's semi-official, done a by a single person. May announce things from planet octave. No one opposed.
* find professors for numerical analysis
*: go to universities and find people that could be using octave. Machine learning course is using octave but they don't communicate with us.
* who uses octave
:* we need this list, something like a showcase. Companies don't want to be the only ones using it. The more we have, the easier to make people believe that octave really is good.
 
[[Category:OctConf]]
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)
Retrieved from "https://wiki.octave.org/OctConf_TODO"