Archive for the 'infrastructure' Category

What is a network service?

A network service is an instance of a software that runs reliably for a period of time and which links together people over space and time.

But who brings together the software needed to run a service? That would be the service maintainer(s). She/he is the one who wields the power of the software to enable communication between people. And linked people communicating build together culture.

To sum up: culture builds on services, which in turn builds upon software and maintainer’s work.

Eliberatica 2009

Ok, I do not know how to cover a conference properly, so I’ll just say that this year I saw more social networking and people were more action focused. I also got the sense that more and more Romanian people want to get involved in the free software movement. Keywords for this conference would be ‘action oriented’ and ‘social networking’, which is great.

A little about myself: I am interested in all things free culture, from software, to artwork, to data, but I am particularly interested in free as in freedom network services (FNS for short), from free cloud service to collaboration services between artists.

What I apprieciate most about this conference is that I had more time to socialize with people around: I had the opportunity to talk with Georg + Monty on patents, javascript AGPL, managed services and mostly stuff related to my trial at making a web/network service.

Now, I’d like to say a few words about the presentations:

Continue reading ‘Eliberatica 2009’

Standard for communication between project infrastructures

I see the way forward as a Foundation Board (free to join as individual contributors, not permited for companies) that establishes community standards on all collaboration resources.

Such a standard should include what kind of information should be contained in a bug report, and this could in turn be implemented as a RDF resource. As far as I have seen LaunchPad already provides RDF resources for bugs. This way there would be an easy transition between different project infrastructures: maybe one will be able to take all the bugs (closed or open) her/his project has on Source Forge and have them automatically imported, as a batch, into LaunchPad or CollabNet.

For project infrastructure there are also tools like Maven, which ads the goodness of dependency management. We should check the effectiveness of Maven and similar tools, find their weakest spot and make a request to the responsible team to improve that feature.

I also think we need to research more thoroughly a free software development methodology. We do not like some Agile or XP programming ways of doing things, so we need our own methodology/-ies. There are some academic studies on our development model but they are scatterd across different web sites. The idea is that we do need a more structured, integrated documentation tool on how we do/should work.

This research is needed to prepare the infrastructure we will use 2,4,8 years from now, when both the number and the diversity of contributors to our community will grow immensely.