As a heavy (ab)user of RAMFS[*]: I appreciated all the continued work on that fromt. Thanks @waddlesplash!
[*] I use it for 99.99% of my HaikuPorts builds, as it reduces SSD wear, and makes cleanups way faster/simpler, along with moderate build speedup on my anemic hardware.
The activity report was an interesting read,as always.
You already mentioned that you were busy with other things this month,but somehow I have the feeling that development slowed down over the last few months.
This is a subjective feeling and maybe I’m wrong,but I think that a year or two ago,more stuff happened at Haiku development.
Anyway,Haiku is going in the right direction and I’m proud to be a small part of it
Personally I’ve been working on other things as well. The year has been busier than usual at work (I hope that is not the “new normal” for me) and I did a lot of non-Haiku things as well. Getting back into Haiku dev a little bit this week, but I doubt that will make a lot of difference.
Also, the activity report only mentions things that were merged in the source tree. This is a limiting or at least delayed vision of things. It ignores Haikuports, all third party apps, and also changes that may have been in development for a while, but are still being discussed in Gerrit. Maybe we should try to communicate more about “what’s in progress” to help attract more people to the code review tool?
I’ve also been very focussed on HDS changes this last 6 months. I’ll write up a blog post on that once I can get through the next couple of deployments.
We have a “What’s new/updated in HaikuPorts” thread on this forum. FWIW I also do a semi-regular feature on the topic on YouTube: I aim at doing this every two months, depending on the number changes that occur.
If you choose not to submit your apps to Haikuports (I don’t) then getting the word out is up to you. The “Playground” topic on this forum seems to be the place to do that ATM, but a separate thread would be OK.
Yeah, that would be interesting: an inside look at the debates going on among the core devs, but in a summarized form that doesn’t require the more casual user to wade through dozens of Mailing list and IRC messages.
The mailing list does not get dozens of mesages. So that part should be easy.
I don’t follow IRC closely. It may be useful for quick technical discussions, but I don’t think that’s where important decisions should be taken, it comes with timezone hroblems and the channel is also busy with a lot of offtopic contents.
If you follow the forum, you are up to date on most things. The other part is looking at gerrit work in progress changes.