The Wayback Machine - https://web.archive.org/web/20170617085226/https://sourceforge.net/blog/
Advertisement

Open Source Project Branding: Lessons from the Pros

Is branding important for open source projects?

As exemplified by such big open source brands as Linux, Mozilla and Firefox, branding does matter. It defines how your project will be seen by the world, helps to differentiate your project from the rest and gets your project to stick in people’s minds. And it’s even more important when you consider what open source projects are often up against.

Proprietary software, though many of which are already integrated with open source parts, are still open source software’s biggest competitors. In order to compete, open source software projects must appear as more viable alternatives to paid software, and proper branding can help with that.

Elements Proven to Work

Many of today’s most successful open source projects can teach us a thing or two about branding. Take for instance Linux, with its famous penguin mascot Tux.

Tux was created by Larry Ewing at the suggestion of none other than Linus Torvalds himself. At the time of brand conceptualization, Torvalds had a fixation of penguins after he was bitten by one in an Australian zoo. He wanted a fun image to represent Linux, and thus, Tux the penguin was born.

Tux the penguin is a great example of how a personal story can help define an entire brand, and is also an example of one element that almost always works well for branding: animals.

Countless projects have proven animal logos and mascots to be effective for branding. Examples include Linux’s Tux the penguin, Firefox’s red panda and GIMP’s Wilber the GIMP (although exactly what animal GIMP is, no one can really say for sure).

This doesn’t mean however that you should immediately choose an animal to represent your brand. Of course, the animal or symbol that you choose must still have some relevance to you or to the project, be it a symbolic connection or a personal story.

Involving the Community

To ensure that a brand is well-established and received by the general public, a lot of projects involve their communities in deciding what goes into their brand. This is another great idea, but projects should be careful to go about this in the right way.

According to Chris Grams, President and Partner of tech branding agency New Kind, involving people in brand creation pays off because “If you invite people along on the journey, they are more likely to embrace the destination.” However, he notes that when involving people it’s better to establish a meritocracy instead of a democracy. But exactly what is the difference?

In a democracy, project leaders would give brand options to people and ask them to vote on the option they like the most. This would seem like a good idea initially, until the people decide to vote on the project team’s least favorite option. In a meritocracy on the other hand, this situation never has to happen. Instead of letting people vote on the final brand, a core group within the project is in charge of branding. They simply get the people’s input on how they think the final brand should be, and the core group decides on the final brand based on this input. The key difference here is instead of the people making the final decision, the core group within the project makes this pivotal decision and the community is only there to provide input and inspiration.

But this can only work if the original sources of inspiration and ideas are given credit. When people see that their own ideas are there and recognized in the final brand and that the brand is truly a result of the entire community’s input, the more likely they are to embrace it.

It’s an Evolution

Sometimes it takes a rebrand, like the Mozilla Foundation’s rebrand, to get a brand that’s an even better fit for the project. Sometimes, a brand may have to change several times.

Take for instance Firefox. Firefox was originally nicknamed “Phoenix”, as it had risen from the ashes of Netscape Navigator. Due to trademark disputes it later became Mozilla Firebird, but because of the confusion it caused with the Firebird RDMS project, it finally settled on Mozilla Firefox. Its icon also underwent a similar evolution.

Though it took a while and several changes for Firefox to get its final brand identity, based on its current standing it’s clear to see that it was all worth it in the end. This goes to show that sometimes, it can take some time and a handful of changes to achieve the right brand identity.

In summary, based on existing successful open source brands it’s a good idea to use elements such as personal stories and animals in your brand so long as they remain relevant to the project. It’s also good to involve the community when coming up with a brand identity as long as you establish a meritocracy rather than a democracy. Finally, remember that branding is not always a one time thing. It can be an evolution or it can take several rebranding efforts before you can achieve the brand that’s just right for your project.

Today in Tech – 1941

