Feel free to add more questions in the comments!

What is Open Source to you? is it always copyleft?

No, it’s not always copyleft. The core concepts for me are:

Open source, free software and libre hardware products are still copyrighted – but they are licensed differently, allowing re-use and modification. They are ‘some rights reserved’ rather than ‘all rights reserved’. I am not living without copyrighted products – the best way to explain it is that I am avoiding ‘traditionally copyrighted‘ products. There  are a number of different licenses and approaches.

The aim for my project is always to achieve the FSF’s definition of ‘the 4 Freedoms‘, and I plan to evaluate ideas, projects and products on their position in the free->open->closed/nonfree spectrum throughout the year, including whether they are true copyleft, or if they are simply permissively licensed, if they are public domain (NOT open source but still acceptable for my project in most situations) or if they are proprietary.

I am not buying traditionally copyrighted items, but that does not mean that I am throwing out every traditionally copyrighted item in my apartment. I continue to use the products I have, and if possible, find a way to improve or replace them. I am learning about new ideas and projects throughout the year, I have to properly research each topic before making changes.

Free/Libre/Open ideas can be found at various different levels.
In the world of beer, for example, I’ve found beers which provide a link to the recipe on the label. That’s an open source beer, in a way. But on the level of open source beer, you can take it further – others also let you use the beer name commercially, or the branding elements & logo as well as the recipe.
You can go up a meta-level: Premium-Pils is made by a company whose business model is entirely documented and licensed for anyone to replicate – the beer-making business itself is open source.
Alternatively, you could go down a level – there’s an open source spectrometer which can be used to aid and improve yeast cultivation for brewers.

So the project can have a very wide scope – there are few hard rules which must be stuck to at all times – I’m just trying to look at each issue, each area of my life, one at a time, and work out what has been done, what can be done, and working out the best way of documenting it.
I’m also looking specifically for projects and ideas which tell a good story, which explain the core concepts of the philosophy. Rather than covering every single open source project in the world or every single thread of cotton I come in contact with, this is just one person’s journey, and we’ll see how far I get over the year.

So on August 1st you’ll be living totally open source?

From the first of August I will avoid buying any more traditionally copyrighted products, and will start the process of replacing as many of my proprietary possessions as possible.
Obviously I can’t achieve all my aims within the first week. I’ll be tackling issues one-by-one in order to be able to research, get feedback and input, conduct interviews, develop solutions and write up documentation.
The things I use everyday, the clearest solutions and the things I buy regularly will be first.So the first project will be the obvious one – On August 1 I’ll switch to Linux and open source software. Beer has to follow soon after.
This might mean those of you giddy with excitement at the thought of tackling open source refrigeration might have to wait a couple of months while I deal with the issue of an open source cellphone. But of course if my fridge dies in the meantime (which it is constantly threatening to do), then it will cut in to the front of the line, and I’ll have to deal with the issue there and then. This is a one-year process and I hope at the end of the year to be living as open source as humanly possible, while still being connected to the internet, eating food and making videos.

What rules are you setting yourself – what can you still buy?

For fulfilling my project I see it as ‘public domain good, open source better’ – I will use plenty of products whose production patents have expired (eg toilet paper, or dried spaghetti, or a bicycle). I can use these public domain products, but if I can occasionally make explicitly open source versions which explain how something is made and actively encourage others to make or modify their own, all the better. This will often be done to explain the difference between public domain and open source.

Basic materials – textiles and food which are not made or grown from patented seed strains or still covered by patents. Wood, nails, glue etc for DIY projects.

Some of the mining and metallurgy involved in the production of these materials is probably proprietary. The trucks that deliver the food are proprietary. There are all sorts of proprietary processes involved in these not-particularly proprietary materials. This project is not just about seeing how much of an effect open source has on the real world but it’s also a way to show how closed-source and proprietary our current products, lifestyles and production systems are.  I’ll be acknowledging, discussing and examining these issues over the year.

You have proprietary vaccines in your body! You’re not open source!

The aim to live 100% open source is the goal, and it’s a naive and impossible goal. But the project itself is about the attempt. I am interested in the philosophy of open source and free software, and I want to promote it, but I also want to be realistic about it.

