What: 98th HelenOS project meeting When: May 10, 2018, shortly after 18:00 Where: Radegastovna Peron Smichov, Prague Who: JS, JJ, OH, JJi, VH Excused: JZr Scribe: JJ
Regarding the venue, let's not come back to this place again: loud music and TV's with sport everywhere, we were unable to make the staff switch it off Round table: VH: - tinkered with Travis - made Sycek ccheck report available on ci.helenos.org OH: - plans to work on joinable fibrils JJi: - implemented a lot of stdc++ - conflicting HelenOS stdc symbols (e.g. list) -> std::hel - full unwinding support not likely to make it to the thesis - complex enough for a separate thesis - instead there will be a "mockup" exception support JS: - Continued work on Sycek - Explained how it works - Fine-grained tokenization of comments to make it possible to use the same indenting logic as for code - has plans for working on consoles and the GUI JJ: - WiP: virtio-net (https://github.com/jermar/helenos/tree/virtio-net) - split among the virtio-net NIC driver and libvirtio - should be easily reusable by other PCI virtio devices, such as virtio-block, may require some levels of indirection for non-PCI virtio - currently device config and virtqueue management code - SYSENTER/SYSCALL with TF - ia32 panics, see ticket #729 Debug exception during SYSENTER panics the kernel - amd64: added TF among the RFLAGS bits that get masked on SYSCALL - works in QEMU, but hard hangs on hw Other topics: - JZr is planning to remove HelenOS linker scripts in favor of compiler-provided ones - there is a catch though: for some platforms also the compiler-provided linker scripts must be patched, so it will become completely impossible to use HelenOS a compiler not built using our toolchain script (now it is _only_ unsupported, but still possible if one is lucky) - VH: how about importing the compiler-provided linker scripts to HelenOS then? - JJ brought up a topic "how to improve the community experience" - should more people be on IRC? - VH: would rather got rid of IRC completely, but uses it anyway - JS: said he would try to hang out in #helenos regularly, if only he can setup his IRC client properly - JJ: is fond of using IRC - shall we switch from Trac to GitHub issues? - People did not show extra emotional attachment to Trac - JJi suggested that reportedly GitHub issues are difficult to export, should we want to leave in the future - VH suggested we setup a GitLab instance in the future - JJ said that should we start self-hosting helenos.org, we would most likely need to switch to a statically generated web and move the wiki and tickets somewhere else anyway - shall more communication go to the ML? - people seemed indifferent, but complained about too much GH PR e-mail traffic (too much of it, sometimes happening too quickly) - JJ: let's forward all important communication (commits, tickets, travis) also to the ML, so that people who are not subscribed see that somebody is working on the project - people on IRC asked: - "What would be the best way to learn about HelenOS" - JJi confirmed that newcomers can have difficult times getting familiar with HelenOS - JS suggested creating more blog-like material and providing skeletal documentation on subsystems with one or two sentences for each - "Where is HelenOS going" - JJ: might be difficult to agree on because different people may have different ideas and a) we cannot tell people what to do b) he/she who merges existing code is more right than he/she who doesn't - JS: mentioned a minimal common direction (something which the scribe forgot (JS?) and experimenting) - Doxygen - current state is not good, if built automatically on ci.helenos.org the result would be dissatisfactory - VH: need to be able to break documentation for the individual components into Doxygen modules - JS: in the future Sycek could check that a function is documented On 05/04/2018 04:25 PM, Jakub Jermář wrote: > Hi! > > The 98th HelenOS project meeting will take place on Thursday of May > 11, shortly after 18:00 somewhere in Prague, Czech Republic. Please let > me know whether you plan to come so that I can make a reasonable > reservation, no later than by morning of May 9. Also, do let me know > whether you have any preferences for the venue of the meeting. > > Jakub > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
