I’ve dabble with open source involvement for a while and thought it would be beneficial to others to share one’s experience. Hopefully, this may inspire others to follow! In this post one intends to cover the steps I followed to get involved with the Fedora project. The path I have taken focuses on installing the latest Fedora release and testing it. In order to open this up to largest audience I will show how to install Fedora into a virtual environment within a Microsoft Windows environment. Once I have the latest Fedora operating system installed, I’ll discuss some basic testing techniques and hopefully spot a software bug. Once we’ve detected a bug I’ll cover the bug reporting tools used by the Fedora project. From this we’ll hopefully see our testing and bug reporting efforts be assigned to and fixed by one of the Fedora software developers. Heck! We might even open the source code ourselves and generate a software patch to fix the problem.
Getting set-up with a virtualization software package
VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2. It’s important to note at this point that VirtualBox is not the only virtualization product on the market. Alternatives include VMWare Server, Xen, KVM and Microsoft’s Virtual PC. Before we delve any deeper, let me re-iterate that this routine assumes you are running Windows 7 and wish to installed Oracle’s VirtualBox. In theory, this routine should work on earlier version of Windows too.
Download VirtualBox. At the point of writing this post the download page could be found here.