ACTA defeated in EU Parliament...

ACTA, the international version of SOPA, has been defeated in the EU Parliament by on overwhelming mayor. The final vote of 478 to 39 against it, making it hard to argue that anyone other than special interests want anything like ACTA.

This is a mayor victory for the users rights, and to against having back door deals like ACTA being forced upon people.

Most importantly, that the EU Parliament voted against it practically unenforceable. Now, most countries will move away from ACTA since people have made one of the most important governments of the word shoot it down on its own backyard.

I hope the message goes out that laws shouldn't protect special interests over the people. As a matter of fact, people should be more protected from the abuses from the special interests.

Patents being used wrong...

It seems that the current patent system has been transformed into a tool that big companies use to curb the competition.

Almost every week now, there is a case of a big company suing or being sued. The worst part is that most patents are on things that shouldn't be able to get a patent to begging with. Like the general design of a certain product, or an algorithm that are needed to run many things because there isn't other ways to do it.

It's worrisome that those patents are granted, and even more worrisome is that judges are upholding them even when the claim or the patent flies against common sense. It seems that you just need to be big or popular to have the system on your side.

Patents should be granted on basis of the technical merit, not just because no patent had been granted on it before.

I just hope more people put pressure on whoever it needs to be put on, so the patent system is reformed.

Building through consensus...

Another of the strengths of FLOSS, is that most projects tend to be managed though consensus.

This is important, because it reaches to those people that will be affected by some change or have the experience required to move the project forward. On most cases, people on both camps is consulted to make the best possible product.

It's important to note that most of the time, the people that build the consensus are those who have qualifications to bring what's needed to the table. Yet, if you have something to say about what's being done, you can weigh in with your opinion or share something that you've made that could benefit the project.

There is a central group, or individual, that makes the final decision. But that decision is made using the input of those who have something to say on how, where, or what should be done.

It's important to keep in mind that not everyone will have their way. But, this makes FLOSS stronger because the projects are make decisions taking into account the voices of those who make up the community of users and developers of that particular project. And yet, there should be someone capable of taking the final decision when the time is right to do so.

There should be a balance, and the great thing is that many FLOSS projects have found it.

Part of a community or just a costumer...

When I see how FLOSS and closed source companies treat the people who use their products or develop for them, the difference couldn't bigger or more striking.

While on closed source projects costumers and developers tend to be seen just as an working relationship, on FLOSS there is a sense of being part of a community that works together as such.

Closed source project are closely guarded to avoid giving away any control of what happens behind the user side. This means that the users don't have any say on what goes on there, and are dependent on whatever the people who run the project choose to do with the software.

On the developer side of business, they are just allowed access to what the project managers believe the developers should have. This means that developers are also tied to whatever to what the project owners want the to do, or how they believe things should work without any outside feedback.

On FLOSS projects, both users and developers can have a say on every aspect of the development process and the direction of where the project should go. It truly becomes a community effort, since everyone that can add something of value to the project can actually do so.

Closed source projects want to retain as much control as possible on as few possible hands, with centralized decision making process. All decisions of where and how changes are made, and where the software is being taken, are made by a the core management.

FLOSS projects are much different. The community around the project has a bigger share on the on how the project is run, and what changes or additions are made. The management is responsible of the final decision, but the community has the chance to give a lot of feedback on what the decision should be or how it should look.

At the end FLOSS is a lot more inclusive of the community of users and developers that builds around the projects built as FLOSS. On the closed source project, the relationship is a lot more rigid. Users and developers are just to consume what the project leaders thing they should.

Personally, I just don't like being forced to use something just because I'm told to do so.

Community effort...

Another of the things I like about FLOSS, is that projects that are made this way become the propriety of those who form the community behind it. It stops being just the propriety of those who kick started the project, or those who manage it.

The efforts to maintain and improve the project, are a lot more democratic. Everyone that has something to say, can make it known to the community at large. If there is an interest to contribute in any way possible, there is a way to do so.

