I am very glad to share with you that registration of the eleventh edition of Software Freedom Day has been opened since early August and you can see from our SFD event map, we already have 129 events from more than 50 countries shown in our map. As usual registration happens after you have created your event page on the wiki. We have a detail guide here for newcomers and for the others who need help, the SFD-Discuss mailing would be the best place to get prompt support.
Don’t forget to tell people about SFD! Simply use one of the banners we’ve made if you are organizing, participating, attending or speaking at a SFD event by placing it on your webpages and link it back to your SFD event page or http://www.softwarefreedomday.org. You can also help us to promote SFD by placing our SFD counter with your own language as well!
The open-source x264 program does support OpenCL acceleration -- when building x264 it will check for the presence of OpenCL development support and then at runtime the --opencl switch must be passed for exploiting the potential of any OpenCL hardware. The x264 test profile part of the Phoronix Test Suite is strictly intended for CPU-based testing so this weekend I added a x264-opencl test profile that uses the same revision of x264 and the same media file, but the only difference is that it forces OpenCL support. So now with the Phoronix Test Suite it's as easy as running phoronix-test-suite benchmark x264 x264-opencl to run the CPU-bound x264 and the OpenCL version for easy comparison purposes.
As much as we may like the myth of the hobbyist developer, no one codes for free anymore. Well, not quite "no one," but according to Dirk Riehle's recent academic research, at least half of all open-source software is written by paid developers during work hours. And if Linux is any indicator, the percentage of 9-to-5 open-source development is only going to increase over time.
Recently a major publication house published an article about how the Tizen smartphone "flopped – and open source is to blame" . If you did read the article, however, you found that even the author did not really believe open source was "to blame." The author blamed the companies behind the projects for a lack of commitment to the use of Open Source, which created a lack of follow-through and (given the number of alternative closed and partially open operating systems they could use) the final use of either Android or Microsoft instead. Of course, this headline particularly infuriated me because even iOS is based on FreeBSD, and both Android and Firefox OS use kernels "based on" Linux. So, "Open Source Failed"?
Commonwealth and state/territory government funded public company, Healthdirect Australia, has used open source software to build an identity and access management (IAM) solution.
The IAM solution allows users to have one identity across all of its websites and applications. For example, users can sign in using their Facebook, LinkedIn or Gmail account.
That’s the reason I got away 15 years ago. It’s too bad the world has endured so much harm all these years before coming to its senses. The world now sees that FLOSS works. Just about everyone has used Android/Linux and knows it works. Just about everyone has used web applications running on GNU/Linux and knows it works. The poor souls still using that other OS are locked in miserable dark damp cells peering at a vibrant world outside.
Looking at the challenges—and opportunities—of FarmBot, I'm reminded a bit of the factors that played into the origin of the world's first open source company, Cygnus. That history traces back to 1987, the year that Richard Stallman released version 1.0 of the GNU C compiler. At that time, compiler ports cost millions of dollars and took years to deliver. I was very interested in writing compilers, but I saw no prospect for doing so because (1) there were very few compiler companies in the world, and (2) they employed a very small number of people—most of whom were famous for having written the few compilers I'd ever heard of. Who would hire somebody with no commercial compiler experience to work on something so rare and valuable?
Small business owners and freelancers put a lot of work into their businesses. They do that not only because they’re passionate about what they do, but they also have the goal of getting paid.
That’s no small part of the job, either.
Getting paid usually means sending a client an invoice. It’s easy enough to whip up an invoice using a word processor or a spreadsheet, but sometimes you need a bit more. A more professional look. A way of keeping track of your invoices. Reminders about when to follow up on the invoices that you’ve sent.
There’s a wide range of commercial and closed-source invoicing tools out there. But the offerings on the open source side of the fence are just as good, and maybe even more flexible than their closed source counterparts.
Let’s take a look at four open source invoicing tools that are great choices for freelancers and small businesses on a tight budget.