Tag Archives: OSS

Wannabe nix guru starting a new os

By donkey42

after much searching around there isn’t a “TOSS” (True Open Source) solution, personally I did like OSS however now i believe that “so called” Free Software should be free & Free From any license restrictions

so as I feel that way I’ve decided to write new OS and I was thinking of basing it loosely on the Downloadable Solaris source code, or maybe someone could suggest a better base, I don’t expect it will be very popular, I just happen to think that people (namely me) deserve a truly free OS

I also on hardwarefofums.com here:

Code:

http://www.hardwareforums.com/threads/oss-open-source-software-what-a-joke.38264/


a while ago so you know it’s not a pie in the sky idea that will never take flight

I’m also thinking this would be a very good way to learn how nix works practically
I know this will be hard very bumpy road to travel, so i appreciate any help / advise offered

thank you very much for taking the time to read this,

thankies xxx

…read more

Source: FULL ARTICLE at The UNIX and Linux Forums

James Hunt: Coverity static analysis for C, C++ and Java code

It’s a well known principle of software engineering that the earlier bugs can be caught, the lower the overall cost. As such, testing needs to happen at every level. Once your project is at the coding stage, the earliest form of testing is on the code itself, not on the binaries the compiler produces.

We run a variety of tools over critical codebases such as Upstart and Whoopsie regularly to identify issues well before they “escape into the wild”. These tools include Coverity Scan (see the list of projects already using it).

If you really care about your code and you are involved with a C, C++ or Java project, I’d strongly encourage you to take a look at this awesome tool. If you aren’t directly involved in such projects, try contacting those running them and suggesting they use Coverity.

The Coverity Scan service is entirely free for OSS projects. You will need to register to obtain an account and then download the client analysis tool. Once setup, a particularly attractive feature is the ability to auto-upload the analysis data generated for your project using ESR’s coverity-submit tool. This could for example be hooked into your upload or release process to ensure no code quality regressions. After you have uploaded the analysis data, you can browse through the results of the scan using the web interface in a variety of ways, including a view that shows the errors “inline” with markers added around the code Coverity has identified as problematic.

For those who have either never used static analysis tools, or have simply never used Coverity, don’t fall into the trap of thinking that gcc -pedantic -Wall or even LLVM‘s scan-build should be “good enough for anyone” – it simply is not. Consider too Steckel’s Rule to Success,

“Good enough is never good enough”

Coverity performs very deep analysis and its results may well surprise you… but rather that than unexpected surprises for your users.

Apologies if this post sounds like a bit of a sales pitch. It really isn’t though: the Coverity service is free and what they are offering really is too good to ignore.

Note: I have no affiliation with Coverity – I’m just extremely impressed with their Scan tool! 🙂

…read more

Source: FULL ARTICLE at Planet Ubuntu

Roadpost Satcom Inc. Deploys LogiSense EngageIP Billing and OSS to Consolidate Systems and Enhance t

By Business Wirevia The Motley Fool

Filed under:

Roadpost Satcom Inc. Deploys LogiSense EngageIP Billing and OSS to Consolidate Systems and Enhance the Customer Experience

LogiSense EngageIP Billing and OSS Platform and BillSoft EZTax combine to Consolidate Billing, Rating, Taxing, Service Fulfillment, and Customer Care for Roadpost Satcom

CAMBRIDGE, Ontario–(BUSINESS WIRE)– LogiSense Corporation, a global provider of Billing and OSS software, services, and solutions to the Telecom, Hosted Communications, Convergent, and Broadband industries is proud to announce that Roadpost Satcom Inc., a Canadian leader in the distribution of mobile satellite products and services, has chosen to deploy the LogiSense EngageIP Billing and OSS platform.

The project will automate and manage operational processes and business rules, improving product and service fulfillment reliability, billing, rating, invoicing, taxing, and customer self-care.

EngageIP Billing will connect to Roadpost’s online commerce portals creating seamless handling of customer transactions, account information, synchronization, product fulfillment, trouble ticket case management and most importantly, an enhanced experience for the customer.

“Consolidating our systems onto a single platform to provide a true holistic view of our clients is a critical and key benefit of using EngageIP Billing,” said Morris Shawn, President and CEO of Roadpost Satcom. “It allows the flexibility to tailor service rating options to our business requirements, open new directions for future growth, and ensure customer loyalty.”

“EngageIP offers rapid time-to-market for new services, and cost reducing automation, creating a sharp competitive edge. Customer loyalty grows with granular and tailored service offerings,” said Flavio Gomes, President of LogiSense Corporation. “LogiSense is pleased to collaborate with Roadpost to extend its mobile and e-commerce inventory, and to empower their vision of next-generation service deployment.”

LogiSense’s technology integration with BillSoft’s EZTax product has also been successfully deployed by Roadpost. Adding EngageIP Billing and EZTax to the conduit offers a leading edge Billing and Taxation system to accurately and efficiently rate, tax and manage Roadpost’s satellite service offering.

“The partnership between LogiSense and BillSoft has been exceptional for a number of years,” said Tim Lopatofsky, CEO of Billsoft. “We want our relationship to benefit mutual customers and the addition of Roadpost exemplifies the value of our partnership.”

LogiSense empowers clients with proven innovative resources, technical expertise, and unmatched support, resulting in effective design, management and building of solutions that monetize.

LogiSense’s flagship software, EngageIP Billing and OSS, is renowned for field-proven features and functionality that address every aspect …read more
Source: FULL ARTICLE at DailyFinance

Benefits of co-existing open source & commercial software

Authors: Tuukka Turunen (Digia), Mirko Boehm (KDE e.V.)

