OctConf 2012

OctConf 2012 will bring together users and developers for five days in July in the French Canadian summer.

Please email Jordi (jordigh@octave.org) 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.

Location

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.

Venue

The CRM will be offering its Université de Montréal facilities for the conference. There is an eponymous metro station that reaches the university.

How to get there

Until the right pavilion is assigned, the reference street address is:

Centre de recherches mathématiques
Université de Montréal
Pavillon André-Aisenstadt
2920 Chemin de la tour, room 5357
Montréal (Québec)
H3T 1J4

Take your flight to the Montréal-Pierre Elliott Trudeau International Airport.

Lodging

There are several hotels and cheaper lodging in Montréal. Additionally, the universities McGill University, Université de Montréal) offer dormitory-style lodgings. The CRM also has more suggestions.

Dates

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.

Possible schedule:

Monday

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.

Tuesday

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.

Wednesday

State-of-the-Octave address. Identify problems to work on, pair off and start working on those problems. Code sprints.
Potential topics of interest

• comparison of functionality between Octave and Matlab (what is the same, what is close, what is either different or significantly slower)
• availability and operability of profiling tools for Octave
• availability and operability of GUI interfaces to Octave
• 64-bit indexing for extremely large arrays
• Discussion of what belongs in Octave Core and what is a package or toolbox
• Discussion about minimum functionality for Octave Core
• Parallel computing using Octave
• Octave in an enterprise setting (making Octave updates trivial for maintenance in large scale computing infrastructures)
• Octave binary for OS-X - what should be included in an all-in-one installer? What versions of OS-X can/should be "supported"
• Octave binary for Windows - what should be included in an all-in-one installer? What versions of Windows can/should be "supported"

Thursday

Reports of results of the previous day. Tech talks if necessary. More code sprints.

Friday

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 graphics toolkit from gnuplot to FLTK. See bugs #31518, #31976, #32134, #32276, #34720.

Code Sprint for the Wiki

Define an effective organizational structure for the new wiki, and clean up the existing content.

• Reorganize existing content to conform the the defined structure.
• Move content to the homepage, OctaveForge, or the documentation.
• Delete spam.

Participants

• John W. Eaton
• Jordi Gutiérrez Hermoso
• Joanna Cheng (pending funding and leave)
• Juan Pablo Carbajal User:KaKiLa. Confirmed. Planning trip and hotel.
• Carnë Draug
• Ben Abbott (possible scheduling conflict)
• Mohammad Nasiruddin (pending funding)
• Pierre Bellec
• Rik Wehbring
• Thomas Yengst
• Alex Marcotte
• Max Brister
• Israel Herraiz (confirmation pending)
• Nir Krakauer

Funding

There may be limited funding to cover the travel expenses of selected participants.