Hello Bernhard, Andre, Kami, all, I'm going to try to answer to everybody in one single email. Sophie pretty much summarized what I wanted to say. I'm just going to react to the the various reactions on this list: The specification itself (the way templates should be accessed into the office suite) is all right and I would say that this is a normal work. The problem, as Sophie pointed out, was that the scope of this page was much broader. It included the idea of a repository made comments on the documentation project, etc.
This page, as it seems, was not written by Kami, but by a so-called iTeam. I don't know what this is, sorry if I missed some news here. But its inspiration on several questions seems to come directly from Kami. I would simply like to know why the interested parties were not included, and worse, how we got to the point where nobody was actually asked to join. I do reiterate my demand that apologies should be made to Gerry and Scott from the Doc project. Wrt to Kami, it is true that I explained to everybody that I would help him include his works inside OOo. I tried. I tried very hard. In fact, with the 2.0.4 the relevance of a "premium" build of OOo would be much lessened, so I proposed Kami to integrate the OOo process itself: the developers wanted to have somebody care about the templates management (that was before the templates contest) and provide the QA (it is necessary for those as well). I proposed Kami to work on this and take charge of the templates collection, QA and management. Well he ended up refusing. Apparently having its own stuff on SourceForge was more important for him. I do ackowledge however that he agreed to change the name of his bundle and that he put it under the LGPL. Yet I keep receiving complaints, people who ask me who is this guy who spams the mailing lists. And no, "Oxygen Office" is not included inside the OOo community, no matter how good this idea can be. Because if it were, there would not be an OxyGen Office, there would be OOo, and a special goodies packages available on our site, not on SourceForge's. But enough with that. This idea of a template project may be good. The problem is not so much the idea itself than the way it has grown. We all know about the need for Hamburg to generate revenue. So we had an IRC session about that. There will be a market place. There will also be free extensions. Perhaps there will also be an extensions project with a different scope (free stuff, training, etc.) Now we learn about these templates. That's so confusing to me and to others. You see the point is that there is a total lack of communication not just between the developers and the non-coding community. It is also between the corporate developers and the non-corporate community. Superior instances may put these developers under pressure. But this is not a reason to act in this way. If you're under pressure, say it, make us understand you are. And for God'sake, let's coordinate and work together. None of us has anything to gain about this behaviour. And I do think again that for Novell engineers to jump in this story is really not appropriate. It simply credits the idea that you have chosen to step over the community and that this is an art in which you are excelling these days. Best, Charles. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
