> It is you that are repeating yourself, without answering the question.
What is "the" question? If the question is "why is not paying for code a core tenet of the asf", I will restate my previous answer more fully and using Roman's concise definition of code followed by more questions. So first, the what: The ASF core tenet of "not paying for code" is based on a concern that doing so threatens another ASF core tenet with vendor neutrality. These two tenets, "not paying for code" and "being vendor neutral" are well espoused tenets of the ASF. Code for this purpose is well defined as anything that would end up in a project repository. Second, the why: If you asked the question why we have this tenet, I would say this is the same as asking why do we have a 1st amendment in the US to which I would tell you to study history and trust the founders. The answer is the same for the ASF and that history will show you that the founders thought it was very important to be neutral as a differentiator from other organizations and that accepting payment for code would be a slippery slope eroding that neutrality. Third, the why not?: The question people seem to be struggling to ask doesn't seem to be A) whether this is a core tenet or B) why. It appears to be C) why not / how will it erode neutrality? and D) can I try a small experiment and see if does erode our neutrality? I like the roadmap we have in place right now with 19.5K coming from a sponsor to outreachy providing us 3 interns at which point we can report on the success of that initiative and look to expend if successful or contract if it isn't. Regards, KAM
