On Fri, 2006-05-05 at 11:36 -0400, Louis Suarez-Potts wrote:
> Hi All,
> 
> Sorry for the cross post; please respond on [EMAIL PROTECTED] 
> lang.openoffice.org.
> 
> 
> I would like to propose that we compile a single repository for all  
> material related to migrating to OpenOffice.org from MS Office. Right  
> now, we have lots of great stuff but it's all over the place and in  
> many languages.
> 
> My proposal:
> 
> * Create a wiki that cites all the material.
> 
> Thus, material in Spanish, on the ES project, could be listed here,  
> as could French, German and Brazilian Portuguese material; English  
> too.  (Note: listed, not placed here: URLS should be fine, though  
> ideally they should point to static HTML pages, not to files in Docs/ 
> Files sections or IZ.)

You mean like the dropdown list on http://documentation.openoffice.org/
for docs in languages other than English? Why duplicate? The support
page would seem to be a better target.


> 
> * Include (among other things):
> 
>       * Comparative matrices (like what Matthew Bennet did)

I have noticed that sometimes there are licensing problems with many
documents which precludes them from being made easily available. Are we
loosening the license requirements?

>       * White papers (analyses, case studies, etc.)

That would be nice but aren't these part of marketing? 

>       * User Guides (Documentation)

Already covered in the Project http://documentation.openoffice.org/

>       * Support (list support.openoffice.org)

Already a page, http://support.openoffice.org/index.html
>       * Clip art, templates, etc.
> 
> These can be in the language of their creation; we can state as much  
> on the wiki and also urge that they be translated to English, if need  
> be.

I am having difficultly wrapping my head around this.  Please explain
why the NLCs are not sufficient.  

> 
> I think this is an urgent issue.  I am weekly, if not more often,  
> asked for material of this nature.  Obviously, coordinating all this  
> and presenting it in a useful fashion has commercial potential. This  
> page would not really compete with such efforts; it would only list  
> what the community has done freely and what is available. It would  
> not tie it all together, nor would it speak to consulting, etc.,  
> though we can also refer to the consultants page.
> 

Then shouldn't this info be available on at least the support page?
Using the wiki for this seems a bit of fragmentation that really isn't
needed. I would rather use the wiki for developing documents. 



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

Reply via email to