home home

downloads files

forum forum

docs docs

wiki wiki

faq faq

Cube & Cube 2 FORUM


Understanding Open Source

by Quin on 06/21/2012 10:20, 29 messages, last message: 07/14/2012 08:12, 10556 views, last view: 05/18/2024 07:08

From: http://qreeves.blogspot.com.au/2012/06/understanding-open-source.html

As the developer of the Open Source first-person-shooter project, Red Eclipse, I have come across many different types of personalities; some are good, some are bad. Quite often, I will have someone looking to contribute to the project who is so convinced that their point of view is so important that it only ever ends badly. Unfortunately, you can’t control this kind of thing, but in the past I have attempted to guide these people along the right path, albeit unsuccessfully most of the time.

I believe there is a misconception surrounding the phrase “Open Source”, that many people bang against and wonder why they’re met with such hostility. When a person decides to release their creations with an Open Source license, their desire is most often always to share it with the public in many ways, including allowing everyone to use and/or modify it for free.

You’ve probably heard the expression, “Free as in beer, not free as in speech”, but maybe don’t quite understand the implications of that. The creator of Open Source content is looking to give you something for free, and quite often allows you to take it and do whatever you want with it; the most beneficial part of which is the ability to study, modify, and play with it. This creator already has their own ideas, their own opinions, and their own way of doing things.

Every so often, you have an individual come along who has their own ideas and opinions, and they are so fixed on the concept that their way is the right way, they end up having a complete disregard for the creator, and the community behind that creation, if one exists. These people will enter a community, demand that everyone conforms to their vision, and when they discover the creator and/or community are resistant to it, blames everyone else for the fact that they failed. This often ends with the person declaring something along the lines of: “I should have known better, you don’t appreciate me, I’ll go elsewhere and get my way there.”

The problem is, these people don’t ever try to integrate with a project naturally, they appear to expect instant results as soon as they come along, and assume they know everything they need to know. This is mostly untrue. Throwing a tantrum and refusing to share your toys is the best way to ensure that everyone will instantly dislike you. To them, they were doing just fine before you came along trying to shake the tree and making demands of them, and they will continue to do just fine without you.

Open Source is a democracy of one. Someone, somewhere up the chain, came up with the idea and executed it. They built it, and they own it. Just because they have given something to you free of charge, does not entitle you to start telling them how to do their “job”. You’re not paying them, in fact, they’re giving up their free time to follow an idea that they are passionate about, and it is just a side effect of generosity that they released it for everyone to enjoy. Too many people think that Open Source bestows a right of ownership on them, but if you ever read one of these licenses carefully, all a creator is giving you is the right to use, distribute, and/or modify it.

So, if you’re looking to contribute to an Open Source project, now or sometime in the future, try to remember this: You are a guest in someone else’s home, please respect them and the work they have done. Try to understand their vision and their rules, get to know the way they operate, find out if they’re even interested in your ideas. If you approach them with a good understanding of their work, you’re more likely to get the result you are after, or maybe even find some other way you can fit in.

   Board Index    Go to next 20 messagesGo to last 20 messages

#1: ..

by eihrul on 06/21/2012 12:47

Not to quibble, but commonly "free as in beer, but not free as in speech" refers to closed-source, freeware programs. Where "free as in speech" refers to what others have taken to call "libre", that is Free Software (as per FSF definition in the vein of the GPL), and also Open Source if you're not a purist/fundamentalist.

That's not to detract from your article, we could amend it as simply being this: just because a project is free beer AND free speech, does not mean it is free REIN. There are some projects that may choose to organize themselves democratically, such as Debian, and even then they regularly elect leadership, but that is the exception, not the rule, as you point out. Most are oligarchies or benevolent dictatorships.

In reality, money makes stuff a lot easier because people can accept there's a boss, and they're getting paid to do what the boss wants. But when you make it into a volunteer situation, people rapidly lose their ability to suffer any leadership, good or bad.

reply to this message

#2: Re: ..

by suicizer01 on 06/21/2012 21:42, refers to #1

So we get a Sauerbraten rank system which shows off how much effort you do for the project?

Maybe that gives the right spirit to people which can't accept the policy on Sauerbraten.

reply to this message

#3: Re: ..

by Zamwa on 06/21/2012 23:32, refers to #2

If this is about corrallings of quadropolis I support the method of ranking but the ranking=admin is a mismanagement!
I think Eihrul's thesis is more about the miss misconception about the original derogatory term "free as in speech, not free as in beer." also known as Free Beer a recipe published under a Creative Commons license with it's origins most likely derivatized from Richard Stallman (yes the well known computer programmer!) who used the phrase "free as in speech, not free as in beer." often!
I could go on but Im no professor wikipedia!

