Changes

Jump to navigation Jump to search
717 bytes added ,  17:19, 26 March 2020
→‎About Me: add more contact options
Line 1: Line 1:  
== About Me ==
 
== About Me ==
   −
I am a user, developer, and advocate of GNU Octave. I started using GNU
+
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.
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 Octave are stability and consistency of
+
My main areas of interest within the Octave project are
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.
     −
I am involved in packaging and testing Octave for both the Debian and
+
* developing Octave's nascent [[Python interface]]
Ubuntu distributions. I am a member of the
+
* maintaining the [[Signal package|signal processing]] and [[Communications package|communications]] packages
[http://wiki.debian.org/Teams/DebianOctaveGroup Debian Octave Group] and
+
* maintaining and improving Octave's build system
the [https://launchpad.net/~octave Ubuntu Octave Team].
+
* aiming for stability and consistency of user experience, portability, particularly to different versions of GNU/Linux and Unix
 +
* encouraging new contributors, mentoring, and helping to build community around Octave
   −
I can be found on [https://webchat.freenode.net/?channels=#octave #octave]
+
My primary development environment is Debian GNU/Linux, but I occasionally build and test Octave on other distributions and Unices.
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.
 +
 
 +
You can contact me on [https://webchat.freenode.net/?channels=#octave #octave] as mtmiller, on Matrix as [https://matrix.to/#/@mtmiller:matrix.org @mtmiller:matrix.org], or on Telegram as [https://t.me/mtmiller @mtmiller].
    
My editor of choice is [[VIM|Vim]].
 
My editor of choice is [[VIM|Vim]].
Line 33: Line 29:  
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, or to the Octave core manual.
+
* Apply [[User:Oheim]]'s custom css for the interval package to the communications package 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
 
** Can this be used to run an automatic build of a "nightly" package on Launchpad?
 
** Can this be used to run an automatic build of a "nightly" package on Launchpad?
 
** 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.
 +
* Hi-resolution time using clock_gettime if available instead of gettimeofday.
    
== Octave Work ==
 
== Octave Work ==
Line 55: Line 52:  
* [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://alioth.debian.org/users/mtmiller mtmiller] on Alioth
+
* [https://gitlab.com/mtmiller mtmiller] on GitLab
 +
* [https://salsa.debian.org/mtmiller mtmiller] on Debian Salsa
 
* [https://launchpad.net/~mtmiller mtmiller] on Launchpad
 
* [https://launchpad.net/~mtmiller mtmiller] on Launchpad
296

edits

Navigation menu