I’m going to try to reach that goal, and I will still be trying, even when it makes my life difficult and uncomfortable. I’ll still be trying well past the point any sane person would have given up, gone home and had a warm, proprietary Nespresso.

I realise that there are current limitations, particularly in terms of what open source hardware is available. I’ll be trying to overcome some of these limitations by developing new projects, or outlining the best path towards developing solutions. There are also theoretical limitations – is it even possible to have an open source airline? should we allow modification and redistribution of swine flu?

Whenever I come across hurdles in my path, I’ll be trying various different methods of leaping over them, scurrying under them, or whacking them with a stick. I’ll share my experiences and solutions with the community. Some solutions will require plenty of creativity and lateral thinking. Many will make me look foolish. I am totally ok with this.

What about your Mac?

There has been plenty of discussion on tech sites about how I’m going to deal with the basic problem of my computer hardware. A MacBook Pro is an extremely closed-source machine, packed with patented, proprietary components. And there are no open source equivalents. So I’m going to approach the problem in three different ways:

1) FrankenBook Pro
I’m not going to throw it on a bonfire – I just don’t have the financial resources to go and buy a new computer. Even if I reach my crowdfunding goal, this is still a low-budget, bare-bones production. If you can provide me with a suitable, more open replacement, then sure, I’ll give the Mac to an organisation that needs it (with Linux installed, naturally).
So as well as switching to free software, I’m going to donate its body to science, so to speak – over the year I will try to replace as many of its hardware components as possible with open source components.

2) Simple solutions
I have thought about my computing needs for this project and year, and what I need, at its most basic, is a simple machine for editing videos and connecting to the internet. I want to put together a simple, cheap, and extremely basic computer, that will perform the basic task necessary.
My aim is to work with others – developers, programmers, electronics and hardware experts – to develop a very basic solution to the problem.
Is there a way to hook up a Raspberry Pi with a basic open hardware LCD screen or other monitor and run an extremely simplistic video editing program? even if it is black and white, slow, with seriously crappy resolution, the idea is to provide a test project, something that others can build on to improve.
An inspiration for this kind of project is The Toaster Project – it’s not meant to be a practical solution to the problem but an interesting way to visualize and think about the complexity of the issue.

3) Predicting the future
I intend to conduct interviews with experts on computer hardware and investigate the problems facing development of a suitable open source alternative to a MacBook Pro. What problems remain unsolved? Is there any hope for a better solution in the future?
I’ll present the results of my interviews and research in video and/or writing on the website.

Linux distributions like Ubuntu and Debian have nonfree elements. Firefox has nonfree elements. Does that mean you can’t use them?

Some would say yes. I say no. The intent of my project is to get more people interested and involved in Open Source. Having me bawling my eyes out at how difficult it is to use open source software is not the best way to do this.
Firefox and Ubuntu are good examples of open source software designed with non-technical users in mind, and they are great ways to bring more people into the community. I will not be using only one distro or browser exclusively throughout the year, however. I’ll test-drive plenty, and use different software for different needs.
But what I will do when faced with free software with nonfree elements is be explicit and transparent about the nonfree parts, see if there is any way around them, and raise awareness of the issue so that the developers of the software know it is important and not forgotten.

Why Open Source, not free software? It’s about freedom!

Since starting my campaign I’ve had a few discussions with people about this issue, and at this stage I’m trying to stay relatively neutral with regards to terminology.
The main reason not to use a name referring to ‘free software’ is simply because a huge part of my project, perhaps the majority, is going to be focused on free and open source hardware, which tends to only use the open source moniker. However, I am also using the term ‘libre hardware’. Now I am trying to mostly use ‘free software’ but also ‘free and open source software’ and simply ‘open source’, although that is usually when referring to the general movement rather than software specifically.
The terminology I use will be up for debate early on in the project itself – I want to bring in many opinions to the discussion and work out what I should be saying, or rather how I should be saying it.

What’s special about Berlin as an open source centre?

I see the open source scene as growing from the artistic and tech communities here.