On this day in 1941 computer pioneers John Mauchly and John Atanasoff met in Iowa City to see Atanasoff’s latest creation, the Atanasoff-Berry Computer or ABC. This event is particularly significant because of the events that followed some 30 years later, when the two became embroiled in a legal battle over who would be deemed the legal inventor of the first electronic digital computer. Mauchly along with his partner J. Presper Eckert were first to file for a patent on a digital computing device (ENIAC), much to Atanasoff’s surprise. At the end of the court battle however the ENIAC patent was deemed invalid, with the judge explicitly stating, “Eckert and Mauchly did not themselves first invent the automatic electronic digital computer, but instead derived that subject matter from one Dr. John Vincent Atanasoff.”  Atanasoff emerged as the victor and was credited for inventing the first electronic digital computer.

The Atanasoff-Berry Computer, the first official automatic electronic digital computer. -Image taken from computerhistory.org

The Atanasoff-Berry Computer, the first official automatic electronic digital computer. -Image taken from computerhistory.org

Projects of the Week, June 12, 2017

Here are the featured projects for the week, which appear on the front page of SourceForge.net:

UNetbootin

UNetbootin allows you to create bootable Live USB drives for Ubuntu, Fedora, and other Linux distributions without burning a CD. It runs on Windows, Linux, and Mac OS X. You can either let UNetbootin download one of the many distributions supported out-of-the-box for you, or supply your own Linux .iso file.
[ Download UNetbootin ]


Lazarus

The Lazarus IDE is a stable and feature rich visual programming environment for the FreePascal Compiler. It supports the creation of self-standing graphical and console applications and runs on Linux, FreeBSD, MacOSX and Windows.
[ Download Lazarus ]


usm

Usm is a unified slackware package manager that handles automatic dependency resolution. It unifies various package repositories including slackware, slacky, ponce, salix and alien. It also supports slackbuilds.org and will build from source.
[ Download usm ]


MPC-BE

Media Player Classic – BE is a free and open source audio and video player for Windows. Media Player Classic – BE is based on the original “Media Player Classic” project (Gabest) and “Media Player Classic Home Cinema” project (Casimir666), contains additional features and bug fixes.
[ Download MPC-BE ]


HP Linux Imaging and Printing

The Hewlett-Packard Linux Imaging and Printing Project provides a unified single and multi-function connectivity solution for Linux. For support and help, please visit https://launchpad.net/hplip
[ Download HP Linux Imaging and Printing ]


VoIP monitor

VoIPmonitor is open source network packet sniffer with commercial frontend for SIP SKINNY RTP and RTCP VoIP protocols running on linux. VoIPmonitor is designed to analyze quality of VoIP call based on network parameters – delay variation and packet loss according to ITU-T G.107 E-model which predicts quality on MOS scale. Calls with all relevant statistics are saved to MySQL or ODBC database. Optionally each call can be saved to pcap file with either only SIP / SKINNY protocol or SIP/RTP/RTCP/T.38/udptl protocols. VoIPmonitor can also decode audio.
[ Download VoIP monitor ]


Maxima — GPL CAS based on DOE-MACSYMA

Maxima is a computer algebra system comparable to commercial systems like Mathematica and Maple. It emphasizes symbolic mathematical computation: algebra, trigonometry, calculus, and much more. For example, Maxima solves x^2-r*x-s^2-r*s=0 giving the symbolic results [x=r+s, x=-s]. Maxima can calculate with exact integers and fractions, native floating-point and high-precision big floats. Maxima has user-friendly front-ends, an on-line manual, plotting commands, and numerical libraries. Users can write programs in its native programming language, and many have contributed useful packages in a variety of areas over the decades. Maxima is GPL-licensed and largely written in Common Lisp. Executables can be downloaded for Windows, Mac, Linux, and Android; source code is also available. An active community maintains and extends the system. Maxima is widely used: annual direct downloads exceed 300,000. Many other users receive it through secondary distribution.
[ Download Maxima — GPL CAS based on DOE-MACSYMA ]


KaOSx

An independent small, rolling distribution, fully focused on KDE/Qt. Using pacman as package-manager.
[ Download KaOSx ]