[This article was initially published at embedded.com. It is part of the “Companies are Community” series.]

In the world of software development the many debates about the benefits of open source versus commercial software continue, with developers, software manufacturers, users and purchasers all putting forward differing opinions and, sometimes, protecting vested interests.

However, as with most things in life, the argument is not black or white but has many shades of grey. Different models and arrangements mean that open source software may be available without license cost or as part of a larger commercial framework offering with a separate licensing scheme.

But the two approaches are not mutually exclusive – in many cases not only can commercial and open source offerings comfortably co-exist, but they actually strengthen both the product offering and the community to which the system designer can turn for support.

Growth of Open Source

Since its inception and promotion under the banner of the ‘free software movement’ in the 1980s the use of open source software (the more corporate-friendly term by which it became known in the 1990s) has grown rapidly.

Typically covered by licensing arrangements that permit the inspection, modification, improvement and distribution of the source code, open source software (OSS) can now be found in applications ranging from industrial machines to medical equipment and from consumer electronics to defense systems.

Among the various benefits stated for using OSS are cost (it is typically available for free), flexibility of deployment and lack of reliance on a single vendor.

Counter points from the proprietary community also focus on cost (one argument being that the need for organizations to invest in technical expertise and/or long-term technical support mean that deploying an OSS is rarely free).

Without a commercial development and support effort, an organization might end up maintaining the whole OSS product itself, which could be more expensive than a proprietary approach in the long term. Lack of documentation and copyright and trademark protection risks of using open software are also regularly raised.

However, for most of the exponents of OSS, by far the largest advantage is the support of (often passionate) communities whose aim is to work together to continually improve the quality, performance, reliability and flexibility of their chosen product.

These communities not only work as technical consultants for the software, they also provide code contributions, are vocal ambassadors for the brand and educate valuable young talent to create the product and new technology in general.

Our experience is that commercial companies and open source developers can form highly beneficial, symbiotic relationships that enable users to have the best of both worlds, provided that both sides are committed to a long term relationship, and are open about their goals.

Companies can be contributors to open source software projects, just like volunteers, but their contributions are usually of a different kind. The contributions needed by the projects can generally be categorized into time, money and expertise.

It is easier for companies to contribute financially, …read more
Source: FULL ARTICLE at Planet KDE

A new Debian-based distribution

Debian Development

Disclaimer: This post just sums up a concept for a new distribution which matches certain ideals. It is not the announcement of a new distribution. These are just abstract ideas. (However, if there is high interest in a project like this, it might of course develop into something real…)

I have been involved in Debian and Ubuntu for a long time now. When Ubuntu started, I was a Debian Testing user, and I immediately switched to Ubuntu when it started, because I liked the idea of a short-release-cycle, user-centric company-supported Debian based Linux distribution. However, I am now back to Debian for a long time, because of many reasons which nearly all had to do with Canonical policy. But this is not a post to criticise Ubuntu, so I’ll leave out most of that part. I am highly disappointed on how Ubuntu develops – not only the technical decisions are at least questionable, but also the social and community part is not that great anymore. There is a high asymetry in the relation between Canonical and other developers, Ubuntu mailinglists basically don’t create meaningful results, they sometimes even mutate to a Canonical Q/A session. The community does not seem to have a large influence on decisions about core services, and it can’t have it if there are things developed behind closed doors. (This is all, of course my subjective impression)

But really nobody can argue against the basic idea of Ubuntu and the great things Ubuntu created Also, many of the processes Ubuntu uses to develop the distribution are just great and well-working, as well as there is a highly active community around it. As you simply cannot argue with Canonical to change their policy (they are a company and have hidden plans, also they have every right to apply whatever policy they want), the natural way in any OSS project would be to fork it. But doing that blindly would just create another distribution, which would almost certainly vanish again soon, since there are already many Ubuntu derivatives which cover many use-cases using an Ubuntu base.

I discussed this stuff with Daniel some time ago, and we did some kind of brainstorming about what a perfect distribution would look like, from the perspective of a developer who wants to use a Debian-based distribution.

Here is a list of points which would define such a project:

  • Every available package complies with the DFSG and Debian policy.
  • Packages of DISTRO stay in close sync with Debian packages, changes are preferrably applied in Debian. DISTRO might work as a playground for new technology while Debian is in freeze.
  • DISTRO stays as close to upstream as possible. It applies as less patches as possible, to deploy desktop environments which look like the thing upstream intended it to look like. Changes for DISTRO are developed upstream and only applied downstream if doing that doesn’t make sense or changes are distribution-specific and can’t be abstracted.
  • All desktop environments are treated equally. There is no preferred DE.
  • DISTRO stays in sync with release …read more
    Source: FULL ARTICLE at Planet KDE

Kwave 0.8.10 (KDE Sound Application)

Thumbnail

Kwave 0.8.10
(KDE Sound Application)
Kwave is a sound editor designed for the KDE Desktop Environment.

With Kwave you can edit many sorts of audio files including multi-channel files. Kwave also includes many plugins to transform the audio data in several ways and presents a graphical view with a complete zoom- and scroll capability.
Supports many sound formats, playback and recording via ALSA and OSS.

changelog:
0.8.10 [2013-02-09]

* support for Ogg/Opus codec
* bugfix: unwanted termination if splash screen closed while the first
toplevel widget still was starting up
* improved auto detect of svg-to-png conversion,
added support for “rsvg-convert” (SF bug #38)
* increased default memory sizes
* some GUI improvements

[read more]

job recommendations:

Sales Engineer full time employee
ownCloud Inc. United States of America, Boston more about this offer

[more jobs]
…read more
Source: FULL ARTICLE at KDE Apps