Getting Started with SparkleShare
If you follow Linux-related news, you've probably heard about SparkleShare, a promising open source alternative to the popular Dropbox service. SparkleShare has been under active development for some time, but the latest 0.2.2 release is actually the first version suitable for practical use. Mind you, it's far from ready for production use, so install it only if you want to satisfy your curiosity, or if you enjoy using bleeding edge releases.
While you can find .deb SparkShare packages in the wild, your best bet is to compile the software from source. This is a rather straightforward thing to do. First off, you need to install the required dependencies. On Ubuntu, this can be done by executing the following command:
sudo apt-get install gtk-sharp2 mono-runtime mono-devel monodevelop libndesk-dbus1.0-cil-dev nant libnotify-cil-dev libgtk2.0-cil-dev libwebkit-cil-dev intltool libtool python-nautilus libndesk-dbus-glib1.0-cil-dev libappindicator0.1-cil-dev
Grab then the latest source package from the project's website, unpack it, switch to the resulting directory in the terminal, and compile the software using three simple commands:
./configure --prefix=/usr make sudo make install
Next step is to set up a Git repository. Although SparkleShare can use GitHub and Gitorious as its file storage back-end, setting up a Git repository on your own server makes a lot of sense. It is also a rather straightforward process, and the How to set up your own server wiki page provides detailed instructions.
With all the pieces in place, launch SparkleShare using the sparkleshare start command. When prompted, specify your server's address in the following format: user@remotehost. Enter then the pass to the Git repository on your server like this: /path/to/dir/repositoryname.git. Press Finish and you are done. Repeat the setup process on other machines.
Don't encourage Mono usage. Mono is a legal risk and a patent threatI would appreciate it if Linux Magazine would show some serious restraint when it comes to writing about Mono or any apps that require Mono. Judging from the ton of information and analysis in techrights.org Microsoft has a legal basis to sue anyone using Mono & Mono based apps. Do you want to subject your readers to that risk? Not even De Icaza has been able to refute that Mono is a legal risk and patent threat. And Ubuntu or Canonical do not seem to provide any sort of indemnification against such a legal threat. Red Hat's decision with regards to Mono and Mono based apps should tell you something. In our Community Friends do not let Friends run legal risks, right?
New release comes with better semantic search and improvements to Kontact.
Annual code quality report shows FOSS is more secure at all project size levels.
The Raspberry Pi Foundation has announced an even smaller version of the tiny computer that will fit into a DIMM slot.
A new class of problems lets a malicious app pre-configure an invisible privilege update.
New Hack language adds static typing and other conveniences.
New crypto policy system will offer easier configuration and more uniform security.
Ubuntu founder denounces insecurity in proprietary, close-source software blobs.
Vulnerability affects many Linux web servers
The Bavarian capital shuns Microsoft, Google, and other alternatives to implement an open source groupware solution.
Phone vendor partnerships bring Mark Shuttleworth's dream of Ubuntu on a phone a step closer to reality.