Each project truly becomes a part of those who work on it, and those who work on it become of something bigger. Both the project and the community at large benefit from each other, and everyone gets something in return from working on the project.

Most important, FLOSS gives all the people who interact with any project much more that they put into the project. We get the freedom to choose the way we interact or collaborate with people on the project, and the project. One can commit to any project to any level one feels comfortable at.

One can choose those projects that better fit what we want to do, and what one believes in. And if there isn't one that fits the bill, there is always the chance to start a project that does. There is no need to tie oneself to particular project just because there is no other way, each individual and community can make the way they want to go.

After all, FLOSS is about giving people the freedom to choose what's best for them.

Using FLOSS to reach out to others...

It's sad to see that for many people are more willing to accept increasing military budgets or aggressive moves, than to increase the budgets for education, libraries, or places for the integration of the communities we live in.

There should be more emphasis on things that bring people together to share what they want to, or to learn, exchange ideas, and work together on whatever they want to. By enabling people to come together to work together, or to get to know each other, we create the kind of environment that fosters unity and peace. We start to see others as persons, with all that comes along with that viewpoint.

FLOSS can give us a platform to help the communities to get there, since it gives everyone an equal opportunity to reach out and discover what's out there for them.

In a way, it can be the gateway not only to know others on the same community and what's going on within. It also enables the individual to reach out further away, enabling the creation of an even wider viewpoint and pool of knowledge, knowhow and wisdom to dispose of.

FLOSS can be a great enabler to a wider audience, since the point of access to it is significantly lower. Not only that, it supports most of the modern standards and has all the software that most people will ever need.

There is a need to be building bridges between communities and individuals. We don't need walled gardens, we need things to be open and transparent for everyone that wishes to be part of the community.

It's time to stop with the divisions, and bring forth unity.

Coming together....

One of the things I like the most about Linux, and FLOSS in general, is that it brings people together to work on things that they enjoy and like to do. By doing so, they can share their with others while getting feedback from people who share their passion and enthusiasm for what they are doing.

It tends to bring the best from everyone, and letting people to freely share their work and ideas with each other. The most valuable thing exchange between the people working within these communities is not money, is the knowledge and experience they have earn after hours of working and contributing to the project, or projects, they are working on.

By sharing what they know, and working on common goals, people come together and the feeling of belonging makes these communities to become close and want to help others to make things better.

I'd love nothing more than to see this kind of community at work in more areas of life. The places where we live and work would greatly benefit from people working and exchanging ideas and experience freely with each others. There is a need to create places where people can come together with ease to work on things, or talk about that are important for them or the community they live in.

The importance that most people must have easy access to these forums, or workplaces, can't be understated. If people can easily go to those places, and make full use of the installations, they are worse than useless. It can be a dedicated place, or it can change location according to the needs that the group has. And, the information of where they are, and the hours it's open should be easy to come by as much people as possible.

With modern technology, not everyone has to be at the same physical place on some occasions. Telecommunications have made it easy for people to be able to work as a group, or be part of a group of people that just likes to discuss a certain topic, without to have to be at the same place at the same time. Meetings by individuals within the group could be easily arranged if they need or want to do so.

There needs to be the will to come together, then the first step is to start building such communities.

Flexibility in numbers...

It's interesting to see how FLOSS projects seem to take a life of their own when they are managed correctly, and seem to actually surpass expectations of what can be done with them.

When there is the right people managing any given project, it can not only reach the goals it sets itself. It can actually surpass them quite easily, since people can join in and give to the project any fixes or improvements that are needed with ease.

And since the community around the project can actually have some amount of say about where the project should go, it's everyone feels more valued and more willing to keep working to make the project move forward.

If the management of a project decides it doesn't want to keep working on it, it's easy for another set of people to come in, and either take the project or fork it. Or if a subset of developers feels that the managers aren't taking the project in the right direction, they can fork it and take it where they believe it should go.

This makes FLOSS a lot more flexible, since the managers of FLOSS projects can benefit more directly from feedback from people on the field. And this feedback can come in the form of bug fixes or improvements to the code that might be hard to do by the people working on the project on daily basis.