phonegap-50 PhoneGap Desktop

PhoneGap Desktop is the easiest way to get started using PhoneGap, the open source framework that gets you building amazing mobile apps using web technology. It provides a drag and drop interface for creating PhoneGap applications. Use it to create apps and serve those apps to connected mobile devices- no need to memorize commands or install dependencies as these are all included when you download PhoneGap Desktop.

PhoneGap Desktop is an alternative to PhoneGap CLI for those who prefer a visual user interface over a command line interface approach.
[ Download PhoneGap Desktop ]

The Next Big Step Software Developers Need to Make

“Open source won. It won because it’s used everywhere now. But now we have a supply chain problem we need to start thinking about and that is, where did you get it and how is it being taken care of?”
~John Bressers, Red Hat Cybersecurity Strategist

The statement “open source software is better than proprietary software” may just be null now. Just ask John Bressers, the cybersecurity strategist for Red Hat. In an interview with InfoWorld Bressers stated, “The concept of proprietary software doesn’t really exist anymore because virtually every organization has open source inside of the products they’re building.”

Open source is virtually everywhere. It’s omnipresence is no longer questioned. The question that developers need to ask themselves now is, what next?

A Kink in the Chain

According to Bressers, the next thing that developers need to focus on is recognizing open source software as a part of the supply chain, and handling this part in the best possible way. Currently there remains an old mindset where developers can simply go out and find the open source components they need, pull them in and that’s that.

Aside from the fact that this completely ignores the communities on which open source projects are built, this can be very dangerous for end products. With low quality, unmonitored open source code inside them, there are bound to be security issues down the line.

This is why, according to Bressers it is important for developers to look at software development as more of a supply chain. In the supply chain you have vendors providing you with the parts you need to finish your product. If you get low-quality parts, you’re most likely to get a low-quality product. Likewise, in software development if you get low-quality open source code or software, you’re very likely to end up with a low-quality product.

The Next Big Step

Following the supply chain format it becomes clear that there are certain measures that need to be in place to keep developers from encountering the same problem. Essentially Bresser notes, you should have a vetting process to make sure that any software you use is top-notch, updated and won’t lead to problems in the future. This vetting could include automated and manual source code scanning, and using tools and systems that will analyze the things you put in and build, and how you build them.

Bressers also suggests either of the following:

  • Have a team dedicated to understanding where your open source code comes from, ensuring its quality, and keeping it updated and working as it should. This team will have to be involved in the open source software community.
  • Work with a vendor that can be your representative in these matters, do all these things for you and will make sure you understand any changes and their implications. You would still have to get involved with the community at some level.

It’s crucial that developers learn to participate in open source communities and not just take what they need from them. It’s a stone that may seem weighty at first, but actually hits two very important birds: it ensures the security of the software they build, and keeps open source software communities alive and well-supported.

Today in Tech – 1954

This day in tech history is a very sad one, as it was on this day in 1954 that English computer scientist, mathematician, logician, cryptanalyst and pioneer Alan Turing passed away. Turing is largely considered the father of theoretical computer science and artificial intelligence. He originally conceived the idea of a machine that could turn thought processes into binary numbers. He also worked at Britain’s codebreaking centre Bletchley Park during World War II, leading a team that was responsible for German naval cryptanalysis. He played a pivotal role in deciphering encrypted German communications, giving the Allies the critical information they needed to defeat the Nazis.

In 1952 Turing was prosecuted for homosexual acts, which at the time was a legally-punishable offense. At the threat of imprisonment, he agreed to a chemical castration treatment instead. Two years later on this day he was found dead in what appeared to be a suicide through cyanide poisoning. In 2013 Queen Elizabeth II granted him a posthumous pardon, and the Alan Turing law is now the informal term for the 2017 law that retroactively pardons those cautioned or convicted under historical legislation that outlawed homosexual acts.

Alan Turing - Image taken from princeton.edu

Alan Turing – Image taken from princeton.edu