On Sun, 2005-05-01 at 14:01, Daniel Carrera wrote: [snip] My apologies for not attending - (when I went to get up just before 3am my partner commented about not feeling well and thus I missed the meeting).
> In any event, I just uploaded the IRC logs. You can find them here: > > http://native-lang.openoffice.org/conference/ > > As I said, the discussion period was interesting and productive. Some of > the main conclusions were: > > * We need a wizard installer for add-ons. Something similar to FontOOo. A possible draft for discussion of such a wizard is available from: http://qa.openoffice.org/issues/show_bug.cgi?id=43532 > > * We should make it easy for people to submit addons. > To me, this has two aspects: 1. A tool and comprehendable guide for creating and uploading UNO packages 2. A repository for the UNO packages that the user wizard downloads the packages from. I note from the logs that there was considerable discussion about licensing of OOo extensions. Some other discussion on this list has seen Mathias Bauer state in response to my comment: > Philosophical issues include: > For an open source project do we want to encourage close source > additions? Of course, why not? Key Foskey was of the view that closed source extensions should be allowed but not encouraged. My personal view is that closed source extensions should be allowed but: * the closed source developers are responsible for a funding/locking mechanism * a warning that the extension is closed source and thus has not been scrutinised for malicious content etc. > * The importance of clear documentation. Ian Laurenson's work received > an honorable mention (ext.openoffice.org.nz). The wiki: http://ext.openoffice.org.nz is one resource, and I do hope that more people will join with me in making it a better resource. For example, I would really like someone to write some guidelines on producing multilingual extensions. I am aware of two approaches: 1. Resource files 2. Modules with language strings As I am barely monolingual I need guidance as to the merits of these approaches, or to recommend a standard approach. There are other resources which are worth mentioning including: The Macros and API and Code snippets forums available from: http://www.oooforum.org/forum/ And the code snippets site: http://codesnippets.services.openoffice.org/ > > * A call for the revival of the scripting project. Sophie, Laurent, > Agnes and myself are interested in contributing. Of course, we need > people who understand OOo's addon system (I don't). We hoped that Ian > Laurenson, Kevin Hendricks, Bernard Marcelly and Russ Phillips might be > interested. > I am definitely interested. A discussion on the [EMAIL PROTECTED] mail list suggested just working within the API project rather than having a separate scripting project. This made sense to me as I dislike the myriad OpenOffice.org related sites. But, to achieve the wiki in time for the Canberra conference I created yet another site. So wherever a more officially recognised OOo extension site ends up, I hope that it is sufficiently flexible to try new ideas such as having a wiki, that we don't get bogged down in endless discussion about licensing, and that we can get on and make things happen. > [remainder snipped] Thanks, Ian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
