
Yay openSUSE is having a shindig in September, yes it's the openSUSE Conference 2011 (aka oSC11). And seeing as the theme is rwx³ I've submitted a couple of BoF propossals. Now they haven't been approved yet, so I'm not 100% sure they'll happen but either way I'll be there and will be keen to talk to anyone that is interested.
The first topic I'd like to talk about is as the post's subject says "Designing the missing Web UI for Bongo".
For un-aware the Bongo is an e-mail & calendaring solution that can trace its roots back to Netmail. It is directly descended from Hula, which was a proof of concept email & calendaring solution which had such luminary hackers such as Dave Camp, Peter Teichman, Nat Friedman, Garrett Le Sage and many others. Unfortunately due to commercial and other management decisions Hula was terminated. Yes it was honestly cool, and as a PoC it actually worked. Thankfully it was an open source project and was forked just before the door was closed, into the Bongo project. As part of the code clean up and ongoing development the existing UI had to be dropped due to code complexity, size and lack of resources for maintaining it. Which leads us to where we are now.
What we have now is a MTA backend that can be distributed over multiple servers or combined on a single machine. It's pretty light weight and works. We support the usual protocols, so IMAP (with or without TLS/SSL), POP3, SMTP (currently we've had to disable outgoing TLS/SSL due to a bug), CalDAV (albeit in a simple form), anti-virus support for clamav, and anti-spam support with spamassassin. So the foundation blocks are there in place, all we're missing is the shiny frontend beauty.
Just to be clear Bongo is not aimed at the "Groupware" market, so it isn't aiming to compete with the likes of Zimbra, Exchange, Domino, GroupWise, OpenXchange etc. It is aimed at those that don't require the bloat that comes with those big products, those that want a simple clean way to deal with e-mail and calendaring. A competitor could be viewed as Gmail+Google Calendar, but self hosted at home/office or hosted as a service. Target audience I suppose could be viewed as individuals/families; SOHO that don't need the bloat or intricate understanding of servers like postfix or sendmail with dovecot or similar; educational facilities - you get the picture.
As I mentioned we have a fairly stable backend that provides email and calendaring, but the only way of interfacing with it is via a fat client (evolution, thunderbird, kmail, etc) - I use it at home. What we need is a way of getting to it via a browser. The aim of my BoF proposal is to discuss ways of meeting that requirement, what technologies could and maybe should be used, going through pros & cons and getting people interested in e-mail & calendaring and web design involved.
As a project we have some ideas on technologies used, but at the end of the day this whole web joojoo is kind of out of developer's field, so if one of you hipster hackers has a better idea and implements it then who are we to argue ;-) As an example we kind of like the idea of HTML5 but we don't have to be limited to that, at the end of the day we want a clean simple and functional UI - both user and admin. We have a blank canvas so anything goes.
As Bongo can be a distributed solution it would also be great if the Web UI could be re-used in a way similar to Roundcube or Squirrelmail, Meaning you could use it as a generic web based MUA hooking into almost any mail server. This isn't mandatory but a "would be nice to have" type feature. Initially we would be looking at something that provides core functionality - email, calendaring & contacts - but can be extended via a plugin system maybe. Again that's just a thought.
Hopefully we can get some real traction going and maybe after the BoF we can start to do some hacking on it :-) It would be absolutely awesome if by the end of the conference we had the beginings of a beautiful product.
So please register for the conference and join in the fun.
It's been over a week now since I came back from the fantabulous FOSDEM, and have had a chance to digest a lot of the conversations I had whilst there. One of the conversations I had was with a senior developer who was in a sort of Special Interest Group. He mentioned to me that his management had asked the SIG to formulate a plan for where they wanted to see their project in five years, and how they aimed to get there.
Now I thought about that idea for a while, and to be honest I find it a really difficult question to answer properly. So I thought I'd ask my fellow community members (whether that's openSUSE, Bongo or whatever) how would you answer that question in relation to your chosen project? I can invariably only come up with a partial answer, not a full where and how. Let me try and show you what I mean.
I'll take Bongo as my first example. For those that have no idea what Bongo is let me explain: Bongo is an evolution of some forward thinking by some people who used to work at Novell. It started out as the Hula Project; then Novell sold the related assets off due to strategy alignments (or whatever); a few of us wanted to continue and forked the code and created the Bongo Project. OK so that's a brief history but what is it? Bongo is a lightweight and simple e-mail & calendaring solution, it is based on proven technology – the heritage goes back to NIMS if I'm not mistaken. Whoopee do there are like a million and one e-mail solutions out there. Yes but not all in one solutions that are light on resources and contain all functions. Bongo is NOT a groupware product, it is aimed at SMBs, geeks education and pretty much anyone that just wants e-mail, calendaring and contacts. Think of it as a FOSS solution to provide the functionality of Gmail+Google Calendar. Here endeth the history lesson.
Back to the example. So I need to list where I would like to see Bongo in five years time, OK how about:
-
Used by a large number of education and SMBs
-
Shipped with all the major distributions
-
Mimicked but never beaten by potential competitors
-
Partnering with other projects to maximise reach
-
Leading edge web front end
-
Hooks for multiple languages/frameworks
-
Large developer community
-
Large user community
-
Global domination
Now the trickier part – how to achieve those goals. So far all I can come up with is (in no particular order):
-
Canvas more developers that are interested in the e-mail/calendaring space to join in
-
Advertise and market Bongo
-
Actually get a working WebUI done
-
Look at existing solutions and try and learn from them
-
Speak to distributions and see if they can help
-
Win the lottery
As you can see the list for where is larger than the list for how. Sure I could expand the latter a bit by being more detailed but this is supposed to be a bullet list with summaries not an essay. In my view one needs to get a list to work from and then expand on it, maybe even categorising the bullet points to see what/how/where/when and also explaining why.
Now Bongo is a relatively simple project with a small user base and community, and a very defined focus. The other project that I'm involved in and care for is openSUSE, and lord knows that is no simple beast :-)
Let me try the same with openSUSE. The where:
-
At the forefront of distributions
-
Large developer base
-
Better toolsets for developers
-
Working better and closer with fellow distributions
-
Have a foundation that manages the project
-
Get more community contributors involved to lessen the load on Novellians
-
Learn from other projects to help improve us
-
Keep momentum going
-
Grow the user base
-
World domination
Now the how:
-
More active marketing
-
Speaking to developers of different projects to find ut what they feel is missing
-
Win the lottery
As you can see I'm woefully short on how on earth I am to achieve anything. I'm open to suggestions :-)
I know for a fact that there may be one or two items that I've listed that could be contentious, and do you know what? I sincerely hope so :-) Now don't get me wrong, I really do appreciate and am grateful for all the work effort and money that Novell has invested in openSUSE; but it isn't fair at all for Novell to keep carrying the Project. If anyone thinks they're not, you are living in lala land. Sure some of it might be their own doing, but a lot isn't and it is up to us the community help them so that we can benefit even more.
I really do hope people start thinking, and doing it seriously about where they would like to see their preferred project in five years time. I would also love to see people's responses as to Where & How they would do it. Anyone that starts screaming like my 21month old daughter about this or that will get a sound thrashing and ignored. There is absolutely ZERO room for pettiness in the community. If you disagree with something then great! Just make sure you are as detailed and as calm as possible about why and also how you propose to do it differently. This doesn't just apply to this whole five year plan thing, but to general discussion.
Don't loose your passion, just learn to use your passion ;-)
Deb, deb, deb
Bad joke I know, but I've got a load more where that came from so don't tempt me. Basically it's two fold (a) my curiosity to build .deb in the OBS and (b) to help Jonny out with bandwidth (utilising openSUSE's global mirrors), I've got Debian Etch packages in my OBS repository. Currently only x86 only (x86_64 Debian and Ubuntu hosts haven't been implemented yet), Ubuntu builds are going to take a bit longer as I need to work out a few issues.
I have both M2 stable (or as stable as it gets at the moment) and unstable builds from svn, just like my RPMs. To get hold of these scouts add the following to /etc/apt/sources.list:
deb http://software.opensuse.org/download/home:/FunkyPenguin/ Debian_4_Etch/
Please let me know if you encounter any issues using any of my packages. I'll leave it up to you how you contact me, here are a few:
Mailing lists, comment on this blog, using the Meebo box on this blog, IRC or a message in a bottle (the latter may take a while as I could be deep in conversation with my coconut friend).
Deb, deb, deb
Bad joke I know, but I've got a load more where that came from so don't tempt me. Basically it's two fold (a) my curiosity to build .deb in the OBS and (b) to help Jonny out with bandwidth (utilising openSUSE's global mirrors), I've got Debian Etch packages in my OBS repository. Currently only x86 only (x86_64 Debian and Ubuntu hosts haven't been implemented yet), Ubuntu builds are going to take a bit longer as I need to work out a few issues.
I have both M2 stable (or as stable as it gets at the moment) and unstable builds from svn, just like my RPMs. To get hold of these scouts add the following to /etc/apt/sources.list:
deb http://software.opensuse.org/download/home:/FunkyPenguin/ Debian_4_Etch/
Please let me know if you encounter any issues using any of my packages. I'll leave it up to you how you contact me, here are a few:
Mailing lists, comment on this blog, using the Meebo box on this blog, IRC or a message in a bottle (the latter may take a while as I could be deep in conversation with my coconut friend).
Deb, deb, deb
Bad joke I know, but I've got a load more where that came from so don't tempt me. Basically it's two fold (a) my curiosity to build .deb in the OBS and (b) to help Jonny out with bandwidth (utilising openSUSE's global mirrors), I've got Debian Etch packages in my OBS repository. Currently only x86 only (x86_64 Debian and Ubuntu hosts haven't been implemented yet), Ubuntu builds are going to take a bit longer as I need to work out a few issues.
I have both M2 stable (or as stable as it gets at the moment) and unstable builds from svn, just like my RPMs. To get hold of these scouts add the following to /etc/apt/sources.list:
deb http://software.opensuse.org/download/home:/FunkyPenguin/ Debian_4_Etch/
Please let me know if you encounter any issues using any of my packages. I'll leave it up to you how you contact me, here are a few:
Mailing lists, comment on this blog, using the Meebo box on this blog, IRC or a message in a bottle (the latter may take a while as I could be deep in conversation with my coconut friend).
With the release of M2 and Jonny's DEBs a standardisation on package names/version was decided. So as of now the stable release of bongo will be versioned 0.2.0 and the unstable will be 0.2.0+svn(revision number).
So when using the repos, BE CAREFUL when upgrading. Choose carefully, you have been warned.