FLOSS projects can be more flexible because it can have a wider set of people that can contribute directly to it.

FLOSS is generally more friendly to create an environment where on which the community that grows around it can make each project stronger through collaboration of its members. Of course, this level varies from project to project.

Yet, most of them are open to all to help.

Importance of open source and standards...

It's important to realize the importance of open source and standards have to give to both developers and users.

Being able to build on the work already there, helps to be able to the developer to focus on adding value to his work. By doing so, it gives him an important tool to differentiate his app from others out there and bring in revenue.

It seems that many developers nowadays spend their time trying to work bringing the solutions they need to common problems, because they can't use existing solutions already out there because they can afford to pay for the license or there isn't a license at all.

This can be a problem to independent developers, even small companies, since they have to put resources they could be using elsewhere to reinvent the wheel. Putting them at an disadvantage, because it becomes harder for them to give value, or can't differentiate, they product from others.

And not only they lose, the users lose too. Those developers could have ideas, or solutions, much needed by the users. Yet, they can't connect with each other because there isn't a way for them to do so.

On the user side, open standards are much more important. Mainly because open standards allows the user to find the software that better suits his needs, without having to worry if he will be able to continue to be able to access and use the data he already has.

And the developer can focus on giving his users the tools they need, without having to worry if the underpinnings will work.

This way, everybody is set to win.

Ease of repair and upgrading...

One of the things I consider when buying a new computer, is how easy it is to repair or to upgrade with relative ease.

I like to upgrade the RAM, or change the battery when it dies, by myself. While I could learn how to change the processor, change the screen, and other repairs by myself I don't mind having someone else doing them. Actually, I believe that is a good thing that computers and other electronics to be easily repaired or upgraded.

It's both economically and environmentally conscious that computers should be serviceable. After all, if computers could be easily made to be as new by skilled servicemen, those computers can have a longer life. This doesn't mean that the original owner can't buy a new computer if the need arises, but the computer can be used by other family member or friend whose needs are meet by that computer.

Not only that, since those computers are usually substantially cheaper than new ones more people can have access to have their own computers.

Let's be honest, the argument that you need the greatest and newest hardware to do the basic stuff that most people does is not true. And there is a lot of great Linux distros that run on that kind of machines, that actually are targeted to run on them. So, you can get the best software with all the modern safety futures that are needed for the basics that runs on substantially more affordable hardware.

Environmentally, the it makes sense to keep the computers or its components for as long as possible. This helps to keep them put of landfills as long possible, and to recycle all that can be recycled would be a great plus.

Servicemen can be a lot of help when come to be able to recycle components, since they can take those components and do the recycle process themselves. Either by using those components on other computers, or handing them to other people to do so.

But, it's important to be conscious of this, and buy only those models that are easily repaired. And when possible, try to give or sell your old computer to those who need them or can put your computer on good use.

For the love of learning...

As a geek, I love learning how thinks work and how systems work to make things happen. How changing any part of a system can alter its functionality, thus being able to make it work better by tweaking any of the individual parts.

This is one of the reasons why I've been using open source software for a long time. Because even though I don't have the technical skill to tweak much, I still can learn about how the software works from the inside-out. And I can do it in an environment that encourages the study of the source code, and if you can't contribute with code you can contribute by giving ideas on how to make the software better.

The first open source software I used was Firefox, and then Songbird as my media player. A couple of years ago I made the jump to Ubuntu, and I've no regrets.

I've fulfilled my thirst of knowledge, and I'm still learning much about software development and how the FLOSS community works. I've seen the complexities inside the FLOSS community, and I'm trilled to be part of it.

Using Ubuntu has been fulfilling, and even though there has been some hiccups along the road, it has been quite a satisfactory road. And I've a new level of respect for those who have build FLOSS and Ubuntu.

They have built quite the great piece of software.And they keep improving it all the time.

It'd be great to see people as engaged on science and mathematics as people are on FLOSS. We can really build a better world if all this was done on the open.