Posts Tagged ‘Free Software’


After the post about code_swarm, here’s another post about the visualization of Open Source communities, and this time I’m going to introduce you the other important software for this task: Gource. code_swarm and Gource are the most complete softwares rigth now for visualizing activities in a repository (and both are open source); there are of course other scripts or strategies, but less important, so I will cover them in the future.

But while with code_swarm it’s easier to see how the community grows and change shape, with Gource we can have a better look at what the users are actually working on. Instead of focusing on the form of the community (be it a social network or another visual metaphor), Gource focuses on the form of the software being developed, analysing it as network of interacting pieces of code. We can then see where the users actually work and we can also see them in a better way than with code_swarm (Gource supports the use of Gravatars for visualizing the users).
(more…)

Share

After the first movie, here is another one, that maybe you have already discovered while reading the Wikipedia page of Revolution OS. It’s “The Code”, a Finnish-made documentary about Linux from 2001, featuring some of the most influential people of the free software movement. It’s in English with Finnish subtitles (and some small parts are in Finnish).

Share

Back from the November tour and a change of server, rigth now I’m working on opening new sections in openp2pdesign.org, on redesigning the theme and the structure of the whole website and on opening openp2pdesign.org to more participants. As you may understand with this post, I will post only in English now, because it takes too much time to write also in Italian and Spanish at the same time; maybe in the future I will write in those languages again.
Meanwhile, the Twitter page, @openp2pdesign, is still a great place to get news and resources at the same time. And there is also a Facebook Fan Page, for further informations and interactions:

openp2pdesign.org | Promote Your Page Too

So, while you wait for the new website and for new posts, I will post some videos, so you will not get too much bored.
Let’s start with “Revolution OS” a 2001 documentary film which traces the twenty-year history of GNU, Linux, open source, and the free software movement. You can watch it on Google Video or right here:

Share

After the first book and the second one about managing Free Software / Open Source projects, here you can find the third one: “Innovation Happens Elsewhere. Open Source as Business Strategy” by Ron Goldman and Richard P. Gabriel.

This is an online version of our open source book based on the version published by Morgan Kaufmann in April 2005. We post it online in the hopes that people will find it useful. Feel free to link to it.

This book is intended for anyone considering using Open Source. It describes what open source is, discusses business reasons for using open source, and describes how an open source project works in a day-to-day manner. It will help you decide on whether open source is right for your project, and, if so, what steps you should take to proceed and some mistakes you should avoid.

.

Share

After the first book about managing Free Software / Open Source projects, here you can find another and older (2002) methodology for managing a free software project: Free Software Project Management HOWTO, by Benjamin “Mako” Hill.

As I said before, this kind of guides are important as inspiration for open p2p projects, especially if we se them up using the web and networked software as the most important part of the collaborative activity’s platform.

This HOWTO is designed for people with experience in programming and some skills in managing a software project but who are new to the world of free software. This document is meant to act as a guide to the non-technical aspects of free software project management and was written to be a crash course in the people skills that aren’t taught to commercial coders but that can make or break a free software project.

.

Share

"Producing  Open Source Software. How to Run a Successful Free Software Project" (Karl Fogel)"

Here is the first of three books about how to manage a Free Software / Open Source community and process that are freely available online. They are very important for two reasons: they represent a good introduction to how Free Software / Open Source projects work, and they can be very useful resources in the organization of an Open P2P Design project. With their explanation of copyleft licenses, processes and tools we can always take a look at them while designing an open p2p project.

The first book is “Producing Open Source Software. How to Run a Successful Free Software Project” by Karl Fogel, available here under a Creative Commons license. This book is a practical guide, not an anthropological study or a history of Free Software / Open Source: it is a guide for designers and for participants and users too.

Producing Open Source Software is a book about the human side of open source development. It describes how successful projects operate, the expectations of users and developers, and the culture of free software. It is available in bookstores and from the publisher (O’Reilly Media), or you can browse or download it here.

Producing Open Source Software is released under an open copyright that allows everyone to share and modify the book freely. The latest version is always here. The online version is the same as the commercially available print version — in other words, you can buy a printed copy and know that it’s up-to-date. When and if there are significant differences, we will list them here.

This book is meant for software developers and managers who are considering starting an open source project, or who have started one and are wondering what to do now. It should also be helpful for people who just want to participate in an open source project but have never done so before.

via | ossblog

Share

