IP Voice 2008 (http://www.ipvoice2008.com/eng/index2.php) will be held in Lisbon, Portugal on March 5th to 6th, 2008, and with the main audience of this conference being targeted to enterprise customers and communication carriers.
There have been a number of Open Software Phone projects that have happened in the past year and which continue to move forward: more>>
Unlike a lot of the events that I discuss in my Blog, the Linux Foundation Collaboration Summit is a "by invitation only" event with a twist. Normally for "invitation only events", the potential attendee sits by the phone with their prom clothes on, waiting for the call that may or may not come. more>>
After speaking at the Florida Linux Show on February 11th, I return ever-so-briefly to the New England area to re-pack my bags and head for Sao Paulo, Brazil to attend Campus Party (February 11th to 17th, 2008). more>>
What's bad about Eventbrite.
Forecasts of a high rate of US oil and gas extraction turn out to be based on oil company figures that were designed to attract investors. The real potential is much less.
If the worst problem we faced was that oil and gas might become expensive, this would be bad news. However, this is good news since it will encourage investment in renewable energy and energy efficiency.
Shell asked the US for a 5 year extension in trying to do dangerous underwater oil drilling in the Arctic.
Join the FSF and friends on Friday, October 31, from 2pm to 5pm EDT (18:00 to 21:00 UTC) to help improve the Free Software Directory by adding new entries and updating existing ones. We will be on IRC in the #fsf channel on freenode.
Tens of thousands of people visit directory.fsf.org each month to discover free software. Each entry in the Directory contains a wealth of useful information, from basic category and descriptions, to providing detailed info about version control, IRC channels, documentation, and licensing info that has been carefully checked by FSF staff and trained volunteers.
While the Free Software Directory has been and continues to be a great resource to the world over the past decade, it has the potential of being a resource of even greater value. But it needs your help!
If you are eager to help and you can't wait or are simply unable to make it onto IRC on Friday, our participation guide will provide you with all the information you need to get started on helping the Directory today!
In this edition, we conducted an email-based interview with Jessica Tallon, the lead developer PyPump, a simple but powerful and pythonic way of interfacing with the pump.io API, which is licensed under the terms of the GNU General Public License version 3 or, at your option, any later version (GPLv3+).
What inspired you to create PyPump?
I began working on PyPump when Evan Prodromou launched the first pump.io servers. Although Status.net had existed before pump.io, I wasn't a user and the only social networks I used were centralized, proprietary ones which really clashed with my views on software freedom and the federated web. I wanted to be able to interact with pump without having to use a browser. The API was easy to understand, so I tried to see if I could put together a basic library.
How are people using it?
There are several interesting projects out there which use PyPump. With my day job as a GNU MediaGoblin developer, we're going to be using it as a way of communicating between servers as a part of our federation effort. A great use I've seen is PumpMigrate, which will migrate one pump.io account to another. Another little utility that I wrote over the course of a weekend is p, which was made to be an easy way of making a quick post, bulk uploading photos, or anything you can script with the shell.
What features do you think really sets PyPump apart from similar software?
One thing PyPump does particularly well is being pythonic. We've written PyPump to be as natural for the python developer to work with as possible. Hopefully, that will lower the bar of entry for developers, as they won't have to read through the pump.io API documentation or be intimately familiar with Activity Streams in order to write great applications that can interact with pump.io.
Why did you choose the GNU GPLv3+ as PyPump's license?
This is actually something I get asked a lot and something which I have spent a lot of time thinking about. PyPump is a library and most people expected me to release it under the GNU LGPLv3. The reason I went with the GNU GPLv3 is that I believe that all software, regardless of size, should be free - so that we can all learn, build, fix, and use the software in whatever way we see fit. GPLv3 gives everyone the protection against someone coming along and using all that great work and writing proprietary code against it.
How can users (technical or otherwise) help contribute to PyPump?
There is so much people can do to help. We would love to get help both on the library, as we're currently working towards our 0.6 release, as well as on documentation. With PyPump being a library, we want to make sure that we have accessible, good quality documentation so that the people who want to use PyPump can. Writing software that uses it is also a great way of contributing!
What's the next big thing for PyPump?
The next big thing is our 0.6 release, in which we're aiming to provide much better documentation, better storage interaction, and a much more stable API to write against. I think some of the most exciting things won't be what we add to PyPump, but, rather, what other developers will create with it. I'm really looking forward to it being used in more ways.
Enjoyed this interview? Check out our previous entry in this series featuring Alan Reiner of Bitcoin Armory.
FreeIPMI 1.4.6 - 10/29/14
o In ipmi-fru, support output of DDR4 SDRAM modules.
o Fix EFI probing on non IA64 systems.
o Fix corner case in ipmi-raw w/ standard input or --file and empty lines.
o Fix parsing corner case in ipmi-chassis.
o Support SSIF bridging.