Hi Ariel,

> the following message appeared in [EMAIL PROTECTED]
> ...
> 
> my proposal[1]: why not announcing and discussing this topics directly 
> in *this* API mailing list? (and let [EMAIL PROTECTED]/ 
> [EMAIL PROTECTED] for internal C++ API or whatever name 
> you give to the core C++ code)
> 
> They way I see it, we API clients are the "end-users" and "target 
> audience" of such announces/discussions, and I guess most people here 
> are not aware of, nor subscribed to, these interface-xxx mailing list; 
> so announcing/discussing here would be more "public" and fruitful.

Would be great if we could agree to this. I never liked publishing this
kind of changes in [EMAIL PROTECTED], as you know. Doing this here
will add a little traffic to the list (and really only little, since
most devs unfortunately do not announce their changes :), but much
better serve the intended target audience.

Ciao
Frank

> [1] not very original proposal, as already discussed in 
> http://dba.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=1967969
> Although there I suggested an [EMAIL PROTECTED], but 
> please no! there are already too many mailing lists in OOo.

Well - at some point in time (when all devs really announce all their
API changes), people might complain about too much traffic they're not
interested in. But it's of course sufficient to discuss a list
separation then, and not now.

Ciao
Frank

PS: Thanks for bringing up this topic!

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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

Reply via email to