Contributed by mtu on from the better-late-than-never dept.
[AsiaBSDCon 2009]: March 14-15, 2009, Tokyo, Japan There are two conferences in Japan that I always look forward to attending: PacSec for security and AsiaBSDCon for everything BSD. This year's AsiaBSDCon looks to be very interesting with more than a few OpenBSD presentations. I'm especially excited as Theo de Raadt will be one of the Plenary speakers. |
Read on to find out more about Theo's plenary talk:
I had a very interesting discussion with Theo on the subject of his talk and as usual I was more than enlightened. Having seen Theo present on a few occasions, I know that it will be a talk not to be missed, if not for the message then for the lively and interesting discussions that usually ensue :-).
Here is Theo's plenary abstract:
Twelve years ago OpenBSD developers started engineering a release process that has resulted in quality software being delivered on a consistent 6 month schedule -- 25 times in a row, exactly on the date promised, and with no critical bugs. This on-time delivery process is very different from how corporations manage their product releases and much more in tune with how volunteer driven communities are supposed to function. Developer and testing laziness is mostly circumvented and leader frustration is kept to a minimum. The reasons, mechanics and social workings of our process have never been detailed outside the project, but now will be, hopefully providing some insight to others who face delays and quality issues with their own product lines.David Gwynne (dlg@) will also present his paper on pfsync and Active-Active Firewall Cluster Support in OpenBSD. Claudio Jeker (claudio@) will give an updated talk on the history and present state of OpenBGPD. Constantine A. Murenin (cnst@) will present the history and design of OpenBSD's hardware sensors framework. Finally, Kristaps Dzonsons will discuss his work on deprecating groff and using OpenBSD by way of example.
I would highly recommend this conference to anyone interested in BSD in general. Please don't expect a conference write up but I am certain that the papers and perhaps slides will be available shortly after the event.
Mark T. Uemura
(Comments are closed)
By Brynet (Brynet) on
By Anonymous Coward (89.103.95.221) on
Page from PacSec about OpenBSD is very nice OpenBSD-support Japan.
I hope,that talks and videos will be available too. Just for info.Are there some companies which use OpenBSD a lot or as their main bussiness and are "ready" to talk about it? I think about more updated version of this book BSD Success Stories and specifically about OpenBSD?It may help some people to use OpenBSD in their work.I think..............By Anonymous Coward (195.42.56.43) on
So lucky to be in Japan dudes !!!
Comments
By Anonymous Coward (85.19.213.88) on
>
> So lucky to be in Japan dudes !!!
I'm so jealous. When's Theo and company coming to Norway? I'm sure
Hansteen has enough room to accommodate a few of them ;-) I'll bring
the beer (and my laptop).
By diw (diw) davidianwalker@gmail.com on
And so you should be.
> a release
process
Of course every engineering project has a plan, a core component of which is a timetable ...
> Developer and testing laziness is mostly circumvented
and leader frustration is kept to a minimum.
Of course all projects are aware enough to build their plan around these constants ...
It really is a no brainer.
Work to a plan or in a state of confusion? Hmm.
Take into account human factors or ignore them? Hmm.
Without careful planning taking into account the resources (volunteers) it may well be that code quality dissipates.
That's why everyone does these things. :]
As much as it is useful to the code wranglers I like it for me.
Friendly upgrading are a criteria when I consider trying software.
Coherent release numbers. I can live with that.
Releases determined by a calender? Ditto.
Productive developers? Fine by me.
OpenBSD FTW.
Best wishes.
Comments
By Anonymous Coward (204.80.187.9) on
> Without careful planning taking into account the resources (volunteers) it may well be that code quality dissipates.
> That's why everyone does these things. :]
>
If everyone did these things, why would OpenBSD be interesting? Yet, it is....
By Peter J. Philipp (62.75.160.180) on http://solarscale.de