Search the Community
Showing results for tags 'gpl'.
There was a recent controversy, and a heated exchange in the betatesting forum, which might have gone largely unnoticed, and I think the topic itself is pretty important for the community. The whole thing starts here: http://forums.thedarkmod.com/topic/19282-cleaning-up-the-neighbourhood-beta/?p=430318 In essence, mapper copypasted portions of his previous map into a new one, along with portions of work by another mapper, with changes ranging from slight/cosmetic to none. Two examples: Since I was the only one speaking up in that thread, I'd like to hear our mapper community stance on such practices. First, does this even constitute reuse, remix, or adaptation? It looks more like a collection in CC definition. And, is there a way to protect your work under GPL/CC from such practices? (paging Demagogue...) Second, I'd just like to hear your personal opinion on this. To me, this is serious, quite dangerous precedent. It's not using abandoned work with sb else's blessing. It's also not an homage, as there's little creativity being shown here. This is copypasting and slightly tweaking sb else's work to speed up your mapping process. To me, it's self-degrading and admitting creative failure. Doing it with sections of your own map might just be poor taste and your personal matter, but doing it with someone else's work? That's whole another level. Do we have to start protecting .map files somehow, or have some kind of community guidelines in place on this?
There are likely to be very few code changes that the Doom 3 community issues where I will comprehend the significance. That said, I am creating this thread for the purpose of folks who catch any good GPL fixes that they'd like included in TDM builds. This is a place to ask "Should I make a tracker for this Doom 3 GPL fix, I found or created?" I'll start. There have been variations of the Carmacks reverse code and I'm sure there will be more. Here is the current best example AFAIK. It basically lets the driver perform the Depth fail code via the "StencilOpSeparate" command thus deferring responsibility for violating the patents to ATI and Nvidia for implementing this driver feature... (Older hardware will not take advantage of this optimization though.) Here are the changes and a little commentary by the coders: http://git.iodoom.org/~raynorpat/iodoom3/raynorpats-glsl_iodoom3/commit/332fa0d46f68e4057a00275a75e09c1f3b1ab7c8#comment_24