204
edits
OctConf 2018 Notes: Difference between revisions
Jump to navigation
Jump to search
m
→Doing: Category
Carandraug (talk | contribs) (→Tuesday: more notes for today) |
m (→Doing: Category) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 96: | Line 96: | ||
=== Talking === | === Talking === | ||
; SWAN presentation | |||
: CERN presented their customized Jupyter instance named SWAN which integrates with the other CERN tools for data and data processing. | |||
; make {{Codeline|--no-gui}} default | |||
: Mike http://lists.gnu.org/archive/html/octave-maintainers/2018-03/msg00044.html suggested on the mailing to make this change for the upcoming 4.4 release. We discussed it all together, and everyone agrees. This should make things simpler for everyone. There will be only one flag which will be {{Codeline|--gui}} to start the gui and will be used by launchers. This will simplify the octave code too since we will no longer have to guess whether to start it or not based on whether we have persist or scripts to eval. | |||
: | |||
: We then coded that change. | |||
; review our review of code contributions | ; review our review of code contributions | ||
; | : a quick rehash of previous discussions. We do a lousy job at review contributions and would need better tools to make the reviewing easier. However, no is available to have such a tool which actually means replacing savannah with our own instance. | ||
; the complicated code in pkg | |||
: Juan showed that the code in pkg is a bit overcomplicated. Some changes were done to simplify it some 3-4 years ago but never got merged. Those changes no longer apply. Juan will try to make those changes again but first will be adding tests for pkg. | |||
; warning users if installing packages with url | |||
: discussed adding a warning that a package was not community maintained if user tried to use a url, and required user to answer yes or no. Decided against such warning. We may instead consider add a warning in the future if user tries to install something with an insecure connection (http:// instead of https:// or file://) | |||
=== Doing === | === Doing === | ||
; new Octave 4.2.2 release | ; new Octave 4.2.2 release | ||
: It was done. In the process of merging default to stable, we may do that tomorrow instead. | |||
; new release of image package | ; new release of image package | ||
: carandraug not even had time to get to it, too busy with changes to core and more discussions. | |||
; more tests to increase code coverage | ; more tests to increase code coverage | ||
; CERN visit | ; CERN visit | ||
; email maintainers mailing list with conclusions | ; email maintainers mailing list with conclusions | ||
== Thursday == | == Thursday == | ||
| Line 114: | Line 133: | ||
; OctConf 2019 | ; OctConf 2019 | ||
: We discussed the place, date, fee, and objective of OctConf 2019. | |||
: ---- | |||
: For '''place''', CERN offered to host it again next year. However, it was also suggested that we should try other places to meet new people and make it easier for people from far away, namely west coast USA. However, this also means more work since it's new logistics and other places have different costs. Seems like most contributions are European and flying them all to USA would be more expensive than flying the American developers to Europe. CERN is also quite cheap. Flying to Geneva from Europe is cheap, the rooms are free, and the CERN hotels are very affordable. It was also suggested to change place every two years or to come to CERN every two years with a new place each other year. We decided to have a call for an organizer, with a deadline of 1st of May. If no suitable option appears, then the place will be CERN. Rik will send out the call for organizer. | |||
: ---- | |||
: The '''date''' for the conference in 2019 must happen during the second half of March or the first half of April, according to the organizers availability. If it happens at CERN, it must be after 17th of March to avoid the motor exposition. As for the duration, next time it will be 3 full days instead of 2 days and two half days. The morning of the first day will be planning for the other days and the last evening to discuss OctConf 2020. | |||
: ---- | |||
: Because of free '''registration''', many registered people do not show. This makes organization difficult, we don't know how much coffee to order, how many people for the restaurants, or the size of the room. We will introduce a registration fee of ~ 20€ which then can be used to cover some costs of the social event. Other possibilities is a much higher fee which would include the accommodation since if attendees are coming, they would have to pay anyway. However, it was decided against since they will only see the high cost and decide against coming. | |||
: ---- | |||
: This years conference was pretty much a '''developers''' conference. There was a total of 3 talks with all other time spent on discussing developer topics and coding. It was discussed the issue of Octave visibility and that a user space could exist during OctConf, which would be one day for users to present their work to each other and have some workshops. This could even happen at the same time as developers would meet on other rooms. It was decided against, as there was not enough interest among the developers. This makes organization simpler since we also only need a smaller room with a whiteboard. There will be john's yearly talk about the state of Octave and Rik will make a more outreach talk, more sales pitch, showing what can be done with Octave and where it is being used. | |||
=== Doing === | === Doing === | ||
; email maintainers mailing list with conclusions | ; email maintainers mailing list with conclusions | ||
: done by carandraug | |||
[[Category:OctConf]] | |||
[[Category:2018]] | |||