Hi,

Petr Mladek a écrit :
> Hi all,
>
> On Monday 04 December 2006 12:41, Charles Schulz wrote:
>   
>> Why not, indeed. But then there is an existing work and infrastructure.
>> I'm not saying it is the best one, far from that . And as you know,
>> there is also the idea of the MarketPlace, and the Extensions project,
>> not to mention the Art sub project at the Marketing project. The
>> Marketplace does not exist yet, but the extensions project and the Art
>> initiative do.
>>     
>
> It looks confusing. We should really start discussion between the project 
> owners and make clear what project is used for. The users and contributors 
> should find the things on reasonable locations.
>   

Big +1  to that, Petr. We should rationalize this stuff, together, so
that three needs can be adequately answered:
- the need to make OOo financially sustainable (more or less)
- that free (as in beer and in speech) content be made available easily
- that the locations of templates, content and more generally extensions
be rational and easy to find for users and the public in general.
>   
>> Well, I was confused between the two parts of the spec. I think that if
>> there had been an actual proposal for a new templates project a proposal
>> should have been drafted and sent to several lists. At this point
>> though, I think it should be welcome and perhaps more effective to take
>> away anything related to the repository of templates question out of the
>> existing spec.
>>     
>
> All the things on the wiki page are more or less related. For example, the 
> web 
> site should follow the proposed categories, the proposed categories would 
> affect the dialogs. This is why I have put them at one page. All things 
> cannot be implemented at once, though. I expected that we would create more 
> detailed page for each group of problems once they are being solved. I also 
> expected that the web site would be solved on a later stage because nobody 
> had time to work on it.
>   


I understand. Chicken -n'-egg problem. :-)

>   
>> The documentation project did not initally focus on templates, so the
>> activity of this project cannot be reduced to the numbers of templates
>> submitted. For instance, did you know that the french native-lang and
>> the japanese native-lang projects had their own set of local and
>> localized templates? It may not have been visible through the Internet
>> Archive though...
>>     
>
> This is why I was probably a bit confused ;-)
>
>   
>> Jan, don't take it personnally of course. I just think that given
>> Novell's quite hectic news and the reactions of many -my opinion
>> notwhistanding here- the way that Novell engineers could handle the
>> present situation on the templates do not help to improve the image of
>> Novell. That's very unfortunate. I'm just talking damage control and
>> public image, but of course I do understand that it is not your job .
>>     
>
> I hope that you have better feeling about us now ;-)
>   

Oh, I am loyal Suse user and didn't change after the announcement. If
you wish to know what I think about it, I wrote an article about that,
sorry for that shameless plug:
http://www.libervis.com/introducing_novells_cunning_plan  . I know quite
a bunch of people at Novell, wether in France or in the US. I know you
guys are not the vampires and daemons some write you are, whatever went
on with Redmond. I was just outlining that you should be aware that some
people might throw plates to you these days... :-[

>   
>> Jan, here's my "humple opinion" about the idea. I am not sure that the
>> documentation project would ultimately be the right place for hosting
>> templates. I think we have to take into account three factors. Of course
>> this is independent from the first part of the spec:
>> - the market place, commercial extensions for OOo
>> - the extensions project: what would be its role?
>> - a repository for the templates: should one part go to the market place
>> and the other one to the extensions project? Or should we create a new
>> repository? etc.
>>
>> So whatever you/we do, we have to include people from the documentation,
>> people from Sun/Novell, engineers, UI testers, marketing/art people, the
>> NLC community members, etc. In short, lots of people :-) .
>>     
>
> We have not started any work on the web site yet, so nothing is lost. I am 
> sure that we would double check the current status before we would start any 
> real implementation... For example, I wanted to check the new extension 
> project, ...
>
> Well, I would really differentiate the two areas at this point.
>
> The UI related thigs (dialogs, menu, ...) should be solved by the iTeam,
> http://wiki.services.openoffice.org/wiki/Feature_-_Templates#iTeam_Members
> I think that there is already enough people from all needed areas. Note that 
> more people can bring more ideas. Too extensive discussion usually is not 
> efective, though. Let's leave Jan to decide.
>   

It sounds reasonnable imho but let's let others speak.

> The remaining problem is what web site and project should host the templates 
> itself. We really should discuss it with the other people (add market place, 
> extensions, ...). Well, I will not have much time to work on it the following 
> weeks. Are you interested to start the communication with the other project 
> members yourself?
>   

I think I would. But we really have to take into account that
Marketplace idea from Hamburg, and the extensions project, and the Art
subproject, and God I'm losing my mind with all this. But yes, it should
be a collective effort.

> BTW: Have you read the ideas at 
> http://wiki.services.openoffice.org/wiki/Feature_-_Templates#Official_OOo_Templates_Web_Site
> What do you think about them? 
>   

Me? These ideas are just fine, but once again, we should ask the
involved parties or otherwise we'll disappoint members from the
community (Sun or others).


Thank you for your involvement,

Charles.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to