Just speaking economically, Berlin is cheap, as far as rent and food etc goes. But that doesn’t mean life is easy. The city is in a lot of debt, unemployment rate is 12.9%, and there’s no minimum wage.
The low cost of living makes it appeal to startups, which are often in development without much income, for long periods, and also artists, who don’t bring in much money either. But what makes Berlin different from other poor cities is that it is also the capital of one of the richest countries in the world, it’s home to a lot of very rich individuals and companies, and is a key centre of the European union, and therefore, EU funding. So for all those startups and artists, there’s a pretty juicy potential carrot in terms of startup incubators, and national, EU and private funds available for tech and the arts.
When you combine these purely economic reasons with the radical, open and artistic history and culture of Berlin, you get a lot of people who think differently, who think critically, and who have the time, technical skills or the ingenuity to put together interesting projects. People save money and find community by working in co-working spaces and hackspaces, and this tends to encourage openness, collaboration and sharing of ideas.

There are many other cities with strong, distinct open source scenes, particularly in North America, but Berlin really has so much going on in so many areas of open source, whether software, hardware, politics, education, and here you have a wider mixing of cultures and approaches. There tends to be a strong bias in tech reporting and open source on English-language and American-based projects, for cultural, practical and historical reasons. (this article is definitely worth reading for a nice summary). Being based in the middle of Europe like this provides a good opportunity to show off some of the wonderful work being done in other cultures. There’s still a bias, I mean, I’ll probably have more of a focus on Germany and Spain just because theirs are the only other languages I speak well enough to engage with people, but I’m much more likely to highlight Dutch, Polish, Danish and Czech stories as well, simply because of geographic proximity.

6 thoughts on “FAQ”

John says:

July 15, 2012 at 12:52 am

I appreciate the idea but what about the film simply in terms of photography equipment alone. There you have a heap of problems. The only open source camera is not completely finished but I guess you should check out and use http://apertus.org/ What about lighting? Not sure there any yet but who knows?

yearofopensource says:

July 15, 2012 at 9:42 am

Hi John, yes, it is a problem – the apertus camera is a project which I’ve been following, and I hope to meet up with the team and make some videos with them, and see if we can develop a basic solution. Another approach is hardware and firmware hacks of my Canon DSLR – I don’t know how possible it is to avoid H.264 yet but I’d like to discuss it and see if anyone can help me find a solution. Camera rigs are all over instructables.com, so that won’t be a problem, and I’ll get in touch with Open MoCo to show people what they’re up to and what their projects can do. For lighting I’m pretty excited about the possibilities of RiftLabs’ work – they’ve released the Kick, which is a little consumer version of the Flynn light, a more professional, programmable, wifi controllable and open source light.

John says:

July 15, 2012 at 2:16 pm

For delivery you can avoid H264 by using ogg vorbis codec. That will mean hosting it in your own player though on your own site. This hosting provider in iceland (1984.is) only uses open source software for its hosting services. Of course, the information will travel between there and the user via many routes which use proprietary equipment and software but at least your end is ‘clean’ which is all you can control.
blender.org has a basic editor and compositor in it even though its a 3D program, you can use it for 2D stuff (image on a plane).
A hacked canon or GH2 doesn’t really count. Camera hacks are not complete rewrites, just patches I think. The hardware is also mostly proprietry. apertus is the only option there and must be usable at least as there are already footage tests.

yearofopensource says:

July 15, 2012 at 2:31 pm

Hi John, at this stage I’m planning to host open codecs on GNU MediaGoblin.
I would love to use an apertus for all my video needs but at this stage its estimated to cost at least $10,000 – as I explain with regards to the computer, this just isn’t possible unless somebody wants to donate one. I’ll be taking a similar approach to the MacBook Pro for the camera – any hardware hacks (not just firmware hacks) possible, trying to create a basic version, and interviewing, testing and experimenting with the Apertus team, outlining the possible future of open source cinema cameras.

yearofopensource says:

July 15, 2012 at 9:45 am

Sorry, I forgot the link to RiftLabs, and got the name wrong: It’s called Floyd. http://riftlabs.com/whats-the-big-idea/

Ana says:

August 10, 2012 at 5:41 pm

Hi ! Debian “main” doesn’t have non-free components. If you don’t add the “non-free” repository, your Debian system will be 100 % free per Debian Free Software Guidelines. Cheers and courage!

Comments are closed.