code_swarm. An experiment in organic software visualization is an application created by Michael Ogawa with Processing, that gathers data about the history of an open source / free software community and visualizes it in a video. Here’s the video for the Python programming language:


code_swarm – Python from Michael Ogawa on Vimeo.

I’ve been studying software projects for a while now. Not the programming, but the people — the way they interact with each other through collaboration and communication.

(more…)

Share

Openmoko: Neo1973

We can say that these days the first mass product completely open source has been distributed. Therefore, this is the first example of a real Open Design, not tied to individual experiments or niche markets (albeit very important): the first example of how open source philosophy can be adopted not only in areas different from programming and production of contents, but also in a production of physical goods, rival goods.
I am talking about the Openmoko organization, a project aimed at the design of a smartphone completely open source, first for its software, and now also for its hardware and design.

Openmoko: Neo1973

We can say that this is the first, true, open source mass product design, as the previous examples have not pursued completely the Open Source philosophy, or because they have had limited results, or, lastly, because the context was not ready for actions of this type.

Thinkcycle, which is the first and most developed example (at least so far), was an experiment aimed at niche markets, and for this reason should deserve even more importance because it was aimed at helping disadvantaged contexts, but still limited in the results and in influence on the world of design as too ahead of the spread of Open Source awareness in society.
The initiative Ronen Kadushin, although worthy, represents only a solitary experiment without broad appeal and development.
Martí Guixé’s proposal takes the Open Source as a metaphor and try to adopt some of its collateral features, in the sense that look for certain effects of the open source that can apply to products too, but in substance it is not open source.

The Openmoko initiative (in its first incarnation, Neo1973, produced by FIC) is so important because the adoption of the Open Source philosophy is not an experiment but a real initiative. We then passed the stage of inspiration and experimentation for Open Design, to a stage where it is put into practice. Of course, experimentation is not over and should be pursued further, but now we are talking about a product that the general public will see in stores and that is in competition with the most expected product of the moment, the Apple iPhone. And this referring to the freedom that this choice of opening may give the user, just like the philosophy of the Free Software:

If you can’t open it, you don’t own it. Our first key unlocked the software, unleashing the community to recraft the code. Now, we free the case and share the keys to Industrial Design. Developers who want to re-craft the case are set free.

It is by no coincidence that an advanced version can be bought, bearing all that is needed to open and edit the phone, enabling his hacking in order to customize and learning from it at the same time.

Openmoko: Neo1973 Advanced Kit

The distribution of the design files, which took place recently, is therefore a logical consequence; the files (IGES, STEP, ProE), were published under license Creative Commons ShareAlike at this address: http://downloads.openmoko.org/CAD/

Openmoko: Neo1973 Source Code

The fact that a mobile phone of new generation (a smartphone) is the first true open source product, makes the event even more important. Why? Because mobile phones represent a huge potential for the development of community-based collaborative services. A tool that will enable us in the future to exploit, enhance and more easily spread the collective intelligence, because it has the ability to further break down barriers of the service, as many more people have access to mobile phones and feel more comfortable with them than with computers and the World Wide Web.

Therefore, with an Open P2P design methodology we could design with/for a community, mobiler phones, their software and their services, according to their specific needs. We are then able to co-design with a community their collaborative services and the tools that allow their deployment, even for small contexts.

via | core77

Share

Yesterday was definitely a day about 3D and Knowledge Sharing…in the morning I gave a presentation about Blender during the LinuxDay 2007 organized in Milan by OpenLabs.
In the evening I watched the Life of Galileo play (by Bertolt Brecht) at the Piccolo Theatre: a play about Knowledge (its research and its sharing), and an experience that reminded me how theatre is 3D (unfortunately, except for concerts, I don’t go very often to theatres).
And then a very interesting discussion with Gianandrea Giacoma (ibridazioni.com): how to make 3D Knowledge Sharing, passing from a Blog to Reality.

Here’s my presentation about Blender (9,3 Mb, in Italian):
presentazione_blender_Menichinelli_linuxday_2007.pdf

And here on Slideshare.net.

Share

Within this Blog, I write about how Free Software and Open Source could be useful to Design if we want to learn how to relate tocommunities and complexity. But they can be useful as well, simply by giving us free/open source design tools!

This Saturday, 27/10/2007, I will talk about Blender at the Linux Day 2007, organized by OpenLabs in Milan.

See you there!

Share
Page 1 of 212
Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.