reply to this message

#4: Re: ..

by Quin on 06/22/2012 04:07, refers to #1

Probably true, but this paragraph was more specifically aimed at the Cube family of communities, where this phrase is actually thrown around a lot. Even Red Eclipse is slightly more democratic, in a way, but in the end there is still a chain of command with someone sitting at the top. I think this is actually unavoidable in most projects.

I love the points you make though, and I'm quite sure you know exactly what I am talking about in this article :)

reply to this message

#5: Re: ..

by suicizer01 on 06/22/2012 19:03, refers to #3

It was actually meant as a joke, yet it's more funny you take that serious.

reply to this message

#6: Re: ..

by Zamwa on 06/22/2012 23:12, refers to #5

Just cheezburgered it to the epic level! ;") http://cheezburger.com/6359935744

reply to this message

#7: ..

by ultrasemen on 06/25/2012 17:00

I don't get it, still. Maybe it's wrong, but for me it seems just like you hate forks that take anything from sauerbraten but engine, and also hate global changes. Even license in readme says:
"The game is freeware, you may freely distribute the archive and/or installer unmodified on any media."
I know there is strictly protected content, but not so much and irreplaceble, right? And it reads like "GTFO with any changes, just play what you have".

reply to this message

#8: Re: ..

by baby~rabbit on 06/26/2012 04:32, refers to #7

Nobody hates forks. Forks are great, go wild, create - just remember to read the license of the content which is often not so 'open'.

As Quin says (paraphrased): respect the house of the creator.

reply to this message

#9: Re: ..

by Quin on 06/26/2012 05:25, refers to #7

Yeah, that couldn't be more untrue. AssaultCube and Red Eclipse (among others) are shining examples of the power that Open Source grants you. None of us hate forks, what we don't like is:

- People taking credit for our work, or using content when they don't have permission.
- People with starry-eyed ideas and either never follow through with them, or expect other people to do the work for them.

I know, from my experience with both the Cube community, and in developing Red Eclipse, that there is nothing wrong with a fork. In fact, Red Eclipse did exactly that; it forked and replaced all content with completely free alternatives (all our content is openly licensed).

When I arrived around here, I bumped against the very problem I described in my article, but I didn't chuck a tantrum and walk away. Instead, I took the time to learn what I needed to know, and contributed what I could, in order to become a productive and respected member of the community.

I worked on my AI until it was at a point where it was ready to show off (and that took a few years of on and off work), then eihrul reviewed my code. Because I learned how to write acceptably formatted code for Cube standards, all he had to do was fix some things to improve performance or correct areas where my knowledge was lacking. As a result, not only does Red Eclipse have bots, but thanks to eihrul, so do the rest of you here in Sauerbraten now.

reply to this message

#10: Re: ..

by suicizer01 on 06/26/2012 23:21, refers to #9

Yep and we thank you for creating the bots, Quin.

They still don't get how weapons work though, but they can aim and move better as the monsters.

reply to this message

#11: Re: ..

by ultrasemen on 06/27/2012 00:00, refers to #9

>or using content when they don't have permission
But what's the point of allowing using content only in original Sauerbraten and not even forks which can have really small differences and are also non-commercial and open-source?
Why not allow use it only on Wednesdays then, or when you're wearing red shirt. People who do it just lost their mind and are ruining conception of open source.

reply to this message

#12: Re: ..

by tempest on 06/27/2012 00:53, refers to #11

"People who do it just lost their mind and are ruining conception of open source."
Oh, yeah? Well, let me tell you something: those people lost their mind in such a way that they decided to contribute their work to Sauerbraten, for free, and allow other people to use it (within Sauerbraten) because they liked the game. I don't think you're in any kind of position to complain about that, and it's not their job to provide you with assets. And guess what: if you ask nicely, I guess most of them wouldn't mind allowing you to use their stuff in your mod.

reply to this message

#13: Re: ..

by ultrasemen on 06/27/2012 01:37, refers to #12

OK, simple analogy.
Someone saves one guy's life, but then decides he doesn't like him and kills him. Painfully. And everyone says "Well, this is his right - he can do whatever he wants with this guy, if it wasn't him he would be dead anyway". The same logic.
And proprietary is saving people for instant money - not good, but at least honest. And open source is saving them for free without any consequences (maybe only you ask him to save other people too, like you did).
>if you ask nicely, I guess most of them wouldn't mind allowing you to use their stuff in your mod
Yes. But finding and asking such a lot of people, finding licenses for everything might be a problem. I'm talking not only about Sauerbraten, but all people who behave like that. What's the problem is someone will modify your content or use it somewhere else, if it's also free and they will write you in credits? Creators often don't mind, but just write it anyway.

