User:Mtmiller: Difference between revisions
(→About Me: add community and mentoring contributions) |
(→About Me: add more contact options) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
I have been a mentor for two very successful projects under the Google Summer of Code program. | 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 29: | Line 29: | ||
might be useful. | might be useful. | ||
* 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 | * 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 38: | 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 52: | 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:// | * [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 17:19, 26 March 2020
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.
You can contact me on #octave as mtmiller, on Matrix as @mtmiller:matrix.org, or on Telegram 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.