OctConf 2012 will bring together users and developers for five days in the French Canadian summer.
Please email Jordi (email@example.com) with your estimated travel costs if you think you could attend. Also write your name below in the Participants section if you think of attending with high probability.
Montréal, Québec, Canada
Montréal is lively city with English and French widely spoken plus many other minority languages. Most business can be conducted in either language. It has four large universities, two Anglophones, McGill, Concordia; and two Francophones: Université du Québec à Montréal (UQAM), and Université de Montréal. The Centre de Recherches Mathématiques (CRM) is a mathematical centre that brings together researchers from all four universities and many others from Montréal and Canada.
The Montréal summer can be quite hot and humid with some chance of rain. The city has a very serviceable public transportation network of buses and underground trains (metro), so it is convenient to get around without renting a car.
The CRM will be offering its Université de Montréal facilities for the conference. There is an eponymous metro station that reaches the university.
July 16-20, 2012. First two days are intended for newbies and casual users, who may possibly be interested in getting involved in development. Next three days are for code sprints and development. Participants are encouraged to attend for all 5 days, but may choose only the first two or last three as convenient.
Introductions, "What is Octave?" talk for a general audience (advertise this a lot in the local scientific computing and engineering communities). Helping with Octave installations, presentations about basic Octave use.
More advanced Octave use, including calling Octave from C++ code. Minimum C++ knowledge necessary expounded. How to work with development tools (reading the Octave source code, using Mercurial, bug and patch trackers, mailing lists, IRC).
Social event during evening.
State-of-the-Octave address. Identify problems to work on, pair off and start working on those problems. Code sprints.
Reports of results of the previous day. Tech talks if necessary. More code sprints.
Reports. Last code sprint. Farewells.
Suggestions for Sessions
Clean up Bugs
Code sprint to clean up the bug tracker. This would include identifying and closing duplicates, as well as re-qualifying "bugs" that represent feature requests, and closing reports that aren't actually bugs.
Cross-platform FLTK Bugs
Developers using Linux, MacOS, and Windows cooperate to fix FLTK bugs. This represents an important effort toward changing the default backend from gnuplot to FLTK. See bugs #31518, #31976, #32134, #32276, #34720.
- Jordi Gutiérrez Hermoso
- Joanna Cheng (pending funding and leave)
- Juan Pablo Carbajal (pending funding).
- Carnë Draug
- Ben Abbott (possible scheduling conflict)
There may be limited funding to cover the travel expenses of selected participants.