Hi Tora, thanks for taking the time to answer, On Thu, Sep 18, 2008 at 6:25 AM, tora - Takamichi Akiyama <[EMAIL PROTECTED]> wrote: > Christian Lohmaier wrote: >> >> Well - I did ask for an explanation on why it makes a difference on >> why it matters whether Sun provides the builds or some other person >> provides it. [...] > > The primary reasons why I did not answer the topics were: > [...] > - I felt no need to *explain* since I was not your employee. > Whatever you could ask anybody to explain, they could choose > what they answer. If you were I, did not you think so?
Well, you were the only person who brought in the topic of responsiblity/credibility towards the customer/enduser - and since I personally hate it when people make claims that they don't explain, I asked for the reason. If someone cannot explain the "why" behind his argumentation, I cannot take the arguments serious. > ===== > [...] > - [...] We do not have a X-ray system that > might find a micro-sized eavesdrop device or bot in the product. > > - [...] Anyone, not to mention, including you and I, can > intentionally or accidentally replace some files to be packed in a > binary package just before uploading the package and then state this > product is based on this open source code. [...] Many words to tell: You don't trust a single contributor. You fear that that single contributor might add malicious code to the downloadset. So this is the reason why it makes a difference between Sun (more trusted, since a) company and b) team) and Contributor (only one, "who knows what he adds") > Another aspect. It seems current build process regarding Mac binaries is > done by a single person. I don't know how many machines are used. If a > build process is professionally done, there must be at least three > real/virtual machines for each platform: > > 1. Build machine > Build machine is a machine to build software products. This machine > should be a pure machine that does not have any unnecessary software > installed. "check" > 2. Sanity check machine > [...] > 3. Debug machine >[...] This is not part of the build-process, and not in the scope of the one that provides the builds, be it at Sun, be it an individual contributor, so that doesn't really make a difference. Even if you want to make this a hard requirement, this is not a reason why it makes a difference towards the liability towards the customer. > Openness > > Openness is one of the strong points that we can offer to our customers. > [...] > To make users satisfied from accountability's perspective of view, we should > promptly respond to a problem that they encounter. To quickly and > efficiently > attack the bug, we, QA team and responsible developers from relevant > project, > definitely will need build environment that produced the OpenOffice.org that > the customer has been using. This is a little contradiction to your "seperate machines" requirement you posted earlier. And: Most of the time the bug will not be fixed on the very same machine anyway. If it breaks, the bug is in the code, not in the buildmachine. If you really would need the very same machine, then there's something seriously broken beyond repair. > [...] > The builder can send his entire build environment to them. But why do we > need to make things so complex? That might be a requirement for a closed-source development, but OOo is opensource project. Every developer builds OOo on his/her own. So they don't need access to the very specific build-environment, they only need access to a comparable machine (PPC vs Intel for example) and even more important: A step-by-step instruction to reproduce/trigger the bug. And you forgot as well: Mac porting was long time done without Sun actively supporting it. Only recently Sun joined the efforts with dedicated developers. But of course the community developers still are there. And those don't have access to Sun's build-environment, only Sun has. And compared to independent developers, the developers at Sun might be working more hours on the code, but its number is small compared to the rest of the community. > [...] ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
