silent_gnomore

Thanks! Also, I can explain my perspective though I can't explain that for others as well. My knowledge of programming has been accumulated across many years of intermittent study and practice. When I get started on it, I devote a lot of time to it and much of what can be learned from a textbook and taken at face value on faith that the book is correct, I've produced by sheer tenacity and learned the hard way. You can see why that would lead to many false starts on projects and stretch the time it has taken me to acquire practically applicable proficiency. Though now, I've met a standard I set for myself years ago: I've accomplished something in code that one I'd consider more knowledgeable has said is impossible, and it only took a few days' tinkering. So, where does this put me as a budding developer? I have no releases to point to yet, nothing on Github to showcase my skills, no resume in programming, and my academic credentials in the subject consist of a whopping one class on fundamental concepts that could have as easily been taught using Basic as C++. I am under no delusions that I am desirable as an asset to any company yet. So, my next milestone is something worthwhile for a portfolio, and the milestone after that is to prove myself an asset. So, wouldn't it be pretentious of me to worry about whether somebody out there makes money with my code? It would only be beneficial to us both if anybody did. Now, bring in KSP. The game has motivated and inspired me, so for love of something fun and challenging, I want to do something challenging to help others have fun. My project is one inspired by sheer good will and recreation; not some serious research project or commercial product in development. It's a toy, even if it's a toy with potential applications for more than just KSP. This is probably a very different perspective from that held by one who understands the nuances of various licenses and the practical consequences of departing from standards thereupon, and I can't say with certainty but would wager that for many mod developers, it's exactly the same. They work out of love for a recreational outlet, and build their skills from that frame of reference. As such, for those of us writing from this perspective, it would be awesome to have a license that better reflects our intentions. See, we could write one up ourselves, but it would be practically meaningless, and we could borrow parts from existing licenses, but we wouldn't understand all the ramifications of such in practice.

I don't mean to be inflammatory with the "don't be a jerk" thing; only humorous about keeping it simple. Thanks for the tips!

What I'm working on, I'm making because I love KSP. It brings out a lot of good qualities in people, it's fun, and it makes me feel happy. It's that simple. Assuming I make it through the project (you never know until you release)... 1) I don't want anybody to use my work to create a better version of exactly the same thing unless it's Squad doing it. They get a free pass if they can make KSP better with it. 2) I don't care how my work is used other than that, just so long as my name is credited visibly. Credited how? Doesn't matter, so long as people see it. That could lead to work. You made a game? Congrats. Put my name down as "Big Jerk" in the credits. I don't care, so long as it shows up. 3) Whatever license accomplishes this, it in no way restricts ME. My work is my work, and I am not bound by the terms meant to protect it. So I could make a better version of my own thing or make a derivative and not credit myself. That's it. Everything I'm writing can be applied to other things. It's not a KSP derivative. It's a stand alone tech being applied to KSP. If I'm going to take a video game too far, then I might as well do it constructively. Now here's the problem: The license I describe doesn't exist. But if there's a software law guru out there who could advise, I'd like this to be called the "General Don't Be A Jerk License". Really, it should just be simple.

More cost effective: than terraforming barren worlds, asteroid mining/other resource faucets; required for medicine production/other research, expansion of economy Safe for indigenous life: in terms of pathogens and required alterations to the environment Necessary to prevent our extinction: If we don't, then every human being dies _________________________________More Cost Effective___________________Safe for Indigenous Life_______________Necessary to prevent our extinction We have to prevent our extinction___________Yes__________________________________Yes ____________________________________Yes Safe to indigenous life_____________________Yes__________________________________Maybe__________________________________Yes More cost effective _____________________Maybe __________________________________Yes___________________________________Yes 7/9 chances, we do colonize, and in the remaining two it's a 50/50 chance. So, 8/9 probability, yes, we colonize. This assumes that if it's not required to prevent our extinction and it would not be cost effective or would destroy the indigenous life, then we would not colonize. I don't think we'll be totally devoid of ethics if we develop that far, and we certainly won't be stupid or careless. This also assumes that since we have nearly developed gene therapy already, then so long as the life is carbon-based, their immune systems can be used to augment our own. In fact, their capacity to deploy agents of biological warfare while rapidly immunizing their population would be their only defense. This matrix does not apply to worlds harboring non-carbon life, as such worlds would likely be unsuitable for human habitation. Before you feel too much like we're bad guys, consider that this matrix is equally valid for any space-faring species that may exist out there. If they find us, then we will be hosts. Finally, do this thought experiment: On this world, right now, it comes to light that either every single person in a small, underdeveloped nation dies or everybody else in the world dies. We may not like the answer, but we know what would happen. edits: Shortened. The matrix is enough. Also, got the matrix to somewhat line up.