Editing User:Mtmiller

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 save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
== About Me ==
 
== About Me ==
  
I am a user, developer, and advocate of GNU Octave. I started using Octave around May 2007 while working on my MSEE. I started submitting bugs and patches against Octave in February 2012, mainly to fix some compilation problems I had with the latest release on an older Red Hat Enterprise 5 system I used at work. One thing led to another and I am now a co-maintainer of the Octave project, frequent contributor to both development and discussion, bug triager, tester, etc.
+
I am a user, developer, and advocate of GNU Octave. I started using GNU
 +
Octave around May 2007 while working on my MSEE. I started submitting
 +
bugs and working on Octave in February 2012, mainly to fix some
 +
compilation problems I had with the newest version on an older Red Hat
 +
Enterprise 5.2 system I use at work. One thing led to another and I am
 +
now learning my way around the code base, helping to fix bugs, test,
 +
etc.
  
My main areas of interest within the Octave project are
+
My main areas of interest within Octave are stability and consistency of
 +
user experience, portability, particularly to different versions of
 +
GNU/Linux and Unix, and the [[Signal package|signal processing]]
 +
and [[Communications package|communications]]
 +
packages. My primary development environment is Debian GNU/Linux.
  
* developing Octave's nascent [[Python interface]]
+
I am involved in packaging and testing Octave for both the Debian and
* maintaining the [[Signal package|signal processing]] and [[Communications package|communications]] packages
+
Ubuntu distributions. I am a member of the
* maintaining and improving Octave's build system
+
[http://wiki.debian.org/Teams/DebianOctaveGroup Debian Octave Group] and
* aiming for stability and consistency of user experience, portability, particularly to different versions of GNU/Linux and Unix
+
the [https://launchpad.net/~octave Ubuntu Octave Team].
* encouraging new contributors, mentoring, and helping to build community around Octave
 
  
My primary development environment is Debian GNU/Linux, but I occasionally build and test Octave on other distributions and Unices.
+
I can be found on [https://webchat.freenode.net/?channels=#octave #octave]
 
+
as mtmx.
I am involved in packaging and testing Octave for both the Debian and Ubuntu distributions. I am a member of the [http://wiki.debian.org/Teams/DebianOctaveGroup Debian Octave Group] and the [https://launchpad.net/~octave Ubuntu Octave Team].
 
 
 
I have been a mentor for two very successful projects under the Google Summer of Code program.
 
 
 
I can be found on [https://webchat.freenode.net/?channels=#octave #octave] as mtmiller.
 
  
 
My editor of choice is [[VIM|Vim]].
 
My editor of choice is [[VIM|Vim]].
Line 29: Line 33:
 
might be useful.
 
might be useful.
  
 +
* Update the default oct-file template in edit.m to reflect current best practices and recommended coding style.
 
* Create a complete Vim environment with [[User:Rik]]'s syntax highlighting rules, indenting, if-end keyword matching, function block jumping, etc.
 
* Create a complete Vim environment with [[User:Rik]]'s syntax highlighting rules, indenting, if-end keyword matching, function block jumping, etc.
 
* Update pygments syntax highlighting for Octave if needed.
 
* Update pygments syntax highlighting for Octave if needed.
* Apply [[User:Oheim]]'s custom css for the interval package to the communications package manual.
+
* Apply [[User:Oheim]]'s custom css for the interval package to the communications package manual, or to the Octave core manual.
 
* Make a static m-file format/style analyzer, a la pep8, that can help users teach themselves GNU Octave style conventions.
 
* Make a static m-file format/style analyzer, a la pep8, that can help users teach themselves GNU Octave style conventions.
 
* Adapt Debian packaging to operate on a clean hg clone, add build-deps (bison, flex, gperf), build package from any hg revision
 
* Adapt Debian packaging to operate on a clean hg clone, add build-deps (bison, flex, gperf), build package from any hg revision
Line 37: Line 42:
 
** Should any of this be applied to the official Debian packaging?
 
** Should any of this be applied to the official Debian packaging?
 
* Query the terminal size directly from the terminal instead of readline as a fallback. Also allow COLUMNS and LINES to override terminal size.
 
* Query the terminal size directly from the terminal instead of readline as a fallback. Also allow COLUMNS and LINES to override terminal size.
* Hi-resolution time using clock_gettime if available instead of gettimeofday.
 
  
 
== Octave Work ==
 
== Octave Work ==
Line 52: Line 56:
 
* [https://bitbucket.org/mtmiller mtmiller] on Bitbucket
 
* [https://bitbucket.org/mtmiller mtmiller] on Bitbucket
 
* [https://github.com/mtmiller mtmiller] on GitHub
 
* [https://github.com/mtmiller mtmiller] on GitHub
* [https://gitlab.com/mtmiller mtmiller] on GitLab
+
* [https://alioth.debian.org/users/mtmiller mtmiller] on Alioth
* [https://salsa.debian.org/mtmiller mtmiller] on Debian Salsa
 
 
* [https://launchpad.net/~mtmiller mtmiller] on Launchpad
 
* [https://launchpad.net/~mtmiller mtmiller] on Launchpad

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)