Friday, I sleep surprisingly well for a first night abroad. I chose to wear a red FSFE t-shirt “There is NO CLOUD, just some other people’s computers”.
At 10am I’m going out to get a donut and coffee, and try to get inside NoiseBridge. Ringing the bell didn’t really work the first time, so I had to work a bit and retry once or twice. But then I was greeted by a French guy, who gave me a tour of the space : library, soldering stations, lots of parts, two classroom, a sewing space, and soon a large cutting machine… they have the whole 3rd floor of the building!
So, it’s Thursday and I’m getting a plane to San Francisco for the GCI meeting. Well, hopefully, as the French railway is on strike… Ok, my train was canceled, but another was 1.5 hours late so I managed to jump on it and arrive… at the Paris Lyon station, which meant taking the RER (oh no, it’s on strike as well), ok, the Metro to another station and then the RER to the airport.
Finally a new report. The time since the latest report has been spent mostly into gaining a preliminary support to streaming and begin finalyzing the underlying support code.
This included documenting myself about the APIs and figuring out how to implement the functionality in a clean way. There are various additions, we are moving to the right place so we finally have a streaming infrastructure.
Hi there! Once again with about a month of delay, here comes the activity report.
This report covers the range hrev50117-hrev50336.
Command line apps
AGMS contributed some fixes to the "mail" command line app which can be now be used easily to send automated messages from a script. This is an useful tool to have in automated tasks to post status report, errors, etc.
Opening issues for an application at github, for example, is a good way to help improving software. Often it's only a small detail and something a non-programming user could easily fix. Maybe it's just a typo or improved documentation etc.
Doing the changes yourself and contributing these fixes directly via a so-called "pull-request" is even better, as it saves the precious time of the developers/maintainers. Also, this dabbling in code might be a nice way to slowly ease yourself into more ambitious contributions.
It’s really a long time since the latest report, starting with this one I’m going to restore the usual article frequency.
The second part of my contract has been accepted and I’m finally returning to work on streaming support. However there is various work I had not the possibility to talk about and other things I pushed in the last week.
This week-end I went to the Journées du Logiciel Libre (JDLL) to hold the Haiku booth. The JDLL is a local event over two days, mostly focused at general public, with workshops and even a FLOSS gaming room for kids, but also with some highly technical and ethical talks. It also has a room with 3D printers and other maker tools.
Good news everyone!
It was a very long week, having easter in the middle too. There are various news, but I want to begin with a summary of this month.
- 42 commits have been included into the Haiku master branch
- More than 15 commits are still WIP among my branches
- 2 commits have been put into haikuports
- 4 tickets are now closed and a lot more are waiting my work to be complete
I submitted a request to Haiku Inc. to work for additional 240 hours, and I hope the project gets the needed funding to support my work. If you are interested in seeing my contract continue, please consider making a donation :-)
Let’s talk about what happened in the meantime.
Hello, here a short report about how things are coming along.
Work continue on the curl streaming code
I’ve continued working on the network glue by adding a very basic locking using the RWLocker in Haiku’s shared kit. This class allow multiple concurrent readers and an exclusive writer at one time.
Hello,
there are not a lot of news. This is mostly due to myself being occupied in the lastest two weeks with other commitments that I can’t really avoid. The situation is going to change, and I plan to restore a normal working day since monday.
The hours in the latest week have been put in the development of the streaming infrastructure. Plugins are now correctly loaded by the app, and the internal classes now provide the needed exceptions to consider network streams. I’ve had to do some step back into the API desing reconsidering more carefully the caching policies offered to the final program.
