Category: bongo (Page 9 of 9)
We talked about it, and I did the form yesterday – we’ve applied as a mentoring organisation for this summer’s Google of Code. I’ve never done an application to GSoC before, although I’m familiar with many of the other projects who’ve taken part. In hindsight, I wanted to say a lot more on our application form, but ho-hum. It would have been nice to find something like OpenSolaris’ application before-hand, but I feel comfortable knowing that our application is completely our own 🙂
I had separate chats with people about MDB yesterday, originally about how we’re going to fix a potential security problem with Bongo, but went into a wider-ranging discussion about MDB. For those who don’t know, MDB is the LDAP-like API we use to store virtually all configuration.
There are a couple of issues with our code base right now:
The mdb.conf is world-readable, which is the security problem. This is necessitated by the current Dragonfly setup, which runs in the Apache process; Ideally, we want full configuration access from Hawkeye (the new web admin tool), also in a secure manner; Making MDB schema changes etc.
In general, using shared libraries already available on a system is a good thing. Witness the difference compiling against the system CLucene, rather than having to build your own:
real 3m0.256s user 1m39.937s sys 0m29.177s
$ time make # against the imported CLucene
real 6m27.311s user 4m30.465s sys 0m47.084s Basically, Lucene accounts for half of the entire build time. If you’re lucky enough to have a clucene development package on your platform (on Fedora it’s clucene-core-devel, on Debian it’s libclucene-dev), you can ignore the CLucene we package and use the system one.
There’s a number of things I’ve been meaning to blog about recently. Thanks to Andrew, who has been blogging about stuff, people will have hopefully known about the web UI meeting we had recently. While relatively informal, it does feel like everyone wants to move in the same direction: a light-weight reliable UI framework pulling togther useful components to provide a compelling app. We’re going to start with “Flasher”, the UI for non-Bongo users, and I started story boarding some use cases.
Within this post, I mention the B-word (business) a few times. Don’t let this put you off, please 😉
One thing I’ve noticed when meeting up with other free software users and developers is that a strikingly high proportion of them are involved in business in some way: either owner/managers of their own small business, or having a key role in one. Not most of them by any means, but a much higher proportion than any other group of people I meet (which perhaps says more about the company I keep – I don’t know!
We all have New Year’s resolutions in some form or another; I haven’t really got mine straight in my head yet but there are a couple of things I’m committing to over the next month or two – one of which is to spend more time regularly hacking Bongo. I had hoped to get some hacking in over Christmas; family events overtook that and as a result I’ve spent virtually no time on Bongo at all.
(What are we to call them? I’ll stick with MoMsg for now I think)
Welcome to the planned MailCo, whose name has been revealed as Mozilla Messaging Inc.. This has been in the pipeline for a little while, and it doesn’t seem to be quite ready yet, but it seems they’re almost there.
I think this will be news to a lot of people – Bryan Clark tells us on his blog he only waved goodbye to RedHat yesterday – but it’s best that things go forward pretty quickly in my opinion.
I noticed “boycott novell” made mention of Bongo today – they mistook our M3 release as the announcement of the project – but nice to see another mention in a new place. I’d like to comment slightly on the Yahoo! situation, though.
The boycott site is quite wrong when it talks of “pulling a Hula”: Hula was never sold because it was competitive to Microsoft Exchange. Anyone who was involved with the project, or used Hula (it’s still available in Ubuntu!
