> Well, at least you're honest about being a dictatorship. :) OTOH, just saying doesn't make it so. Hostile forks are a thing, license changes without copyright

> Well, at least you're honest about being a dictatorship. :) OTOH, just saying doesn't make it so. Hostile forks are a thing, license changes without copyright assignment are not a thing, etc. Hostile forks do not change the project, they create a new one. License changes are of course restricted by law, as are all other ‘decisional powers’ (as any reasonable person would assume). > Congratulations, you're biased in favor of people with more outgoing and assertive personalities. ;) Not my problem, a technical project is not a therapeutical session for people who can’t speak their mind. > Proportional requires that contributions be quantifiable. I'm not aware of any accurate, objective way to do that. (If there was, it would also be a solution to the "how to measure productivity" problem.) You only need a good enough comparison to differentiate two people if there is a dispute. This is often a very clear-cut case. If it isn’t, let the rest of the project decide in whatever way is appropriate. > What does "technical advantage" include? Switching costs imposed on users? The level of skill required from contributors? IDE-computable code metrics? I don’t see why different projects could not have different metrics there, to be decided upon by the project/core team? If it’s a fun-in-your-free-time project, you can expect as much as you want from future contributors and don’t give a shit about your users, conversely, if you try to sell it, you may need to take switching costs into account. > Wow, working only on clearly-defined problems must be nice. What happens when the ambiguity is part of the problem space? If your problem space is not well defined you have bigger problems than a code of merit you may or may not like. Do more research first until the problem space is defined. Apart from this trivial tidbit, the sentence obviously aims at ambiguity in communication, where there is never any place for it. Not using words ill-defined words or ambiguous constructs seems like a decent idea in general.