Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Le 2010-11-03 01:25, jonathon a écrit :
Hash: SHA1

On 11/02/2010 05:43 PM, Marc Paré wrote:

The members would be picked according to their expertise in these categories.

The ability to create a template is more important that knowledge of the

If we were to setup a Templating Team group and published a large variety of templates, then the 
LibO suite would become more valuable as an Office suite for everyone.

My suggestion would to be provide a templating_team with the
specifications for the template, and let them create the template. A
clean room implementation of the template.

My idea was to provide a system for specialists in their own domain where they could devise templates for repetitive tasks. Then, Andy suggested a mentorship programme where a "templater" with more technical experience could then join the group and help them construct the templates. This is pretty well what you are suggesting, except that the mentor would be helping out the specialist with the hopes of teaching her/him the technical aspects of templating.

creating some templates for Evangelical church routines.

For some things, such as membership records, a database is required.
(I'm not going to get into a PICK v RDBM debate here.)

For others, a simple Write, Calc, or Impress template is suitable.

In an ideal situation, there is a database_creation team, that works in
conjunction with the template_creation team.

The template_creation team create a calc, impress, or write template,
that is then passed on to the database_creation team.  This (database)
team then determines whether this is something that is suitable for a
database, and if so, creates a database, and the associated interface

I like this too! So, there would be like a two tier templating team.

First tier: the category specialist (LibO member) would outline the template and with the help of the mentor work out the initial detail and if there is no need for a database, they would complete the template, arrange for testing, have some kind of review process and finally make it available in a template repository.

Second Tier: the specialist and mentor make note for the need of a database to complete the template. They may "rough in" the template and ready it for the template database dev and then submit it for the dev. The dev would then assess whether or not the use of a template would be the most elegant way to treat the template and if so, the template database dev would complete the template, return it to the specialist+mentor and they arrange for testing, have some kind of review process and finally make it available in a template repository.

[Database rant: LibO should either add SQLite as a built in database
engine, or else replace Base database engine with SQLite.]

My guess is that some, if not most of the databases, will have to be
constructed as extensions. For example, a genealogical database would
have to be able to both import, and export data in GEDCOM format.

Yes, the database debate rears its ugly head once again. How about, where it is possible to use Base in templates, then it will be used.

SQLite is used where needed (would have to install it from the Mageia Control Centre -- MCC :-) ) and GEDCOM import/export when needed. For sure, these would be used in a more complex template.

Do you know if many devs know their ins and outs of Base?

Actually, I think that this would work.

-- the specialist would be happy to participate if we gave him/her the title of "Categoryname Template dev maintainer" -- my rationale being that the specialist will be constructing templates with mentor help. This will give the specialist a sense of belonging.

-- the mentor dev would be working along side perhaps a person(s) with a substantial amount of experience in certain fields

-- the database dev would be happy working on certain short-term solutions where the end product is put out to people in specialised fields

How does this sound?


E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.