Goonhub
12-01-2020, 10:11 AM
(This post was last modified: 12-01-2020, 01:21 PM by Carbadox. Edited 1 time in total.)
Moving forward with the coding being open source now, what are the 'policies', for lack of a better word, in regards to ownership of parts of the game?
The reason I ask is because I recall 2 situations, one where there were proposed new sprites for bees which were rejected due to the current ones having sentimental value to some admins. Another being that a suggested rework of Cog1's medbay was rejected by the creator. Obviously I don't know the full story of the incidents and the details I recall are pretty hazy. But from my point of view, it seems to contradict the idea behind open sourcing, since the basis for rejection seemed to come off as more personal rather than measure of quality and what not and I think it'd be good to have some sort of reference for the future.
Edit: If I'm allowed a 2nd semi-related question, are there set prerequisites(?) or general guidelines for accepting community contributed pull requests?
The general public understanding, in my interpretation, is that not alot of people are really know what does and doesn't contribute to whether something is approved and merged or not, EG some assume that community approval is first and foremost while others think that only the Developers final word counts, regardless if the community is for or against it.
The reason I ask is because I recall 2 situations, one where there were proposed new sprites for bees which were rejected due to the current ones having sentimental value to some admins. Another being that a suggested rework of Cog1's medbay was rejected by the creator. Obviously I don't know the full story of the incidents and the details I recall are pretty hazy. But from my point of view, it seems to contradict the idea behind open sourcing, since the basis for rejection seemed to come off as more personal rather than measure of quality and what not and I think it'd be good to have some sort of reference for the future.
Edit: If I'm allowed a 2nd semi-related question, are there set prerequisites(?) or general guidelines for accepting community contributed pull requests?
The general public understanding, in my interpretation, is that not alot of people are really know what does and doesn't contribute to whether something is approved and merged or not, EG some assume that community approval is first and foremost while others think that only the Developers final word counts, regardless if the community is for or against it.