original: Oleg Mastruko ... But, now that you asked this, who exactly is "WE" in this case, and who is the Permission Granting Authority (PGA) that asked, or authorised el cid to do this and that? No need to answer, I am just trying to point out the absurdity of the above discussion.
I would like to comment on "the process".
Joe ( me ) being a software guy ... as part of my efforts with CHS, I have tried to bring some bits and pieces of software process to the table.
While our "MODS" are just data MODS ( not code MODS ) ... changing data ... is still a "software thing" ( not a hardware thing ). So software principles are relevant.
Open Source projects have two relevant concepts that I've tried to introduce in CHS.
(1) Gate Keeping
(2) Fork the Code
An Open Source process template would have a "commitee" ( which could be a commitee of one ) who reviews and allows contributors to make changes to the base product. Typically the gate keepers are part of the original creator team, but regardless they are typically charged with somhow preserving some aspect of the original concept ( perhaps in the case of CHS .. the extra focus on historical accuracy ). We are now using a "Peer Review" process as a part of the review process. So each contributor has an assigned "peer reviewer" who looks over their work and approves it to the CHS team prior to final approval ( by the single appointed gate keeper of the moment ) into CHS. This is a good process and has caught a number of errors, typos and other wise. I'm not aware of anyone who is in opposition to this process.
In the event that a contributor desires to move things in a different direction from the original open source project. Or in the event that a contributors work is refused by the gatekeeper. The contributor is always free to "fork the code"... In Open Source speak, this just means the contributor takes the "product" makes his changes and re-publishes the product as something different. And in the Open Source world, this is all perfectly fine and intended. The only restriction, is that the "forker" is no longer presenting the forked version as if it were the original "product". It is something new and different. And actually, if I'm not mistaken, this has already happened to CHS. And may well happen again. And this is fine !
So, I am mainly trying to discuss where "permission" is relevant and where it is not. It is relevant in open source, if is desired to add the contribution to the original product. It is not required if the ccontributor wishes to "fork the code".
And BTW - I "asked" El Cid to work with me on making some changes to CHS requested by Andrew. "Approval" for my changes and separately for El Cid's changes ( or for any ccontributors changes ) comes from the peer review process.
I hope this helps clarify our process.