Re:Government Open Source Office deal set to provide major s...
by pbhjpbhj on Tuesday October 20, 2015 @12:52PM
(#10420288)
I'm not sure what you're refuting? All I did was express that in circumstances where a company sells bug fixes for considerable sums that there has to be pressure on that company to compromise their morals; if it takes a hundred months of service to a company to recover the revenue one gets from one day of bug fixing then the economics of the situation require strong moral backing. It seems there should be lower risk ways of structuring this relationship.
However, with proper external independent oversight this becomes moot, thank you for pointing out that oversight appears to be in place.
It sounds from what you say that all Collabora work is pushed to the LO git repos?
In fact, I introduced a few bugs into the VCL demo tool and Michael Meeks was quite (how should I put this?) direct in his feedback to me. Those inadvertent bugs got fixed very quickly by myself.
I can assure anyone reading - Collabora only cares about good quality work, and in fact if any work is pushed into the LO git repository that is substandard the other non-Collabora devs either a. fix it immediately or revert the changes, or b. have some stern words with the Collabora dev, or (I'd imagine) to Michael or Kendy.
P.S. Eventually all code Collabora writes gets pushed into the TDF's LO git repository. Maintaining incompatible branches for any length of time in insanity, and aside from the fact that contributing back to LO is the ethos of the Collabora Productivity team, it's better for them to do so in order to allow others to help maintain and enhance the code they write.