The Bongo BoF is on
One thing I would like to do with the BoF is to record the session on video, so if anyone is attending and has a camcorder that can easily transfer the video off (I have a Sony DCR-IP7E and it is a real bitch to get the video off even on proprietary OSes) I would be most appreciated.
So to sum up -
There are some shots of Hawkeye before it received its A-List Celebrity facelift, so you can see there is progress being made
The RPMs have had a little rework this week, after some deliberation it was decided to remove the bongo-hawkeye and bongo-dragonfly packages and replace them with a single bongo-web package. I had forgotten to enter one line in the spec which made it awkward to install, thanks to Lance Haig for highlighting the issue
Work have finally decided to send me somewhere for a week, so I'm not 100% sure how much Bongo related work I'll be able to do. If there is a specific issue that you need me for please mail me or mail either of the mailing lists, and I'll try and jump on IRC or something.
P.S. Great work on Hawkeye Alex, but couldn't you use an alias, middle name or something? Two Alex's is fine, but have two with the same initials?!
I would appreciate it if people could get the word out that this BOF is planned, and try and get as many people there. Once I have confirmation on which day and at what time I'll let it be known.
I would appreciate it if people could get the word out that this BOF is planned, and try and get as many people there. Once I have confirmation on which day and at what time I'll let it be known.
It was a simple misunderstanding/typo on my part - RHEL 5 uses the Fedora Core 6 packages, I have changed the wiki to point to the right repo on the OBS. There is a slight issue when installing on RHEL5 well actually CentOS 5 but it should be the same (I hope), you will possibly get an error similar to this:
cp: cannot stat `/usr/share/bongo/examples/bongo.conf': No such file or directory /var/tmp/rpm-tmp.65080: line 20: fg: no job controlThe strange thing is bongo.conf is in /usr/share/bongo/examples All you need to do is copy it from there to /etc/httpd/conf.d/
As always, let me know if there are any issues.
The following distros and architectures now have packages available for them:
- Gentoo
- Mandriva 2006 - i586
- Mandriva 2007 - i586
- Fedora Core 5 - i386 / x86_64
- Fedora Core 6 - i386 / x86_64
- SUSE 10.0 - i586 / x86_64
- SUSE 10.1 - i586 / x86_64
- openSUSE 10.2 - i586 / x86_64
- SUSE Linux Enterprise 10 - i586 / x86_64
- RHEL 4 / CentOS 4 - i386 (Still not really working)
- RHEL 5 / CentOS 5 - i386 / x86_64 (Uses FC6 packages)
I know Ubuntu and Debian is still missing, hopefully soon. Also OpenSolaris will hopefully be available - no guarantees, if you hadn't noticed I've had a crappy time getting Bongo to work
The Un-Stable packages will be a bit longer as I need to do a bit of rejigging with my repo on the OBS, another announcement will be made when it's ready.
The following distros and architectures now have packages available for them:
- Gentoo
- Mandriva 2006 - i586
- Mandriva 2007 - i586
- Fedora Core 5 - i386 / x86_64
- Fedora Core 6 - i386 / x86_64
- SUSE 10.0 - i586 / x86_64
- SUSE 10.1 - i586 / x86_64
- openSUSE 10.2 - i586 / x86_64
- SUSE Linux Enterprise 10 - i586 / x86_64
- RHEL 4 / CentOS 4 - i386 (Still not really working)
- RHEL 5 / CentOS 5 - i386 / x86_64 (Uses FC6 packages)
I know Ubuntu and Debian is still missing, hopefully soon. Also OpenSolaris will hopefully be available - no guarantees, if you hadn't noticed I've had a crappy time getting Bongo to work
The Un-Stable packages will be a bit longer as I need to do a bit of rejigging with my repo on the OBS, another announcement will be made when it's ready.
It looks like word about Bongo is starting to get out there which is great, my only request is that we have a very very wealthy person donate ludicrous amounts of cold hard money to help fund Bongo without wanting too much in return
It looks like word about Bongo is starting to get out there which is great, my only request is that we have a very very wealthy person donate ludicrous amounts of cold hard money to help fund Bongo without wanting too much in return
So I went and downloaded the Developer Edition in the hope that it would have all that was needed to get Bongo up and running. Sun provide the DVD ISO as a fragmented download to ease people's bandwidth - 5 zip files of about 650MB each - so after pulling all 5 down and following their instructions I had a 3.6GB DVD ISO to use. It might have all I need, but blow me if I can find them all. I asked on #bongo (always my first point of call
Word of caution people OpenSolaris Developer Edition takes a fair amount of time to install - 3h 25min - and I couldn't find anyway of selecting which packages I wanted installed. Once it was finished and ready for use I set about trying to get the packages I needed for Bongo building. Thanks to the guys over on #opensolaris on irc.freenode.net, I found out how to install packages that aren't already installed but provided on the disc.
Here is my little HowTo to getting Bongo to build on OpenSolaris (*CAUTION* This is still WIP as I can't get past ./configure):
To install Python 2.4 and -devel packages
bash-3.00# cd /media/SOL_11_x86/Solaris_11/ProductMake sure you include the dot (.)
bash-3.00# pkgadd -d. *Python*
When prompted to continue with the installation of [y,n,?] select y
install bison
bash-3.00# pkgadd -d. SUNWbisonAgain when prompted to continue with the installation of [y,n,?] select y
For the remaining packages, head over to Blastwave and follow the howto on to install pkg-get and setup install sources. Ensure you choose the unstable feed eg: /unstable. This is very similar to using apt-get, but unfortunately there is no GUI to make package hunting easy (I ended up browsing the mirror and Blastwave's Software listing).
Once that is all completed I installed the following:
bash-3.00# pkg-get -i ggettext openldap openldap_devel gnutls flex apache2 ap2_modpython doxygen pkgconfig libxml2 curl gcc4core gcc4g++ libpoptAgain when prompted to continue with the installation of [y,n,?] select y
There may be an issue with ap2_modpython pulling Blastwave's version of Python (which is 2.3), either run
bash-3.00# python-Vor try building Bongo - you'll soon find out
bash-3.00# pkg-get -r python
This enabled me to run
bash-3.00# ./configure --prefix=/usr --localstatedir=/var/bongobut when it comes to running make I get a bit unstuck
bash-3.00# makeThe contents of line 1037 of my Makefile is: ACLOCAL_AMFLAGS = -I m4 -I macros Anyone got any ideas?
make: Fatal error in reader: Makefile, line 1037: Unexpected end of line seen
I then decided to try gmake and got the following:
bash-3.00# gmakeAgain, anyone with a clue?
src/agents/addressbook/.deps/addressbook.Po:1: ** missing separator. Stop.
If anyone (Sebastian maybe?) has managed to get Bongo running on Solaris please let me know how. Also if anyone has a better way of doing it I'm all ears
So I went and downloaded the Developer Edition in the hope that it would have all that was needed to get Bongo up and running. Sun provide the DVD ISO as a fragmented download to ease people's bandwidth - 5 zip files of about 650MB each - so after pulling all 5 down and following their instructions I had a 3.6GB DVD ISO to use. It might have all I need, but blow me if I can find them all. I asked on #bongo (always my first point of call
Word of caution people OpenSolaris Developer Edition takes a fair amount of time to install - 3h 25min - and I couldn't find anyway of selecting which packages I wanted installed. Once it was finished and ready for use I set about trying to get the packages I needed for Bongo building. Thanks to the guys over on #opensolaris on irc.freenode.net, I found out how to install packages that aren't already installed but provided on the disc.
Here is my little HowTo to getting Bongo to build on OpenSolaris (*CAUTION* This is still WIP as I can't get past ./configure):
To install Python 2.4 and -devel packages
bash-3.00# cd /media/SOL_11_x86/Solaris_11/ProductMake sure you include the dot (.)
bash-3.00# pkgadd -d. *Python*
When prompted to continue with the installation of [y,n,?] select y
install bison
bash-3.00# pkgadd -d. SUNWbisonAgain when prompted to continue with the installation of [y,n,?] select y
For the remaining packages, head over to Blastwave and follow the howto on to install pkg-get and setup install sources. Ensure you choose the unstable feed eg: /unstable. This is very similar to using apt-get, but unfortunately there is no GUI to make package hunting easy (I ended up browsing the mirror and Blastwave's Software listing).
Once that is all completed I installed the following:
bash-3.00# pkg-get -i ggettext openldap openldap_devel gnutls flex apache2 ap2_modpython doxygen pkgconfig libxml2 curl gcc4core gcc4g++ libpoptAgain when prompted to continue with the installation of [y,n,?] select y
There may be an issue with ap2_modpython pulling Blastwave's version of Python (which is 2.3), either run
bash-3.00# python-Vor try building Bongo - you'll soon find out
bash-3.00# pkg-get -r python
This enabled me to run
bash-3.00# ./configure --prefix=/usr --localstatedir=/var/bongobut when it comes to running make I get a bit unstuck
bash-3.00# makeThe contents of line 1037 of my Makefile is: ACLOCAL_AMFLAGS = -I m4 -I macros Anyone got any ideas?
make: Fatal error in reader: Makefile, line 1037: Unexpected end of line seen
I then decided to try gmake and got the following:
bash-3.00# gmakeAgain, anyone with a clue?
src/agents/addressbook/.deps/addressbook.Po:1: ** missing separator. Stop.
If anyone (Sebastian maybe?) has managed to get Bongo running on Solaris please let me know how. Also if anyone has a better way of doing it I'm all ears
When you are viewing a mail/conversation, in the top right hand corner of your view you'll see something that enables you to scroll up and down through your mail/conversations avoiding having to go back to your inbox and selecting the next message. The key to working out which way you are scrolling is to look for the greater/lesser than symbols (< >), these point you in the direction of the message trail. Below is a screenshot detailing it, click on the thumbnail for a large view:
The font could probably do with changing as it is a bit hard to see, or is that just my bad eyesight?
EDIT: Now that Zooomr has been upgraded it is back online, I've move the hosting of the image. I highly recommend Zooomr
When you are viewing a mail/conversation, in the top right hand corner of your view you'll see something that enables you to scroll up and down through your mail/conversations avoiding having to go back to your inbox and selecting the next message. The key to working out which way you are scrolling is to look for the greater/lesser than symbols (< >), these point you in the direction of the message trail. Below is a screenshot detailing it, click on the thumbnail for a large view:
The font could probably do with changing as it is a bit hard to see, or is that just my bad eyesight?
EDIT: Now that Zooomr has been upgraded it is back online, I've move the hosting of the image. I highly recommend Zooomr
When you are viewing a mail/conversation, in the top right hand corner of your view you'll see something that enables you to scroll up and down through your mail/conversations avoiding having to go back to your inbox and selecting the next message. The key to working out which way you are scrolling is to look for the greater/lesser than symbols (< >), these point you in the direction of the message trail. Below is a screenshot detailing it, click on the thumbnail for a large view:
The font could probably do with changing as it is a bit hard to see, or is that just my bad eyesight?
EDIT: Now that Zooomr has been upgraded it is back online, I've move the hosting of the image. I highly recommend Zooomr
The repository hasn't changed yet, as soon as it does i will let you know. If possible could people try the UNSTABLE packages as these include Pat's recent patch to remove the last of openssl. Obviously be careful when selecting which package, if you search for "bongo" and then select "install all in list" you will quite possibly come unstuck as it will try and install both versions.
Hmm, note to self: look at adding to the spec file that if one is installed do not install the other.
I've been battling now for two days to get bongo to build on CentOS4/RHEL4 without joy - kudos to Alex and Pat for their patience and perseverance. Hopefully we can get this resolved soon. That will just leave Mandriva 2006/Mandriva 2007 and SLES9 to fix, and to start building for Debian and Ubuntu.
So how does this affect the Bongo RPMs? Simple Bongo will move into the server:mail group. Before we go live in there, a few things have to be done on the OBS side of things (primarily for us is FC6/Mandriva/Debian/Ubuntu support) which requires the enabling of some services. Don't forget that the OBS is still in beta
My plan is to create two groups of packages - STABLE and UN-STABLE. The former will be official releases like M1/M2 etc, where as the latter will be variants of stable that include patches that haven't yet been committed or incorporate messy hacks.
I will let everyone know when the move is complete, with the new repo details, and update the wiki
So how does this affect the Bongo RPMs? Simple Bongo will move into the server:mail group. Before we go live in there, a few things have to be done on the OBS side of things (primarily for us is FC6/Mandriva/Debian/Ubuntu support) which requires the enabling of some services. Don't forget that the OBS is still in beta
My plan is to create two groups of packages - STABLE and UN-STABLE. The former will be official releases like M1/M2 etc, where as the latter will be variants of stable that include patches that haven't yet been committed or incorporate messy hacks.
I will let everyone know when the move is complete, with the new repo details, and update the wiki
So how does this affect the Bongo RPMs? Simple Bongo will move into the server:mail group. Before we go live in there, a few things have to be done on the OBS side of things (primarily for us is FC6/Mandriva/Debian/Ubuntu support) which requires the enabling of some services. Don't forget that the OBS is still in beta
My plan is to create two groups of packages - STABLE and UN-STABLE. The former will be official releases like M1/M2 etc, where as the latter will be variants of stable that include patches that haven't yet been committed or incorporate messy hacks.
I will let everyone know when the move is complete, with the new repo details, and update the wiki
So how does this affect the Bongo RPMs? Simple Bongo will move into the server:mail group. Before we go live in there, a few things have to be done on the OBS side of things (primarily for us is FC6/Mandriva/Debian/Ubuntu support) which requires the enabling of some services. Don't forget that the OBS is still in beta
My plan is to create two groups of packages - STABLE and UN-STABLE. The former will be official releases like M1/M2 etc, where as the latter will be variants of stable that include patches that haven't yet been committed or incorporate messy hacks.
I will let everyone know when the move is complete, with the new repo details, and update the wiki
So how does this affect the Bongo RPMs? Simple Bongo will move into the server:mail group. Before we go live in there, a few things have to be done on the OBS side of things (primarily for us is FC6/Mandriva/Debian/Ubuntu support) which requires the enabling of some services. Don't forget that the OBS is still in beta
My plan is to create two groups of packages - STABLE and UN-STABLE. The former will be official releases like M1/M2 etc, where as the latter will be variants of stable that include patches that haven't yet been committed or incorporate messy hacks.
I will let everyone know when the move is complete, with the new repo details, and update the wiki
On a slightly less chirpy note, RHEL4, SLES9, CentOS4 and Mandriva 2006 builds are pretty much a no-go at this moment in the space-time continuum. This is mostly down to GNUTLS' API changing and the aforementioned distros have the "old" one. Alex and Pat are working away trying to get it resolved as soon as possible, thanks go to Michel for troubleshooting and finding the issue.
On a slightly less chirpy note, RHEL4, SLES9, CentOS4 and Mandriva 2006 builds are pretty much a no-go at this moment in the space-time continuum. This is mostly down to GNUTLS' API changing and the aforementioned distros have the "old" one. Alex and Pat are working away trying to get it resolved as soon as possible, thanks go to Michel for troubleshooting and finding the issue.
On a slightly less chirpy note, RHEL4, SLES9, CentOS4 and Mandriva 2006 builds are pretty much a no-go at this moment in the space-time continuum. This is mostly down to GNUTLS' API changing and the aforementioned distros have the "old" one. Alex and Pat are working away trying to get it resolved as soon as possible, thanks go to Michel for troubleshooting and finding the issue.
Alex has mentioned doing a BOF (he did one last year for Hula) which I think is a pretty good idea. Hopefully we can get some shirts made up prior to going there. So far Alex, Jonny and myself are thinking of going - I just need to convince the wife to let me go, I'm currently getting a good ear bashing
Alex has mentioned doing a BOF (he did one last year for Hula) which I think is a pretty good idea. Hopefully we can get some shirts made up prior to going there. So far Alex, Jonny and myself are thinking of going - I just need to convince the wife to let me go, I'm currently getting a good ear bashing
In total there are now 10 binary packages + 1 source package. These can be obtained from the following places:
- Mandriva 2007
- Fedora Core 5
- Fedora Core 6
- SUSE 10.0
- SUSE 10.1
- openSUSE 10.2
- SUSE Linux Enterprise 10
There are currently issues with the x86_64 builds, which I'm trying to resolve so please be patient. I'm also going to start looking at getting CentOS 4 builds done this week, and hopefully Debian/Ubuntu builds.
The issues with building on Mandriva 2006, SLES 9, and SUSE 9.3 are still outstanding but are being worked on. As always any problems/issues log a bug, and try and get me on IRC or the mailing lists.
In total there are now 10 binary packages + 1 source package. These can be obtained from the following places:
- Mandriva 2007
- Fedora Core 5
- Fedora Core 6
- SUSE 10.0
- SUSE 10.1
- openSUSE 10.2
- SUSE Linux Enterprise 10
There are currently issues with the x86_64 builds, which I'm trying to resolve so please be patient. I'm also going to start looking at getting CentOS 4 builds done this week, and hopefully Debian/Ubuntu builds.
The issues with building on Mandriva 2006, SLES 9, and SUSE 9.3 are still outstanding but are being worked on. As always any problems/issues log a bug, and try and get me on IRC or the mailing lists.
In total there are now 10 binary packages + 1 source package. These can be obtained from the following places:
- Mandriva 2007
- Fedora Core 5
- Fedora Core 6
- SUSE 10.0
- SUSE 10.1
- openSUSE 10.2
- SUSE Linux Enterprise 10
There are currently issues with the x86_64 builds, which I'm trying to resolve so please be patient. I'm also going to start looking at getting CentOS 4 builds done this week, and hopefully Debian/Ubuntu builds.
The issues with building on Mandriva 2006, SLES 9, and SUSE 9.3 are still outstanding but are being worked on. As always any problems/issues log a bug, and try and get me on IRC or the mailing lists.
of distros to be built against! This couldn't have come at a better
time as my FC6 virtual machine managed to annoy me so I wiped it in a
fit of rage
So to summarise the avialable distrobutions available for Bongo from the OBS are:
One thing to note is that currently openSUSE 10.2 doesn't work (builds but doesn't run) due to Python 2.5 - a bug
has been filed with a possible solution, and Luis and Alex are
assessing what route is best to take for a fix. The other distros will have to wait until the libcurl issue has been fixed.
If I could ask users of the packages to file bugs with regards to issues, that would be most helpful, you can also shout on the mailing lists and IRC. I will be more active on IRC as of next week as I'll be back in the office, and not galavanting around.
I normally enjoy listening to LUG Radio, but they appear to have taken the stance of bashing Novell and all things related to them including SUSE/openSUSE as a result of the announcement with Microsoft. As it was the last episode for 2006, they had a "Predictions" segment, one of the predictions was that there will be only 2/3 major community distrobutions - Ubuntu (surprise, surprise!), Fedora and Debian. They reckon that openSUSE will dissapear as Novell's focus is purely enterprise related.
As they like to say on the show CHIN! Do they forget that SUSE has been around since about 1996, and has a huge community attached to it. They also reckon that if Novell ceased support for openSUSE the community would not be able to pick the baton up and and run with it. Sorry but a definate pile of crud.
So Novell ceased sponsorship of Hula, that doesn't mean they are moving away from community projects, they have managed to get Messaging Architects to take on the sponsorship role and keep the project going albeit in a slightly different direction that some would have liked.
Bongo has managed to pick the baton up when Novell couldn't give a quick enough response to requests, as a new fledgling project I think Bongo has done pretty damn well. We now have a superb looking Wiki - thanks to Sebastian for the final artwork and Luis for making some good comments on the initial work; Michel for setting up the forum; Jonny for doing the documentation; Alex and Patrick for hacking (more hackers required
So in a nutshell LUG Radio - Kiss your chin as you're spouting so much bull!
Unfortunately there are some issues with some distros
The packages available from the Build Service are:
- Fedora Core 5 - x86 only
- SUSE Linux Enterprise 10 - x86 and x86_64
- SUSE 10.1 - x86 and x86_64
- openSUSE 10.2 - x86 and x86_64
I will hopefully have a build for the following shortly:
- Mandriva 2007 - x86 only
- CentOS / RHEL 4 - x86 only
- Fedora Core 6 - x86 only
I'll advertise when the packages are done, and where they are hosted.
From the command line (as root):
rug service-add http://software.opensuse.org/download/home:/FunkyPenguin/[YourDistro] --type=ZYPP "FunkyPenguin-Bongo" or [whatever you would like to call it]
In YaST:
Select Software > Installation Source > Add > HTTP
For Server Name put
software.opensuse.org/
For Directory put
download/home:/FunkyPenguin/[YourDistro]
From ZEN Updater:
Select Configure > Add Service > Select either ZYPP or Auto detect for the Service Type. Enter the following for the Service URI: http://software.opensuse.org/download/home:/FunkyPenguin/[YourDistro]. Enter FunkyPenguin-Bongo or [whatever you would like to call it] for the Service Name.
Or you could use SMART and the .repo file and open the file from within SMART or use one of the above options from within SMART.
If anyone uses any of the other package managers, please let me know how to use it with the repo.
I have expanded the distros built by the openSUSE Build Service in comparison to what I had for Hula. The distros that I am building for via the service are:
- Fedora Core 4
- Fedora Core 5
- Mandriva 2006
- openSUSE Factory
- openSUSE 10.2
- SUSE 10.1
- SUSE 10.0
- SUSE 9.3
- SUSE Linux Enterprise 10
- SUSE Linux Enterprise 9
All packages are signed with the following key.
To get the packages please see here and select the distro of your choice. You can configure your package manager to get the latest package automatically by using the "home:FunkyPenguin.repo" file.
Please let me know if you have any issues, also be a bit patient while the packages get built.
I have expanded the distros built by the openSUSE Build Service in comparison to what I had for Hula. The distros that I am building for via the service are:
- Fedora Core 4
- Fedora Core 5
- Mandriva 2006
- openSUSE Factory
- openSUSE 10.2
- SUSE 10.1
- SUSE 10.0
- SUSE 9.3
- SUSE Linux Enterprise 10
- SUSE Linux Enterprise 9
All packages are signed with the following key.
To get the packages please see here and select the distro of your choice. You can configure your package manager to get the latest package automatically by using the "home:FunkyPenguin.repo" file.
Please let me know if you have any issues, also be a bit patient while the packages get built.






