Clarifications on code policy in mods.
Yesterday a post was made that started to give details about how we would handle code in mods that was deemed to be spiteful in nature or disputes between mod developers. However before we get into this there are a couple of points that need to be cleared up for everyone. Firstly is this term 'Malware' that is being thrown around a lot. By any definition of Malware that I have seen, the code that has been shown around in different places from various mods is not even remotely close to being classed as malware. In my original post I mentioned that code designed to crash games with malicious intent is as close to malware as someone can get. This is not the same as something actually being Malware.
Why is this important? Essentially because once a few people start calling something Malware then it inevitably spreads across the internet. Soon, everyone is calling it malware and it sticks and then the mods reputation is harmed. Let us make no mistakes on this, this code is not designed in any way to track or steal information and it certainly wont harm anyones computer in any way.
This leads us on to the next question. Does a mod developer have a right to add code which is aimed at preventing their modification in a way that is contrary to their wishes. This to me is a big question, that I honestly do not know the right answer . There are many points of view on this subject, many of them valid. For me I think the right line that needs to be drawn is that is it OK for a mod developer to add code to a mod which is targetted at preventing their mod from being used in a way against their wishes as long as they take all reasonable measures to protect the integrity of a players world and where possible ensure that the end user is sufficiently warned in advance.
The next question is what do we do when someone adds code that contravenes this but is targetted at something other than FTB (eg a different modpack). This to me is a far harder question, morality dictates that we should be equal across the board and make decisions irrespective of where it is targetted. However this leads us down a road, I really do not want to travel. It is not our role or place to enforce our morality anywhere beyond FTB. If it doesnt affect us then it is really none of our business.
So the line I am proposing is as follows.
From this point forwards FTB will not knowingly distribute destructive or compatibility breaking code that has been added to a mod for spiteful reasons and affects mod packs that FTB distributes.
Code added by a mod developer for any purpose that does not directly affect FTB will be deemed outside of our purview, this includes things like legitimate DRM measures.
Slowpoke.
Yesterday a post was made that started to give details about how we would handle code in mods that was deemed to be spiteful in nature or disputes between mod developers. However before we get into this there are a couple of points that need to be cleared up for everyone. Firstly is this term 'Malware' that is being thrown around a lot. By any definition of Malware that I have seen, the code that has been shown around in different places from various mods is not even remotely close to being classed as malware. In my original post I mentioned that code designed to crash games with malicious intent is as close to malware as someone can get. This is not the same as something actually being Malware.
Why is this important? Essentially because once a few people start calling something Malware then it inevitably spreads across the internet. Soon, everyone is calling it malware and it sticks and then the mods reputation is harmed. Let us make no mistakes on this, this code is not designed in any way to track or steal information and it certainly wont harm anyones computer in any way.
This leads us on to the next question. Does a mod developer have a right to add code which is aimed at preventing their modification in a way that is contrary to their wishes. This to me is a big question, that I honestly do not know the right answer . There are many points of view on this subject, many of them valid. For me I think the right line that needs to be drawn is that is it OK for a mod developer to add code to a mod which is targetted at preventing their mod from being used in a way against their wishes as long as they take all reasonable measures to protect the integrity of a players world and where possible ensure that the end user is sufficiently warned in advance.
The next question is what do we do when someone adds code that contravenes this but is targetted at something other than FTB (eg a different modpack). This to me is a far harder question, morality dictates that we should be equal across the board and make decisions irrespective of where it is targetted. However this leads us down a road, I really do not want to travel. It is not our role or place to enforce our morality anywhere beyond FTB. If it doesnt affect us then it is really none of our business.
So the line I am proposing is as follows.
From this point forwards FTB will not knowingly distribute destructive or compatibility breaking code that has been added to a mod for spiteful reasons and affects mod packs that FTB distributes.
Code added by a mod developer for any purpose that does not directly affect FTB will be deemed outside of our purview, this includes things like legitimate DRM measures.
Slowpoke.
