Difference between revisions of "User:Mtmiller"

From Octave
Jump to navigation Jump to search
(→‎About Me: update list of projects)
m (→‎External Links: fix URL copy and paste error)
 
(5 intermediate revisions by the same user not shown)
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. I maintain the [[Signal package|signal processing]]
 
and [[Communications package|communications]]
 
packages. I'm also involved in developing Octave's [[Python interface]].
 
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.
 +
 
 +
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 34: 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
Line 43: Line 37:
 
** 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 57: 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

Latest revision as of 12:18, 28 September 2019

About Me[edit]

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.

My main areas of interest within the Octave project are

  • developing Octave's nascent Python interface
  • maintaining the signal processing and communications packages
  • maintaining and improving Octave's build system
  • 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

My primary development environment is Debian GNU/Linux, but I occasionally build and test Octave on other distributions and Unices.

I am involved in packaging and testing Octave for both the Debian and Ubuntu distributions. I am a member of the Debian Octave Group and the 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 #octave as mtmiller.

My editor of choice is Vim.

Octave Project Ideas[edit]

I always have more ideas for projects I would like to work on than I have time for. Please feel free to contact me about any of these ideas, borrow them, work on them, copy them to the projects page, but let me know as a courtesy and in case I have any other thoughts or partial work that might be useful.

  • 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.
  • 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.
  • 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?
    • 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[edit]

See User:Mtmiller/TODO.

External Links[edit]

I work under the following profiles on these development sites. These are all related to work I've done with Octave to some degree.