reply to this message

#14: Re: ..

by Quin on 06/27/2012 03:06, refers to #13

You seem to fail to understand. The only thing that is Open Source in Sauerbraten is the engine/code - the license is clear in this regard, so there really can't be any misconceptions about it.

Seriously, it isn't /that/ hard to find libre assets and use them in your own game. Either that, or you're free to make your mod as a drop-in to the main Sauerbaten game - I did this originally with SauerBot/SauerMod, these things are not hard to do.

In a way, I suppose you're the exact kind of person that this article is aimed at. You seem to think you have a right of ownership bestowed upon you, when this is simply not the case. You can go a long way if you simply understand the rules and work within those confines, and it isn't up to you to decide what those rules are, it is the people who created these things in the first place.

reply to this message

#15: Re: ..

by Dratz-_C on 06/27/2012 04:06, refers to #9

I just want to say that I am enjoying this thread. More often than I like to admit, I fit into the description,

- People with starry-eyed ideas and either never follow through with them, or expect other people to do the work for them.

Occasionally I do some actual work, but not as much as I ask other people to consider doing stuff. :/ I guess I am just in the learning phase.

Cheers

reply to this message

#16: Re: ..

by ultrasemen on 06/27/2012 04:36, refers to #14

Yeah-yeah, I get it - "we can do whatever we want with what we created, it's ours and not yours, and giving it up free doesn't mean anything".
But the reason I get butthurted is not only subconscious feeling of "half-freedom" (but mostly it, I must admit), but also just not understanding why. For all non-commercial freeware too. Why would one put some restrictions on anything he doesn't get money from? Nothing will get better for him (still no money), nor for others (can't use it in their projects). So, what's the point of doing so? Can you explain?

reply to this message

#17: Re: ..

by ultrasemen on 06/27/2012 04:41, refers to #15

Yeah. I have this problem too, that's why I'm arguing here and not actually improving source code :)
Anyway, I can just make fork with no sauer content and just something to replace, but with easy way to import it for player at his own risk. I call this distribution model "soapware".

reply to this message

#18: Re: ..

by Quin on 06/27/2012 04:48, refers to #16

As developers, we can't control the terms under which people release their content. Sauerbraten has many assets from people who have chosen only to allow that specific project to use them. You can either say "thanks" or you can deny that content being included because it doesn't fit your scheme. Sauerbraten chooses the former (whereas Red Eclipse chooses the latter).

Artists are hard to come by, and they are even harder to keep (there are other problems too which I won't get into here). Sometimes a project will just take what it can get so it can accomplish its goal. The Sauerbraten engine/code is Open Source so you can use it yourself, but the "game" is locked down by its content.

The other side of the issue is this: It is easy for people to complain about these things, but it is another thing entirely to fix it. Unless you can constructively and sufficiently contribute something better, you have no right to complain. I think this is basically summarised as "Be part of the solution, don't add to the problem." - I think I've done this with Red Eclipse already, so the point is rather moot. I've collected a decent amount of free to use assets there, that any person can use as a starting point for their own projects.

reply to this message

#19: Re: ..

by Quin on 06/27/2012 04:51, refers to #17

I keep coming back to my own experience here, I'm sorry if this sounds like a bunch of advertising. You can actually play Sauerbraten maps in Red Eclipse so long as you have it installed, it isn't hard to offer import ability and it doesn't technically violate any licenses, as everything is sourced from and happens on the end-user machine.

reply to this message

#20: Re: ..

by ultrasemen on 06/27/2012 05:38, refers to #19

I meant ability to replace everything to that from sauer - guns, sounds, playermodels, particles, etc - just make game look identical. What about RE, I'm sorry to say it, but it doesn't look good, its only my perception and I didn't play for long though. Yes, and also nobody plays it - much bigger problem for single gamer.
Yes, soapware doesn't violate licenses. I got this idea is from GTA, you know, it's so expensive to license cars to use them in game, so they just made their own clones of every real life car - but modmakers added real cars back to the game, so we can play it with real cars and R* don't have to pay car makers for licensing. Well, modmakes would have to - but who cares about them? This is like "don't steal anything from shop, just leave door open for the thief".

reply to this message

   Board Index    Go to next 20 messagesGo to last 20 messages


Unvalidated accounts can only reply to the 'Permanent Threads' section!


content by Aardappel & eihrul © 2001-2024
website by SleepwalkR © 2001-2024
54036965 visitors requested 71817033 pages
page created in 0.027 seconds using 9 queries
hosted by Boost Digital