Re:Re: build sw

[2]

Hi,
 Thanks you, I got it .
 I used "make clean debug=t" firstly, then used "make -sr debug=true"

Yi

At 2013-01-11 14:58:13,"Fan Zheng"  wrote:
>Well, I guess you misunderstand something.
>
>you said that you executed "build --from SW", means you want to just build
>the module SW right?
>
>The there may exist 2 issues:
>1. Before the partial build could be executed as you wished, the full build
>has to be finished at least once. Otherwise the dependent libraries and
>include files wont be the places they should be; For executing the full
>build, just execute "dmake -P4" in your step 3 (in the path where you
>execute step 2);
>2.  Such "build from" parameter is used for executing a partial/full build
>from the module you indicated and all the modules depend on said
>module. Commonly such execution way is only available in the installation
>package module named "instsetoo_native"; Inside the SW module package,
>execute the following one instead:
>"make -sr debug=true -j4";
>
>Hope this could solve your problems.
>
>
>
>
>
>2013/1/11 2 
>
>> Hi,
>>I couldn't complete sw building in partial build, when I input the
>> commands ,I got the messages as follow:
>> ===
>>  build -- version: 275224
>> This module has been migrated to GNU make.
>> You can only use build --all/--since here with build.pl.
>> To do the equivalent of 'build && deliver' call:
>> make -sr
>> in the module root (This will modify the solver).
>> =
>>
>>I don't how to deal with this problems.
>> there are the commands I input in cygwin:
>> 1.cd main
>> 2.source winenv.Set.sh
>> 3.cd sw
>> 4.build --from sw --prepare
>> 5.build debug=true --from sw

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Dave Fisher]

On Jan 11, 2013, at 12:05 PM, Marcus (OOo) wrote:

> Am 01/11/2013 03:06 PM, schrieb Jürgen Schmidt:
>> On 1/10/13 3:56 PM, Oliver-Rainer Wittmann wrote:
>>> Hi,
>>> 
>>> On 10.01.2013 11:55, Rony G. Flatscher wrote:
 Hi Oliver-Rainer,
 
 On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:
> I have finished the renaming from "OpenOffice.org" to "Apache
> OpenOffice" - see issue 121388.
> 
> Beside corresponding changes in the user interface this change has
> impact on the following
> important and critical stuff:
> - folder/directory names
> - package names
> - Windows registry key names and values
> - ...
> 
> As the folder/directory path to the user profile is also changed, the
> user profile of a former
> installed AOO (or OOo) version is not taken over.
 for installation script purposes of add-ons etc., where can one find
 the concrete strings for
 folder/directory names on the various operating system platforms and
 the Windows registry key names
 and values?
 
>>> 
>>> Unfortunately, there is no single place in the source code. I also had
>>> not the resources to clean this up during the renaming work - hint,
>>> hint, hint :-)
>>> 
>>> Please have a look at issue 121388, the wiki page referenced in one of
>>> the issue's comments and the intrinsic changes I have made.
>>> 
>>> The product installation folder is more or less a form of the
>>> $PRODUCTNAME + [major version number]. E.g.:
>>> - Windows: "Apache OpenOffice 3"
>>> - Linux: "apache_openoffice3"
>>> On Linux platforms we have also the basis installation folder. It name
>>> is found in /main/instsetoo_native/util/openoffice.lst
>>> 
>>> The user profile folder is more or less $PRODUCTNAME/[major version
>>> number]/
>>> 
>>> The Windows registry keys and values can be found in module main/scp2/
>>> 
>>> I hope that helps a little bit.
>> 
>> I was thinking about the name and here I mean the name that is used for
>> the folder etc. The name is used in the help, in tools option, in the
>> menu...
>> 
>> We changed "OpenOffice.org" to "Apache OpenOffice" so good so far. But
>> would it be nicer to shorten the folder, menu entries, ... to simply
>> OpenOffice
>> 
>> Folders
>> Linux: /opt/openoffice4
>> Mac: OpenOffice.app
>> Windows: OpenOffice 4
>> 
>> Tools Option
>> OpenOffice
>> OpenOffice Writer
>> OpenOffice ...
>> 
>> Help
>> OpenOffice instead of hundreds of "Apache OpenOffice"
>> 
>> The idea is that the project and product is called Apache OpenOffice but
>> in practice we would use in the product the short from OpenOffice. The
>> intro, start center, about can of course use images where we use "Apache
>> OpenOffice".
>> 
>> Well it's just an idea and I know it would require some further work but
>> now would be the time for it. I believe legally should it be ok today
>> but it have to checked to be safe.
>> 
>> What's your opinion?
> 
> In general a very good idea: Shorter menu entries, etc. and a higher 
> attention of the open source product.
> 
> And yes, we should get this clarified from trademarks@.

If it is called Apache OpenOffice software or product on first use on certain 
pages then it is permissible to use short forms like OpenOffice in various 
places. There is no trouble with that approach. Look at the Apache Hadoop 
project's home page - http://hadoop.apache.org/

We should make sure that somewhere we use OpenOffice.org ® for the link to the 
website to preserve that trademark in certain jurisdictions.

Regards,
Dave


> 
> Marcus
> 

Re: Decision Making Module

[Kay Schenk]

Hello Brandon,

Thanks for letting us know how your progress is going.

Hopefully, you'll feel more comfortable soon to subscribe to one of our
mailing lists -- dev, marketing, or doc -- so you can interact more.

We'd love to hear to hear from you and help you in your volunteering
efforts.

On Thu, Jan 10, 2013 at 2:45 PM, Brandon McCartney wrote:

> Dev Community,
>
> I am working on the "Decision Making Module".
>
> Brandon
>



-- 

MzK

"No act of kindness, no matter how small, is ever wasted."
 --
Aesop

Re: [FOSDEM]: At your service on Saturday

[Sylvain DENIS]

Hello
I have the chair. (One or two in my car :-) )
Sylvain
Le 11 janv. 2013 23:11, "Andrea Pescetti"  a écrit :

> Fabrizio Marchesano wrote:
>
>> Assuming that I'll take enough coffee to be responsive since Saturday
>> morning (don't take it for granted ;-) ), if I can give a hand just let me
>> know how.
>>
>
> Thank you Fabrizio, I've taken note of your availability on the page where
> we list available volunteers for the stand/booth:
> https://cwiki.apache.org/**confluence/display/OOOUSERS/**
> FOSDEM+2013+Organization
>
> The stand is just one table, so it will definitely be overcrowded if all
> of us are there simultaneously. We will attend to it 2-3 people at a time,
> according to everyone's availability. Everybody can edit that wiki page.
>
> See you in Brussels!
>
> Regards,
>   Andrea.
>

Re: [FOSDEM]: At your service on Saturday

[Andrea Pescetti]

Fabrizio Marchesano wrote:

Assuming that I'll take enough coffee to be responsive since Saturday
morning (don't take it for granted ;-) ), if I can give a hand just let me
know how.


Thank you Fabrizio, I've taken note of your availability on the page 
where we list available volunteers for the stand/booth:

https://cwiki.apache.org/confluence/display/OOOUSERS/FOSDEM+2013+Organization

The stand is just one table, so it will definitely be overcrowded if all 
of us are there simultaneously. We will attend to it 2-3 people at a 
time, according to everyone's availability. Everybody can edit that wiki 
page.


See you in Brussels!

Regards,
  Andrea.

Re: "dist" move...

[Marcus (OOo)]

Am 01/11/2013 11:41 AM, schrieb Jürgen Schmidt:

On 12/6/12 10:18 PM, Dave Fisher wrote:


On Dec 6, 2012, at 11:36 AM, Andrew Rist wrote:



On 12/6/2012 9:40 AM, Kay Schenk wrote:

On Thu, Dec 6, 2012 at 12:17 AM, Herbert Duerr  wrote:

On 06.12.2012 00:03, Kay Schenk wrote:

I put in a request, as part of our graduation process, to have our
"dist" area moved to a top level.

INFRA-5607

https://issues.apache.org/jira/browse/INFRA-5607


The issue is requesting a move to http://www.apache.org/dist/ooo, but
shouldn't this better be named */openoffice (or */aoo)?

Herbert

Herbert -- see comments by Henk on the ticket. It does appear that
/dist/openoffice will be the new top-level name for our *next* release
-- nothing will be moved now. Perhaps this was already communicated to
infra and I was not aware of it.

Also, of more immediate concern is the archiving of the 3.4.0 source
release and possibly the 3.3. patch.


All of this is driven by the nature of /dist/, how it is mirrored outside 
Apache, and the pretty substantial resources taken up by our release.
There are consequences to moving something once it is there - some mirrors 
might end up with both areas mirrored, for example.
The best way to resolve that (in the opinion of infra - AIUI) is to move the 
location on our next release, this allows for planing of resources and the 
notification of the mirror network.   It seems a reasonable approach to me.


This is the direction the comments are going in Kay's issue.

Since the 3.4.1 Language packs are supplements to the 3.4.1 source release and 
will have incubator branding they will go into the incubator/ooo/ location.

Some might think that we should be doing a full 3.4.2 with non-incubator 
branding, but no real need IMO.



What does it mean for our upcoming respin of AOO 3.4.1? Taking the
discussion into account I plan to do the following.

1. copy the new src release ("") to
www.apache.org/dist/incubator/ooo/3.4.1/source besides the former 3.4.1
src release. Please notice that the name includes now a revision number.


Ah, thanks for the reminder.


2. copy the the new binaries besides the existing ones under
www.apache.org/dist/incubator/ooo/files/stable/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/ast/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/da/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/eu/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/gd/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/pl/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/ko/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/nb/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/sv/3.4.1


OK


With the next release AOO 4.0 we will have a new name without
"incubating" and I plan to reorganize the directory structure to
simplify it. I know we had a discussion about it in the past and I will
continue there or will start a new thread on this topic separately. I
would like to plan this asap to be prepared and to have enough time to
adapt the download scripts etc.


Please have a look here to see the work that was done already:

https://cwiki.apache.org/confluence/display/OOOUSERS/Improvements+for+the+download+webpages#Improvementsforthedownloadwebpages-Reworktostartoverwiththenextbiggerrelease%28AOO3.5%2C4.0%2Cetc.%29

(Part #2)

It should be possible to go on from here.

Marcus

Re: [WEBSITE] broken link on mac porting page

[Rob Weir]

On Fri, Jan 11, 2013 at 3:28 PM, Marcus (OOo)  wrote:
> Am 01/11/2013 12:36 AM, schrieb Rob Weir:
>
>> On Thu, Jan 10, 2013 at 5:18 PM, Marcus (OOo)
>> wrote:
>>>
>>> Am 01/10/2013 10:59 PM, schrieb Rob Weir:
>>>
 On Thu, Jan 10, 2013 at 4:36 PM, Marcus (OOo)
 wrote:
>
>
> Am 01/08/2013 09:37 PM, schrieb Andrea Pescetti:
>
>> On 07/01/2013 Marcus (OOo) wrote:
>>>
>>>
>>>
>>> Am 01/07/2013 09:54 PM, schrieb Rob Weir:



 http://www.openoffice.org/porting/mac/
 So I'd recommend either keeping the page and updating it. Or
 replacing it with a page that says that the Mac port is now full
 integrated with our releases and then link to the download page. Or
 put in a 401 redirect from that URL to the download page. ...
>>>
>>>
>>>
>>> OK, then I prefer to use a redirect to the download area.
>>
>>
>>
>>
>> Sounds good. Actually, we can redirect everything under
>>
>> http://www.openoffice.org/porting/mac/
>>
>> to the homepage, since links on the old page include support,
>> screenshots, downloads... all resources directly available from the
>> project homepage.
>
>
>
>
> Then I would like to volunteer to try this on Sunday.
>

 Hi Marcus,

 I took a closer look at the data and I have some concerns from an SEO
 perspective.

 We get a large number of visits from users who query Google for terms
 like:

 openoffice for mac
 open office mac
 openoffice mac
 free office for mac
 download openoffice for mac

 Try these queries in your browser.   See the porting page is the
 number one hit.  For me the 2nd hit is CNet and then we start hitting
 malware sites.  We don't get another openoffice.org web page until
 position #10 in the search results.

 If we redirect to the home page, which does not mention "Mac"
 anywhere, then the next time Google updates its index it will see that
 as the contents of /porting/mac and judge it to be far less relevant
 to queries like "openoffice for mac".
>>>
>>>
>>>
>>> Does it help to leave some keywords on the "/porting/mac/index.html"?
>>> The the Google indexing bot recognize it, redirects then to the new
>>> webpage
>>> and we keep the search hits.
>>>
>>
>> If you do a redirect at the HTTP level then Google won't ever see the
>> contents of the /porting/mac pages.  It will only see the destination
>> page's contents.
>>
>> You could possibly do a>>>
 1) Create a new landing page for users interested in OpenOffice for
 Mac. Maybe it is at http://www.openoffice.org/mac.  Maybe it is based
 on whatever is relevant still from /porting/mac.  It doesn't need tons
 of content, but enough to be relevant.

 2) Redirect /porting/mac/* to /mac/index.html

 3) Delete the old /porting/mac
>>>
>>>
>>>
>>> Why does a Google search behave different here? Sorry, I don't see the
>>> difference to just redirect.
>>>
>>
>> The redirect would work the same way.  The difference is in the
>> contents of the landing page.  If we redirect to the home page, or the
>> download page, there is almost no discussion about Mac OpenOffice.
>> The old page, even if the content is out-of-date, is still seen as
>> relevant.
>
>
> OK, so the difference is to leave the keywords on the target webpage and not
> on the one that is redirecting.
>

Yes.

> To create "http://www.openoffice.org/mac"; with some content helping to keep
> the Google hits high and a big, visible download link (which points to the
> actual download webpage) should be hopefully enough.
>

The current .porting/mac page isn't fancy, but it does have a central
"Get the latest Apache OpenOffice release for your MacOS X." with a
link to the download page.

I'd keep it simple.  What is the minimum amount of information a Mac
user needs to know?   Maybe, what versions of MacOS are supported?
Maybe anything special to know about installing with Lion security?
That plus a download link.

Regards,

-Rob

> Right?
>
>
>>> PS:
>>> I want to get rid of the old content but of course not loose the Google
>>> search hits.
>>>
>>
>> Me too ;-)
>>
>> -Rob
>>
>>
>>> Marcus
>
>
> Marcus

Re: [WEBSITE] broken link on mac porting page

[Marcus (OOo)]

Am 01/11/2013 12:36 AM, schrieb Rob Weir:

On Thu, Jan 10, 2013 at 5:18 PM, Marcus (OOo)  wrote:

Am 01/10/2013 10:59 PM, schrieb Rob Weir:


On Thu, Jan 10, 2013 at 4:36 PM, Marcus (OOo)
wrote:


Am 01/08/2013 09:37 PM, schrieb Andrea Pescetti:


On 07/01/2013 Marcus (OOo) wrote:



Am 01/07/2013 09:54 PM, schrieb Rob Weir:



http://www.openoffice.org/porting/mac/
So I'd recommend either keeping the page and updating it. Or
replacing it with a page that says that the Mac port is now full
integrated with our releases and then link to the download page. Or
put in a 401 redirect from that URL to the download page. ...



OK, then I prefer to use a redirect to the download area.




Sounds good. Actually, we can redirect everything under

http://www.openoffice.org/porting/mac/

to the homepage, since links on the old page include support,
screenshots, downloads... all resources directly available from the
project homepage.




Then I would like to volunteer to try this on Sunday.



Hi Marcus,

I took a closer look at the data and I have some concerns from an SEO
perspective.

We get a large number of visits from users who query Google for terms
like:

openoffice for mac
open office mac
openoffice mac
free office for mac
download openoffice for mac

Try these queries in your browser.   See the porting page is the
number one hit.  For me the 2nd hit is CNet and then we start hitting
malware sites.  We don't get another openoffice.org web page until
position #10 in the search results.

If we redirect to the home page, which does not mention "Mac"
anywhere, then the next time Google updates its index it will see that
as the contents of /porting/mac and judge it to be far less relevant
to queries like "openoffice for mac".



Does it help to leave some keywords on the "/porting/mac/index.html"?
The the Google indexing bot recognize it, redirects then to the new webpage
and we keep the search hits.



If you do a redirect at the HTTP level then Google won't ever see the
contents of the /porting/mac pages.  It will only see the destination
page's contents.

You could possibly do a

I thought about to do it this way. Is there a better way?


So I think we should consider this carefully.



Of course.



Is there anything

actually wrong with the /porting/mac page as it is?



Ahm, besides totally outdated and no longer needed data not. ;-)

When I look around there is nearly nothing that should be kept (links,
screenshots, X11<-->  Aqua, release news about older versions, FAQs).



OK.  I am not a Mac person.  Is there anything useful we could say
about OpenOffice on the Mac?  Any FAQ's?  Any useful instructions?




Here's an alternative idea.  If the issue is that this is no longer a
"porting" project, then maybe we could do something like this:

1) Create a new landing page for users interested in OpenOffice for
Mac. Maybe it is at http://www.openoffice.org/mac.  Maybe it is based
on whatever is relevant still from /porting/mac.  It doesn't need tons
of content, but enough to be relevant.

2) Redirect /porting/mac/* to /mac/index.html

3) Delete the old /porting/mac



Why does a Google search behave different here? Sorry, I don't see the
difference to just redirect.



The redirect would work the same way.  The difference is in the
contents of the landing page.  If we redirect to the home page, or the
download page, there is almost no discussion about Mac OpenOffice.
The old page, even if the content is out-of-date, is still seen as
relevant.


OK, so the difference is to leave the keywords on the target webpage and 
not on the one that is redirecting.


To create "http://www.openoffice.org/mac"; with some content helping to 
keep the Google hits high and a big, visible download link (which points 
to the actual download webpage) should be hopefully enough.


Right?


PS:
I want to get rid of the old content but of course not loose the Google
search hits.



Me too ;-)

-Rob



Marcus


Marcus

Re: [RELEASE]: AOO 3.4.1 respin

[Marcus (OOo)]

Am 01/11/2013 11:16 AM, schrieb Jürgen Schmidt:

On 1/10/13 10:29 PM, Marcus (OOo) wrote:

Am 01/10/2013 07:07 PM, schrieb Kay Schenk:

On Thu, Jan 10, 2013 at 8:43 AM, Jürgen
Schmidtwrote:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 1/10/13 1:38 PM, Ariel Constenla-Haile wrote:

On Wed, Jan 09, 2013 at 10:56:46AM +0100, Jürgen Schmidt wrote:

I will start the build of the first official AOO 3.4.1 respin
snapshot today based on revision 1424891 on the AOO34 branch.

The new supported languages are "ast", "da", "eu", "gd", "pl",
"ko", "nb", "sv".

I will built a new updated source release, including the
translation updates. The only further change is in the scripts
for building the source release where I include the revision
number.

@Ariel: can you please start the build for Linux as well?


Linux packages are available at
http://people.apache.org/~arielch/packages/respin_aoo341



The first snapshot build is now available and you can find the bits
under

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1.respin


Please let me know if there is problem with the links.

If possilbe I would like to move the release date to Jan 24th. I will
be on a business trip for the rest of Jan. starting on 26th and have
not really time to handle it at this time.

Juergen



Ok, so this is a week earlier than we originally anticipated.

thanks for the heads-up.


Juergen, any idea of the time you want to execute the release?

At least for me more important than the day itself. ;-)


we can propably prepare everything in front of it or not. Adding further
languages shouldn't be too difficult if the files are located in the
same place and using the same naming convention.


Of course, even if it's not much, we should prepare this work.


But anyway which time would work best for you?


As my daily job don't belong to OpenOffice I can help only in the 
evening hours (CET timezone). Maybe it's possible at this day to come 
home a bit earlier. I'll try and let you know a few days before 24th Jan.


Marcus

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Marcus (OOo)]

Am 01/11/2013 03:06 PM, schrieb Jürgen Schmidt:

On 1/10/13 3:56 PM, Oliver-Rainer Wittmann wrote:

Hi,

On 10.01.2013 11:55, Rony G. Flatscher wrote:

Hi Oliver-Rainer,

On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:

I have finished the renaming from "OpenOffice.org" to "Apache
OpenOffice" - see issue 121388.

Beside corresponding changes in the user interface this change has
impact on the following
important and critical stuff:
- folder/directory names
- package names
- Windows registry key names and values
- ...

As the folder/directory path to the user profile is also changed, the
user profile of a former
installed AOO (or OOo) version is not taken over.

for installation script purposes of add-ons etc., where can one find
the concrete strings for
folder/directory names on the various operating system platforms and
the Windows registry key names
and values?



Unfortunately, there is no single place in the source code. I also had
not the resources to clean this up during the renaming work - hint,
hint, hint :-)

Please have a look at issue 121388, the wiki page referenced in one of
the issue's comments and the intrinsic changes I have made.

The product installation folder is more or less a form of the
$PRODUCTNAME + [major version number]. E.g.:
- Windows: "Apache OpenOffice 3"
- Linux: "apache_openoffice3"
On Linux platforms we have also the basis installation folder. It name
is found in /main/instsetoo_native/util/openoffice.lst

The user profile folder is more or less $PRODUCTNAME/[major version
number]/

The Windows registry keys and values can be found in module main/scp2/

I hope that helps a little bit.


I was thinking about the name and here I mean the name that is used for
the folder etc. The name is used in the help, in tools option, in the
menu...

We changed "OpenOffice.org" to "Apache OpenOffice" so good so far. But
would it be nicer to shorten the folder, menu entries, ... to simply
OpenOffice

Folders
Linux: /opt/openoffice4
Mac: OpenOffice.app
Windows: OpenOffice 4

Tools Option
OpenOffice
OpenOffice Writer
OpenOffice ...

Help
OpenOffice instead of hundreds of "Apache OpenOffice"

The idea is that the project and product is called Apache OpenOffice but
in practice we would use in the product the short from OpenOffice. The
intro, start center, about can of course use images where we use "Apache
OpenOffice".

Well it's just an idea and I know it would require some further work but
now would be the time for it. I believe legally should it be ok today
but it have to checked to be safe.

What's your opinion?


In general a very good idea: Shorter menu entries, etc. and a higher 
attention of the open source product.


And yes, we should get this clarified from trademarks@.

Marcus

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Marcus (OOo)]

Am 01/11/2013 03:31 PM, schrieb Rob Weir:

On Fri, Jan 11, 2013 at 9:06 AM, Jürgen Schmidt  wrote:

On 1/10/13 3:56 PM, Oliver-Rainer Wittmann wrote:

Hi,

On 10.01.2013 11:55, Rony G. Flatscher wrote:

Hi Oliver-Rainer,

On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:

I have finished the renaming from "OpenOffice.org" to "Apache
OpenOffice" - see issue 121388.

Beside corresponding changes in the user interface this change has
impact on the following
important and critical stuff:
- folder/directory names
- package names
- Windows registry key names and values
- ...

As the folder/directory path to the user profile is also changed, the
user profile of a former
installed AOO (or OOo) version is not taken over.

for installation script purposes of add-ons etc., where can one find
the concrete strings for
folder/directory names on the various operating system platforms and
the Windows registry key names
and values?



Unfortunately, there is no single place in the source code. I also had
not the resources to clean this up during the renaming work - hint,
hint, hint :-)

Please have a look at issue 121388, the wiki page referenced in one of
the issue's comments and the intrinsic changes I have made.

The product installation folder is more or less a form of the
$PRODUCTNAME + [major version number]. E.g.:
- Windows: "Apache OpenOffice 3"
- Linux: "apache_openoffice3"
On Linux platforms we have also the basis installation folder. It name
is found in /main/instsetoo_native/util/openoffice.lst

The user profile folder is more or less $PRODUCTNAME/[major version
number]/

The Windows registry keys and values can be found in module main/scp2/

I hope that helps a little bit.


I was thinking about the name and here I mean the name that is used for
the folder etc. The name is used in the help, in tools option, in the
menu...

We changed "OpenOffice.org" to "Apache OpenOffice" so good so far. But
would it be nicer to shorten the folder, menu entries, ... to simply
OpenOffice

Folders
Linux: /opt/openoffice4
Mac: OpenOffice.app
Windows: OpenOffice 4



or even OpenOffice4, avoiding a space in the directory name, a source
of much pain in Windows.


even when I nearly don't use any Windows, I support to prevent any error 
prone file and directory naming - which was proven many time in the 
past, IMHO.


Marcus




Tools Option
OpenOffice
OpenOffice Writer
OpenOffice ...

Help
OpenOffice instead of hundreds of "Apache OpenOffice"

The idea is that the project and product is called Apache OpenOffice but
in practice we would use in the product the short from OpenOffice. The
intro, start center, about can of course use images where we use "Apache
OpenOffice".

Well it's just an idea and I know it would require some further work but
now would be the time for it. I believe legally should it be ok today
but it have to checked to be safe.

What's your opinion?

Juergen

WIKI, down for change

[janI]

Hi.

MWIKI is down at the moment, I try to get it up again...but I will take it
down tonight (GMT:1900-2400) for upgrading to a new VM.

Sorry for the inconvience, but there are 3 persons who have root access, so
I allowed myself a day off in real life 

rgds
Jan I.

Re: "dist" move...

[Kay Schenk]

On Fri, Jan 11, 2013 at 2:41 AM, Jürgen Schmidt wrote:

> On 12/6/12 10:18 PM, Dave Fisher wrote:
> >
> > On Dec 6, 2012, at 11:36 AM, Andrew Rist wrote:
> >
> >>
> >> On 12/6/2012 9:40 AM, Kay Schenk wrote:
> >>> On Thu, Dec 6, 2012 at 12:17 AM, Herbert Duerr  wrote:
>  On 06.12.2012 00:03, Kay Schenk wrote:
> > I put in a request, as part of our graduation process, to have our
> > "dist" area moved to a top level.
> >
> > INFRA-5607
> >
> > https://issues.apache.org/jira/browse/INFRA-5607
> 
>  The issue is requesting a move to http://www.apache.org/dist/ooo, but
>  shouldn't this better be named */openoffice (or */aoo)?
> 
>  Herbert
> >>> Herbert -- see comments by Henk on the ticket. It does appear that
> >>> /dist/openoffice will be the new top-level name for our *next* release
> >>> -- nothing will be moved now. Perhaps this was already communicated to
> >>> infra and I was not aware of it.
> >>>
> >>> Also, of more immediate concern is the archiving of the 3.4.0 source
> >>> release and possibly the 3.3. patch.
> >>>
> >> All of this is driven by the nature of /dist/, how it is mirrored
> outside Apache, and the pretty substantial resources taken up by our
> release.
> >> There are consequences to moving something once it is there - some
> mirrors might end up with both areas mirrored, for example.
> >> The best way to resolve that (in the opinion of infra - AIUI) is to
> move the location on our next release, this allows for planing of resources
> and the notification of the mirror network.   It seems a reasonable
> approach to me.
> >
> > This is the direction the comments are going in Kay's issue.
> >
> > Since the 3.4.1 Language packs are supplements to the 3.4.1 source
> release and will have incubator branding they will go into the
> incubator/ooo/ location.
> >
> > Some might think that we should be doing a full 3.4.2 with non-incubator
> branding, but no real need IMO.
> >
>
> What does it mean for our upcoming respin of AOO 3.4.1? Taking the
> discussion into account I plan to do the following.
>
> 1. copy the new src release ("") to
> www.apache.org/dist/incubator/ooo/3.4.1/source besides the former 3.4.1
> src release. Please notice that the name includes now a revision number.
>
> 2. copy the the new binaries besides the existing ones under
> www.apache.org/dist/incubator/ooo/files/stable/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/ast/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/da/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/eu/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/gd/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/pl/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/ko/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/nb/3.4.1
> www.apache.org/dist/incubator/ooo/files/localized/sv/3.4.1
>

 I think the consensus/suggestion from infra was YES to all the above. Just
add the new languages in to the existing incubator "dist" area despite the
fact that we are no longer in incubation.


>
> With the next release AOO 4.0 we will have a new name without
> "incubating" and I plan to reorganize the directory structure to
> simplify it.


Yes.



> I know we had a discussion about it in the past and I will
> continue there or will start a new thread on this topic separately.


OK, good...we need to go over this again. And Sourceforge needs a heads up
as well I think.


> I
> would like to plan this asap to be prepared and to have enough time to
> adapt the download scripts etc.
>
> Juergen
>
>





-- 

MzK

"No act of kindness, no matter how small, is ever wasted."
 --
Aesop

Re: Symphony code in AOO 4.0

[Kay Schenk]

On Fri, Jan 11, 2013 at 1:20 AM, Shenfeng Liu  wrote:

> 2013/1/11 Rob Weir 
>
> > On Thu, Jan 10, 2013 at 8:03 PM, Andrea Pescetti 
> > wrote:
> > > Rob Weir wrote:
> > >>
> > >> I'm reading FUD, from the usual misinformed suspects ... I
> > >>
> > >> can certainly sympathize with leaders of communities that can only be
> > >> held together by irrational fears.  It is not easy to maintain that
> > >> peak level of paranoia.
> > >
> > >
> > > Your personal opinions on the people involved (I admit I have very
> little
> > > context, I only had the time to read the discussion here but nothing
> > else so
> > > far) are best kept separated from the important fact, that is that
> > > apparently incorrect information is being circulated about the benefits
> > that
> > > the Symphony donation is bringing to OpenOffice and to the
> > free/open-source
> > > software world in general.
> > >
> > >
> > >> Anyone who cares to look can
> > >> see that we've actually integrated quite a but of Symphony code into
> > >> the AOO trunk already.   For example, the following 167 bug fixes
> > >
> > >
> > > People don't care to look, unfortunately... But I definitely agree that
> > this
> > > listing is impressive, as it is this page:
> > >
> >
> http://wiki.openoffice.org/wiki/Documentation/Fidelity_Improvement_Since_AOO341
> > >
> > > If you manage to co-author a blog post with Shenfeng Liu (or someone
> else
> > > from the former Symphony team) about the integrated fixes/features,
> this
> > > will be an important service to the OpenOffice users. But please, let's
> > do
> > > it because it's important in itself and because it's clearly overdue
> > (aside
> > > from a brief mention in the "top 10 questions" posts), not because
> > someone
> > > feels the need to address some particular wrong or misleading claim.
> > >
> >
> > Clarifying the facts where misinformation is being spread is part of
> > the necessary communications that any project needs to engage in.  We
> > saw that as a podling, when the ASF itself addressed misinformation
> > regarding this project.  Now this is our responsibility.
> >
> > Of course, misinformation about insubstantial matters is best ignored.
> >  But where misinformation is propagated about substantial project
> > operations, then that is sufficient motivation for the contents and
> > timing of a post to correct such misinformation.
> >
> > In any case, pointing out the lie on this list already gives 90% of
> > the benefit, since such FUD cannot survive the light of day.  A blog
> > post is unnecessary.
> >
>
> IMHO, we can consider a blog post about our progress on the 4.0 release,
> including the contents we are working on, e.g. fidelity,
> performance&reliability, accessibility, usability, enhanced platform
> support... Symphony's contribution is part of this story.
> If we decided to post it, I'd like to be the co-author.
> Thanks!
>
> - Shenfeng (Simon)
>

Yes, this is a good idea! I would suggest we wait until the 3.4.1 re-spin
is done on Jan 24th to do this, though.

I could have sworn that when we put out the blog post on Nov. 21 for
Marketing volunteers that we had a link in to the release planning for 4.0
-- this would be
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Release+Planning--
but I don't see a link now looking at:
https://blogs.apache.org/OOo/.

 So, hmmmmaybe a new blog on 4.0 status would help?


>
>
>
>
> >
> > -Rob
> >
> > > Regards,
> > >   Andrea.
> >
>



-- 

MzK

"No act of kindness, no matter how small, is ever wasted."
 --
Aesop

Re: [RELEASE]: AOO 3.4.1 respin

[Jürgen Schmidt]

On 1/11/13 5:32 PM, Xuacu wrote:
> Hi Juergen, all
> 
> Hopefully It's not too late to include Asturian spellchecker in AOO
> 3.4.1. I've created an issue here:
> https://issues.apache.org/ooo/show_bug.cgi?id=121610
> 
> I downloaded and tested it with current Asturian build and, after a
> quick test, it all works as expected. Dictionary is a good quality
> one, even i it's still unfinished.

I will include it in the next snapshot

Thanks

Juergen

> 
> Best regards
> --
> Xuacu
> 
> 2013/1/7 Jürgen Schmidt :
>> Hi,
>>
>> I plan now with the following 8 languages for our upcoming AOO 3.4 1 respin:
>>
>> Danish (da), Swedish (sv), Norwegian Bokmal (nb), Polish (pl), Korean
>> (ko), Asturian (ast), Basque (eu), Scottish Gaelic (gd)
>>
>> Please correct me if I should have missed something!
>>
>> So far we have only received information for Danish about the dictionary
>> that we should bundle. If we should bundle a dictionary for one of these
>> languages please let us know until tomorrow. Please create an issue for
>> this, see
>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+Respin+for+additional+languages
>>
>> All other languages where volunteers are working on updates, please
>> continue your work and we will integrate your work on trunk immediately
>> that you can benefit from our regular snapshot builds.
>>
>> AOO 4.0 is coming soon and we will have to do some work for this release
>> as well. Some strings moved in other locations (modules) and we will
>> have some new UI elements that require translation. But mainly strings
>> that are already translated somewhere else. I will keep you informed.
>>
>> Juergen

Re: [RELEASE]: AOO 3.4.1 respin

[Xuacu]

Hi Juergen, all

Hopefully It's not too late to include Asturian spellchecker in AOO
3.4.1. I've created an issue here:
https://issues.apache.org/ooo/show_bug.cgi?id=121610

I downloaded and tested it with current Asturian build and, after a
quick test, it all works as expected. Dictionary is a good quality
one, even i it's still unfinished.

Best regards
--
Xuacu

2013/1/7 Jürgen Schmidt :
> Hi,
>
> I plan now with the following 8 languages for our upcoming AOO 3.4 1 respin:
>
> Danish (da), Swedish (sv), Norwegian Bokmal (nb), Polish (pl), Korean
> (ko), Asturian (ast), Basque (eu), Scottish Gaelic (gd)
>
> Please correct me if I should have missed something!
>
> So far we have only received information for Danish about the dictionary
> that we should bundle. If we should bundle a dictionary for one of these
> languages please let us know until tomorrow. Please create an issue for
> this, see
> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+3.4.1+Respin+for+additional+languages
>
> All other languages where volunteers are working on updates, please
> continue your work and we will integrate your work on trunk immediately
> that you can benefit from our regular snapshot builds.
>
> AOO 4.0 is coming soon and we will have to do some work for this release
> as well. Some strings moved in other locations (modules) and we will
> have some new UI elements that require translation. But mainly strings
> that are already translated somewhere else. I will keep you informed.
>
> Juergen

Re: Possible broken link: other

[imacat]

On 2013/01/11 23:46, Jürgen Schmidt said:
> On 1/11/13 4:35 PM, j...@autostage.de wrote:
>> Hello,
>>
>> this links are not working:
>>
>> http://wiki.openoffice.org/wiki/Documentation/BASIC_Guide
>> http://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide

Thanks for the reporting.  We are working on restoring it now.

> 
> the wiki has a technical problem at the moment, should be back soon
> hopefully
> 
> Juergen
> 
>>
>> Cheers,
>> Jens
>>
>> _
>>
>> mediaengineer - Ingenieurbüro für CAD und technische Planungen
>>
>> Dipl. Ing. (FH) Jens Mueller
>>
>> Grafenwerthstraße 18
>> 50937 Köln
>>
>> mobil: +49 (0) 172 30 68 072
>> büro: +49 (0) 221 299 88 80
>> fax: +49 (0) 221 299 88 79
>>
>> j...@autostage.de
>>
>> www.autostage.de
>> www.mediaengineer.de
>>
>> !! Bitte drucken Sie diese Email nur, wenn Sie unbedingt müssen. Der Umwelt 
>> zuliebe !!
>> !! please don't print this e-mail unless you really need to !!
>>
>>
> 


-- 
Best regards,
imacat ^_*' 
PGP Key http://www.imacat.idv.tw/me/pgpkey.asc

<> News: http://www.wov.idv.tw/
Tavern IMACAT's http://www.imacat.idv.tw/
Woman in FOSS in Taiwan http://wofoss.blogspot.com/
OpenOffice http://www.openoffice.org/
EducOO/OOo4Kids Taiwan http://www.educoo.tw/
Greenfoot Taiwan http://greenfoot.westart.tw/



signature.asc
Description: OpenPGP digital signature

Re: Introduction and Question

[Jonathan Simona]

Hi, unfortunately I'm currently using the Windows OS (I really should
switch to Linux). I've finished downloading the source code and am just
waiting to wiki to get back up so I can start trying to build it.

On Fri, Jan 11, 2013 at 2:59 AM, Ariel Constenla-Haile
wrote:

> Hi Jonathan,
>
> On Thu, Jan 10, 2013 at 10:22:24PM -0800, Jonathan Simona wrote:
> > Thanks so much for the replies! Unfortunately I do not know how to build
> > and run AOO and can't seem to find out because the wiki link seems to be
> > down.I'm not sure if this problem is only occuring for me, but I will
> > attempt to build when wiki comes back up.
> >
> > Wiki's error message:
> > A database error has occurred. Did you forget to run
> maintenance/update.php
> > after upgrading? See:
> > https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
> > Query: SELECT page_id,page_len,page_is_redirect,page_latest FROM `page`
> > WHERE page_namespace = '10' AND page_title = 'Extension_DPL' LIMIT 1
> > Function: LinkCache::addLinkObj
> > Error: 1286 Unknown table engine 'InnoDB' (localhost)
>
> Yes, the wiki seems to be dead. While it gets fixed, you can checkout
> the source code.
>
> Are you working on Windows, Linux, MacOS? Depending on the system, you
> may have all the tools at hand to checkout source.
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
>

Re: Possible broken link: other

[Jürgen Schmidt]

On 1/11/13 4:35 PM, j...@autostage.de wrote:
> Hello,
> 
> this links are not working:
> 
> http://wiki.openoffice.org/wiki/Documentation/BASIC_Guide
> http://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide

the wiki has a technical problem at the moment, should be back soon
hopefully

Juergen

> 
> Cheers,
> Jens
> 
> _
> 
> mediaengineer - Ingenieurbüro für CAD und technische Planungen
> 
> Dipl. Ing. (FH) Jens Mueller
> 
> Grafenwerthstraße 18
> 50937 Köln
> 
> mobil: +49 (0) 172 30 68 072
> büro: +49 (0) 221 299 88 80
> fax: +49 (0) 221 299 88 79
> 
> j...@autostage.de
> 
> www.autostage.de
> www.mediaengineer.de
> 
> !! Bitte drucken Sie diese Email nur, wenn Sie unbedingt müssen. Der Umwelt 
> zuliebe !!
> !! please don't print this e-mail unless you really need to !!
> 
> 

Possible broken link: other

[j...@autostage.de]

Hello,

this links are not working:

http://wiki.openoffice.org/wiki/Documentation/BASIC_Guide
http://wiki.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide

Cheers,
Jens

_

mediaengineer - Ingenieurbüro für CAD und technische Planungen

Dipl. Ing. (FH) Jens Mueller

Grafenwerthstraße 18
50937 Köln

mobil: +49 (0) 172 30 68 072
büro: +49 (0) 221 299 88 80
fax: +49 (0) 221 299 88 79

j...@autostage.de

www.autostage.de
www.mediaengineer.de

!! Bitte drucken Sie diese Email nur, wenn Sie unbedingt müssen. Der Umwelt 
zuliebe !!
!! please don't print this e-mail unless you really need to !!

Re: Introducing myself

[Andrea Pescetti]

On 10/01/2013 Rob Weir wrote:
> On Thu, Jan 10, 2013 at 7:23 AM, Fabrizio Marchesano wrote:
>> I'm ready to give my contribution to the community in any way I can,
and if
>> you're planning to attend FOSDEM 2013 I'll be glad to meet you in
person ...
> I personally will not be able to make it to Fosdem, but we will have
> many project members there, and we will have a table and a dev room.
> So be sure to stop by the dev room and introduce yourself!

Fabrizio is actually one of the FOSDEM accepted speakers for the Apache
OpenOffice devroom, so it will be easy to meet him! Extensions developers
(hence, putting the api list in CC) shouldn't miss the early afternoon
session, with a talk by Fabrizio and another one by Juergen.

Schedule: https://fosdem.org/2013/schedule/track/apache_openoffice/

FOSDEM 2013 is in Brussels, Belgium, 2 February.

Regards,
  Andrea.

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Rob Weir]

On Fri, Jan 11, 2013 at 9:06 AM, Jürgen Schmidt  wrote:
> On 1/10/13 3:56 PM, Oliver-Rainer Wittmann wrote:
>> Hi,
>>
>> On 10.01.2013 11:55, Rony G. Flatscher wrote:
>>> Hi Oliver-Rainer,
>>>
>>> On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:
 I have finished the renaming from "OpenOffice.org" to "Apache
 OpenOffice" - see issue 121388.

 Beside corresponding changes in the user interface this change has
 impact on the following
 important and critical stuff:
 - folder/directory names
 - package names
 - Windows registry key names and values
 - ...

 As the folder/directory path to the user profile is also changed, the
 user profile of a former
 installed AOO (or OOo) version is not taken over.
>>> for installation script purposes of add-ons etc., where can one find
>>> the concrete strings for
>>> folder/directory names on the various operating system platforms and
>>> the Windows registry key names
>>> and values?
>>>
>>
>> Unfortunately, there is no single place in the source code. I also had
>> not the resources to clean this up during the renaming work - hint,
>> hint, hint :-)
>>
>> Please have a look at issue 121388, the wiki page referenced in one of
>> the issue's comments and the intrinsic changes I have made.
>>
>> The product installation folder is more or less a form of the
>> $PRODUCTNAME + [major version number]. E.g.:
>> - Windows: "Apache OpenOffice 3"
>> - Linux: "apache_openoffice3"
>> On Linux platforms we have also the basis installation folder. It name
>> is found in /main/instsetoo_native/util/openoffice.lst
>>
>> The user profile folder is more or less $PRODUCTNAME/[major version
>> number]/
>>
>> The Windows registry keys and values can be found in module main/scp2/
>>
>> I hope that helps a little bit.
>
> I was thinking about the name and here I mean the name that is used for
> the folder etc. The name is used in the help, in tools option, in the
> menu...
>
> We changed "OpenOffice.org" to "Apache OpenOffice" so good so far. But
> would it be nicer to shorten the folder, menu entries, ... to simply
> OpenOffice
>
> Folders
> Linux: /opt/openoffice4
> Mac: OpenOffice.app
> Windows: OpenOffice 4
>

or even OpenOffice4, avoiding a space in the directory name, a source
of much pain in Windows.

-Rob

> Tools Option
> OpenOffice
> OpenOffice Writer
> OpenOffice ...
>
> Help
> OpenOffice instead of hundreds of "Apache OpenOffice"
>
> The idea is that the project and product is called Apache OpenOffice but
> in practice we would use in the product the short from OpenOffice. The
> intro, start center, about can of course use images where we use "Apache
> OpenOffice".
>
> Well it's just an idea and I know it would require some further work but
> now would be the time for it. I believe legally should it be ok today
> but it have to checked to be safe.
>
> What's your opinion?
>
> Juergen
>
>
>
>
>

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Jürgen Schmidt]

On 1/10/13 3:56 PM, Oliver-Rainer Wittmann wrote:
> Hi,
> 
> On 10.01.2013 11:55, Rony G. Flatscher wrote:
>> Hi Oliver-Rainer,
>>
>> On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:
>>> I have finished the renaming from "OpenOffice.org" to "Apache
>>> OpenOffice" - see issue 121388.
>>>
>>> Beside corresponding changes in the user interface this change has
>>> impact on the following
>>> important and critical stuff:
>>> - folder/directory names
>>> - package names
>>> - Windows registry key names and values
>>> - ...
>>>
>>> As the folder/directory path to the user profile is also changed, the
>>> user profile of a former
>>> installed AOO (or OOo) version is not taken over.
>> for installation script purposes of add-ons etc., where can one find
>> the concrete strings for
>> folder/directory names on the various operating system platforms and
>> the Windows registry key names
>> and values?
>>
> 
> Unfortunately, there is no single place in the source code. I also had
> not the resources to clean this up during the renaming work - hint,
> hint, hint :-)
> 
> Please have a look at issue 121388, the wiki page referenced in one of
> the issue's comments and the intrinsic changes I have made.
> 
> The product installation folder is more or less a form of the
> $PRODUCTNAME + [major version number]. E.g.:
> - Windows: "Apache OpenOffice 3"
> - Linux: "apache_openoffice3"
> On Linux platforms we have also the basis installation folder. It name
> is found in /main/instsetoo_native/util/openoffice.lst
> 
> The user profile folder is more or less $PRODUCTNAME/[major version
> number]/
> 
> The Windows registry keys and values can be found in module main/scp2/
> 
> I hope that helps a little bit.

I was thinking about the name and here I mean the name that is used for
the folder etc. The name is used in the help, in tools option, in the
menu...

We changed "OpenOffice.org" to "Apache OpenOffice" so good so far. But
would it be nicer to shorten the folder, menu entries, ... to simply
OpenOffice

Folders
Linux: /opt/openoffice4
Mac: OpenOffice.app
Windows: OpenOffice 4

Tools Option
OpenOffice
OpenOffice Writer
OpenOffice ...

Help
OpenOffice instead of hundreds of "Apache OpenOffice"

The idea is that the project and product is called Apache OpenOffice but
in practice we would use in the product the short from OpenOffice. The
intro, start center, about can of course use images where we use "Apache
OpenOffice".

Well it's just an idea and I know it would require some further work but
now would be the time for it. I believe legally should it be ok today
but it have to checked to be safe.

What's your opinion?

Juergen

[INFO]: I moved the SNAPSHOT tag to revision 1431825

[Jürgen Schmidt]

Hi,

I moved the SNAPSHOT tag to revision 1431825. Means the next snapshot
from the build bots include the renaming changes from Oliver.

Oliver is planning to change the version 3.5 to 4.0 next week and with
this changes we should create a new developer snapshot build.

Based on this I think some further and more intensive testing is
probably a good idea to find and report problems regarding the renaming
early.

Juergen

Re: Symphony code in AOO 4.0

[Herbert Duerr]

On 11.01.2013 13:59, Rob Weir wrote:

On Fri, Jan 11, 2013 at 4:38 AM, Jürgen Schmidt  wrote:

[...]
In general we can improve our communication to the public. We can more
often talk about what we are doing, or can collect on a regular base the
fixes we have made. Herbert prepared a nice script that we can use. New
and bigger things can we highlight separately as we partly did already.
We can simply do more in this area.



I must have missed this.  What is Herbert's script?   We might be able
to use it for the documentation team as well, since we're thinking of
authoring the doc on the wiki first.


Please have a look at its sample output for developers [1] or users [2], 
the thread "Script to get infos about development snapshot differences" 
[3], or the script itself [4].


[1] http://people.apache.org/~hdu/izlist1.htm
[2] http://people.apache.org/~hdu/izlist9.htm
[3] at http://markmail.org/thread/dtlfvv2ztfvtw47v)
[4] 
http://svn.apache.org/repos/asf/openoffice/devtools/scripts/svnlog2info.py


Herbert

Re: [IMPORTANT, DISCUSS]: no migration/use of former user profile with AOO 4.0

[Oliver-Rainer Wittmann]

Hi,

On 10.01.2013 13:10, O.Felka wrote:

Am 10.01.2013 12:05, schrieb Oliver-Rainer Wittmann:

Hi,

 From my point it is important to point out (and also discuss) that the
installation of a AOO 4.0 - our planned next major release - will not
migrate/use a user profile from a former installed AOO (or OOo) version.
This has been also mentioned in our blog "Your top questions answered",
answer to question 10 [1].

It is a consequence of the new version number - "4.0" - as the major
version number - "4" - is part of the folder/directory path to the user
profile.
But, it is already a consequence of the completed renaming from
"OpenOffice.org" to "Apache OpenOffice" as the productname (in a certain
form) is also part of the folder/directory path to the user profile -
see issue 121388.

We have a lot of trouble with the migration/usage of user profiles of
former installed OOo 3.x versions - unfortunately I could never
reproduce these problems and thus I could not work on a fix. Thus, not
migrate/use a user profile from former installed AOO (or OOo) versions
would solve these problems.

Let the discussion begin :-)


Ok!

I think it is a bad user experience to do nothing.

We have had a migration wizard for user settings (was it OOo 1.x to 2.x or 2.x
to 3.x?). This wizard offers to migrate user settings to the new version.
It's a better experience and gives the chance to migrate these settings which
are supported or convert the configuration files to the supported format of the
new office version.



I have found the corresponding code. I am currently having a deeper look.

Does anybody already have deeper knowledge in this area?
If yes, please share it.

Does somebody know, if the migration of installed extensions from OOo 2.x to OOo 
3.x ever worked?


Thanks in advance,
Oliver.

Re: Adapt the naming of our project deliverables - "OpenOffice.org" --> "Apache OpenOffice"

[Oliver-Rainer Wittmann]

Hi,

On 10.01.2013 17:08, Rony G. Flatscher (Apache) wrote:


On 10.01.2013 15:56, Oliver-Rainer Wittmann wrote:

Hi,

On 10.01.2013 11:55, Rony G. Flatscher wrote:

Hi Oliver-Rainer,

On 10.01.2013 11:23, Oliver-Rainer Wittmann wrote:

I have finished the renaming from "OpenOffice.org" to "Apache OpenOffice" - see 
issue 121388.

Beside corresponding changes in the user interface this change has impact on 
the following
important and critical stuff:
- folder/directory names
- package names
- Windows registry key names and values
- ...

As the folder/directory path to the user profile is also changed, the user 
profile of a former
installed AOO (or OOo) version is not taken over.

for installation script purposes of add-ons etc., where can one find the 
concrete strings for
folder/directory names on the various operating system platforms and the 
Windows registry key names
and values?



Unfortunately, there is no single place in the source code. I also had not the 
resources to clean
this up during the renaming work - hint, hint, hint :-)

Please have a look at issue 121388, the wiki page referenced in one of the 
issue's comments and
the intrinsic changes I have made.

The product installation folder is more or less a form of the $PRODUCTNAME + 
[major version
number]. E.g.:
- Windows: "Apache OpenOffice 3"
- Linux: "apache_openoffice3"
On Linux platforms we have also the basis installation folder. It name is found 
in
/main/instsetoo_native/util/openoffice.lst

The user profile folder is more or less $PRODUCTNAME/[major version number]/

The Windows registry keys and values can be found in module main/scp2/

I hope that helps a little bit.

Thank you very much Oliver, that definitely helps already!

Though because of your hints to modules, what would be the best tool to locate 
them in your version
of AOO via the Internet to learn about the concrete strings for the Linux basis 
installation folder,
the profile folder, and especially the Windows registry keys and values?



I am not sure, if I got you right.
I assume that you want to know the "best tool" to locate the corresponding 
folders of an actual installation of AOO.
I have no tool at hand - I am just looking "manually" in folders which typically 
contain "application installations" and "application settings" on the different 
platforms.


Best regards, Oliver.

Re: Symphony code in AOO 4.0

[Rob Weir]

On Fri, Jan 11, 2013 at 4:38 AM, Jürgen Schmidt  wrote:
> On 1/11/13 10:20 AM, Shenfeng Liu wrote:
>> 2013/1/11 Rob Weir 
>>
>>> On Thu, Jan 10, 2013 at 8:03 PM, Andrea Pescetti 
>>> wrote:
 Rob Weir wrote:
>
> I'm reading FUD, from the usual misinformed suspects ... I
>
> can certainly sympathize with leaders of communities that can only be
> held together by irrational fears.  It is not easy to maintain that
> peak level of paranoia.


 Your personal opinions on the people involved (I admit I have very little
 context, I only had the time to read the discussion here but nothing
>>> else so
 far) are best kept separated from the important fact, that is that
 apparently incorrect information is being circulated about the benefits
>>> that
 the Symphony donation is bringing to OpenOffice and to the
>>> free/open-source
 software world in general.


> Anyone who cares to look can
> see that we've actually integrated quite a but of Symphony code into
> the AOO trunk already.   For example, the following 167 bug fixes


 People don't care to look, unfortunately... But I definitely agree that
>>> this
 listing is impressive, as it is this page:

>>> http://wiki.openoffice.org/wiki/Documentation/Fidelity_Improvement_Since_AOO341

 If you manage to co-author a blog post with Shenfeng Liu (or someone else
 from the former Symphony team) about the integrated fixes/features, this
 will be an important service to the OpenOffice users. But please, let's
>>> do
 it because it's important in itself and because it's clearly overdue
>>> (aside
 from a brief mention in the "top 10 questions" posts), not because
>>> someone
 feels the need to address some particular wrong or misleading claim.

>>>
>>> Clarifying the facts where misinformation is being spread is part of
>>> the necessary communications that any project needs to engage in.  We
>>> saw that as a podling, when the ASF itself addressed misinformation
>>> regarding this project.  Now this is our responsibility.
>>>
>>> Of course, misinformation about insubstantial matters is best ignored.
>>>  But where misinformation is propagated about substantial project
>>> operations, then that is sufficient motivation for the contents and
>>> timing of a post to correct such misinformation.
>>>
>>> In any case, pointing out the lie on this list already gives 90% of
>>> the benefit, since such FUD cannot survive the light of day.  A blog
>>> post is unnecessary.
>>>
>>
>> IMHO, we can consider a blog post about our progress on the 4.0 release,
>> including the contents we are working on, e.g. fidelity,
>> performance&reliability, accessibility, usability, enhanced platform
>> support... Symphony's contribution is part of this story.
>> If we decided to post it, I'd like to be the co-author.
>> Thanks!
>>
>
> In general we can improve our communication to the public. We can more
> often talk about what we are doing, or can collect on a regular base the
> fixes we have made. Herbert prepared a nice script that we can use. New
> and bigger things can we highlight separately as we partly did already.
> We can simply do more in this area.
>

I must have missed this.  What is Herbert's script?   We might be able
to use it for the documentation team as well, since we're thinking of
authoring the doc on the wiki first.

-Rob

> The key point here is that people take responsibility, for example using
> Herbert's script and convert the output in the wiki to document it. We
> can play with different styles how to present such info best and where.
>
> Juergen
>
>
>
>
>
>
>

Re:Re: build sw

[2]

Hi,
 Yes, I have finished the full build without debug, now I want to build the 
module sw with debug,  because I would like to change the code of sw ,and debug 
the module. I have finished partial build with debug about sc and sd, and debug 
success in VC++2008, but sw couldn't be built completely.
  I fellow the step which you told me, but it didn't success, the message 
as follows:
==
/cygdrive/d/aoo/main/sw
$ make -sr debug=true
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/bin/swen-US.res' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/lib/imsword.lib' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/lib/isw.lib' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/xml/component/sw/util/sw.component' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/xml/component/sw/util/msword.component' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/lib/iswd.lib' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/xml/component/sw/util/swd.component' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/lib/iswui.lib' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/lib/ivbaswobj.lib' 有一个精细的时间标志
make: *** 警告: .LOW_RESOLUTION_TIME 文件 `/cygdrive/d/aoo/main/solver/341/wntms

ci12.pro/xml/component/sw/util/vbaswobj.component' 有一个精细的时间标志
[ build ALL ] top level modules: sw
[ build ALL ] loaded modules: sw
[ build CHK ] loaded modules: sw
===
Thank you

Yi

At 2013-01-11 14:58:13,"Fan Zheng"  wrote:
>Well, I guess you misunderstand something.
>
>you said that you executed "build --from SW", means you want to just build
>the module SW right?
>
>The there may exist 2 issues:
>1. Before the partial build could be executed as you wished, the full build
>has to be finished at least once. Otherwise the dependent libraries and
>include files wont be the places they should be; For executing the full
>build, just execute "dmake -P4" in your step 3 (in the path where you
>execute step 2);
>2.  Such "build from" parameter is used for executing a partial/full build
>from the module you indicated and all the modules depend on said
>module. Commonly such execution way is only available in the installation
>package module named "instsetoo_native"; Inside the SW module package,
>execute the following one instead:
>"make -sr debug=true -j4";
>
>Hope this could solve your problems.
>
>
>
>
>
>2013/1/11 2 
>
>> Hi,
>>I couldn't complete sw building in partial build, when I input the
>> commands ,I got the messages as follow:
>> ===
>>  build -- version: 275224
>> This module has been migrated to GNU make.
>> You can only use build --all/--since here with build.pl.
>> To do the equivalent of 'build && deliver' call:
>> make -sr
>> in the module root (This will modify the solver).
>> =
>>
>>I don't how to deal with this problems.
>> there are the commands I input in cygwin:
>> 1.cd main
>> 2.source winenv.Set.sh
>> 3.cd sw
>> 4.build --from sw --prepare
>> 5.build debug=true --from sw

Re: Introduction and Question

[Ariel Constenla-Haile]

Hi Jonathan,

On Thu, Jan 10, 2013 at 10:22:24PM -0800, Jonathan Simona wrote:
> Thanks so much for the replies! Unfortunately I do not know how to build
> and run AOO and can't seem to find out because the wiki link seems to be
> down.I'm not sure if this problem is only occuring for me, but I will
> attempt to build when wiki comes back up.
> 
> Wiki's error message:
> A database error has occurred. Did you forget to run maintenance/update.php
> after upgrading? See:
> https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script
> Query: SELECT page_id,page_len,page_is_redirect,page_latest FROM `page`
> WHERE page_namespace = '10' AND page_title = 'Extension_DPL' LIMIT 1
> Function: LinkCache::addLinkObj
> Error: 1286 Unknown table engine 'InnoDB' (localhost)

Yes, the wiki seems to be dead. While it gets fixed, you can checkout
the source code.

Are you working on Windows, Linux, MacOS? Depending on the system, you
may have all the tools at hand to checkout source.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpiGi3FiMjD_.pgp
Description: PGP signature

Re: Symphony code in AOO 4.0

[Fernando Cassia]

On Thu, Jan 10, 2013 at 2:06 PM, Rob Weir  wrote:
> I'm reading FUD, from the usual misinformed suspects, saying that the
> "IBM donation to AOO is pure marketing fluff" and "IBM faked the
> donation of the Symphony code" and "IBM did not donate anything".   I
> can certainly sympathize with leaders of communities that can only be
> held together by irrational fears.  It is not easy to maintain that
> peak level of paranoia.

could that be someone who worked at Burson Marsteller ? am I thinking
about the same Public Relations specialist?

A PR guy being a master of spin? surely some mistake (sarcasm)

http://pages.citebite.com/k9g2s1t6neji

"history has shown that the proprietary StarOffice and Oracle Open
Office have never been able to generate any visible turnover (and have
not attracted a single company)" (...) "None of these companies – some
of them very large, up to 100.000 seats – ever asked for a license of
Sun StarOffice."

https://blogs.oracle.com/ontherecord/entry/staroffice_8_and_sixth_annual
"The Sixth Annual eWEEK Excellence Award winners posted yesterday.
This year almost 800 entries were submitted for the award, from which
19 winners in different categories were chosen. StarOffice 8 is the
Productivity Applications category winner."

http://philwilson.org/blog/2006/07/bristol-adopts-odf
"Bristol City Council has joined the ODF Alliance, The Council already
uses StarOffice instead of Microsoft Office "

"Largest implementation of Sun's StarOffice office productivity suite
in the UK retail sector"
http://www.prnewswire.co.uk/news-releases/jessops-develops-new-point-of-sale-and-desktop-infrastructure-to-achieve-2m-pounds-sterling-cost-saving-154678395.html

"By centralising our POS management and moving to StarOffice, we will
not only save money, we will have a centralised view of each and every
Jessops store across the UK. "

India insurance firm moves 10,000 seats to StarOffice
http://www.smh.com.au/articles/2004/02/06/1075854037075.html

" Banca Popolare di Milano

4,500 SUSE Linux desktops with a Mozilla web browser, web client for
Lotus Notes, * Sun’s StarOffice suite*, and a Java-based custom suite
of banking applications in its 500 branch offices."

HDFC Bank uses StarOffice
http://computer.financialexpress.com/20050228/market01.shtml

So how does this compare to claims that "None of these companies ever
asked for a license of Sun StarOffice." ?? and "not a single company"

Wonder how anyone still takes him seriously...
FC
-- 
During times of Universal Deceit, telling the truth becomes a revolutionary act
- George Orwell

Re: ipad

[FR web forum]

>Is this available for ipad?  I have it on a lap top.  It is great.
You have many, many answers directly on the community forum:
http://forum.openoffice.org/en/forum/viewtopic.php?f=17&t=33096

Re: "dist" move...

[Jürgen Schmidt]

On 12/6/12 10:18 PM, Dave Fisher wrote:
> 
> On Dec 6, 2012, at 11:36 AM, Andrew Rist wrote:
> 
>>
>> On 12/6/2012 9:40 AM, Kay Schenk wrote:
>>> On Thu, Dec 6, 2012 at 12:17 AM, Herbert Duerr  wrote:
 On 06.12.2012 00:03, Kay Schenk wrote:
> I put in a request, as part of our graduation process, to have our
> "dist" area moved to a top level.
>
> INFRA-5607
>
> https://issues.apache.org/jira/browse/INFRA-5607

 The issue is requesting a move to http://www.apache.org/dist/ooo, but
 shouldn't this better be named */openoffice (or */aoo)?

 Herbert
>>> Herbert -- see comments by Henk on the ticket. It does appear that
>>> /dist/openoffice will be the new top-level name for our *next* release
>>> -- nothing will be moved now. Perhaps this was already communicated to
>>> infra and I was not aware of it.
>>>
>>> Also, of more immediate concern is the archiving of the 3.4.0 source
>>> release and possibly the 3.3. patch.
>>>
>> All of this is driven by the nature of /dist/, how it is mirrored outside 
>> Apache, and the pretty substantial resources taken up by our release.
>> There are consequences to moving something once it is there - some mirrors 
>> might end up with both areas mirrored, for example.
>> The best way to resolve that (in the opinion of infra - AIUI) is to move the 
>> location on our next release, this allows for planing of resources and the 
>> notification of the mirror network.   It seems a reasonable approach to me.
> 
> This is the direction the comments are going in Kay's issue.
> 
> Since the 3.4.1 Language packs are supplements to the 3.4.1 source release 
> and will have incubator branding they will go into the incubator/ooo/ 
> location.
> 
> Some might think that we should be doing a full 3.4.2 with non-incubator 
> branding, but no real need IMO.
> 

What does it mean for our upcoming respin of AOO 3.4.1? Taking the
discussion into account I plan to do the following.

1. copy the new src release ("") to
www.apache.org/dist/incubator/ooo/3.4.1/source besides the former 3.4.1
src release. Please notice that the name includes now a revision number.

2. copy the the new binaries besides the existing ones under
www.apache.org/dist/incubator/ooo/files/stable/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/ast/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/da/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/eu/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/gd/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/pl/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/ko/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/nb/3.4.1
www.apache.org/dist/incubator/ooo/files/localized/sv/3.4.1


With the next release AOO 4.0 we will have a new name without
"incubating" and I plan to reorganize the directory structure to
simplify it. I know we had a discussion about it in the past and I will
continue there or will start a new thread on this topic separately. I
would like to plan this asap to be prepared and to have enough time to
adapt the download scripts etc.

Juergen

Re: level 2 accomplished

[Dave Barton]

 Original Message  
From: Anders Kvibäck 
To: dev@openoffice.apache.org
Date: Fri, 11 Jan 2013 10:48:40 +0100

> Hi!
> I'm done  with level 2. And I'm starting off with level 3 now.
> 
> Regards, Anders Kvibäck
> 

That's great Anders, but your messages are coming through moderation, so
one of the first things you should do is subscribe to this list.
See:
https://openoffice.apache.org/mailing-lists.html#development-mailing-list-public

Regards
Dave

Re: [RELEASE]: AOO 3.4.1 respin

[Jürgen Schmidt]

On 1/10/13 10:29 PM, Marcus (OOo) wrote:
> Am 01/10/2013 07:07 PM, schrieb Kay Schenk:
>> On Thu, Jan 10, 2013 at 8:43 AM, Jürgen
>> Schmidtwrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA512
>>>
>>> On 1/10/13 1:38 PM, Ariel Constenla-Haile wrote:
 On Wed, Jan 09, 2013 at 10:56:46AM +0100, Jürgen Schmidt wrote:
> I will start the build of the first official AOO 3.4.1 respin
> snapshot today based on revision 1424891 on the AOO34 branch.
>
> The new supported languages are "ast", "da", "eu", "gd", "pl",
> "ko", "nb", "sv".
>
> I will built a new updated source release, including the
> translation updates. The only further change is in the scripts
> for building the source release where I include the revision
> number.
>
> @Ariel: can you please start the build for Linux as well?

 Linux packages are available at
 http://people.apache.org/~arielch/packages/respin_aoo341

>>>
>>> The first snapshot build is now available and you can find the bits
>>> under
>>>
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOO3.4.1.respin
>>>
>>>
>>> Please let me know if there is problem with the links.
>>>
>>> If possilbe I would like to move the release date to Jan 24th. I will
>>> be on a business trip for the rest of Jan. starting on 26th and have
>>> not really time to handle it at this time.
>>>
>>> Juergen
>>>
>>
>> Ok, so this is a week earlier than we originally anticipated.
>>
>> thanks for the heads-up.
> 
> Juergen, any idea of the time you want to execute the release?
> 
> At least for me more important than the day itself. ;-)

we can propably prepare everything in front of it or not. Adding further
languages shouldn't be too difficult if the files are located in the
same place and using the same naming convention.

But anyway which time would work best for you?

Juergen


> 
> Thanks
> 
> Marcus

level 2 accomplished

[Anders Kvibäck]

Hi!
I'm done  with level 2. And I'm starting off with level 3 now.

Regards, Anders Kvibäck

Re: Symphony code in AOO 4.0

[Jürgen Schmidt]

On 1/11/13 10:20 AM, Shenfeng Liu wrote:
> 2013/1/11 Rob Weir 
> 
>> On Thu, Jan 10, 2013 at 8:03 PM, Andrea Pescetti 
>> wrote:
>>> Rob Weir wrote:

 I'm reading FUD, from the usual misinformed suspects ... I

 can certainly sympathize with leaders of communities that can only be
 held together by irrational fears.  It is not easy to maintain that
 peak level of paranoia.
>>>
>>>
>>> Your personal opinions on the people involved (I admit I have very little
>>> context, I only had the time to read the discussion here but nothing
>> else so
>>> far) are best kept separated from the important fact, that is that
>>> apparently incorrect information is being circulated about the benefits
>> that
>>> the Symphony donation is bringing to OpenOffice and to the
>> free/open-source
>>> software world in general.
>>>
>>>
 Anyone who cares to look can
 see that we've actually integrated quite a but of Symphony code into
 the AOO trunk already.   For example, the following 167 bug fixes
>>>
>>>
>>> People don't care to look, unfortunately... But I definitely agree that
>> this
>>> listing is impressive, as it is this page:
>>>
>> http://wiki.openoffice.org/wiki/Documentation/Fidelity_Improvement_Since_AOO341
>>>
>>> If you manage to co-author a blog post with Shenfeng Liu (or someone else
>>> from the former Symphony team) about the integrated fixes/features, this
>>> will be an important service to the OpenOffice users. But please, let's
>> do
>>> it because it's important in itself and because it's clearly overdue
>> (aside
>>> from a brief mention in the "top 10 questions" posts), not because
>> someone
>>> feels the need to address some particular wrong or misleading claim.
>>>
>>
>> Clarifying the facts where misinformation is being spread is part of
>> the necessary communications that any project needs to engage in.  We
>> saw that as a podling, when the ASF itself addressed misinformation
>> regarding this project.  Now this is our responsibility.
>>
>> Of course, misinformation about insubstantial matters is best ignored.
>>  But where misinformation is propagated about substantial project
>> operations, then that is sufficient motivation for the contents and
>> timing of a post to correct such misinformation.
>>
>> In any case, pointing out the lie on this list already gives 90% of
>> the benefit, since such FUD cannot survive the light of day.  A blog
>> post is unnecessary.
>>
> 
> IMHO, we can consider a blog post about our progress on the 4.0 release,
> including the contents we are working on, e.g. fidelity,
> performance&reliability, accessibility, usability, enhanced platform
> support... Symphony's contribution is part of this story.
> If we decided to post it, I'd like to be the co-author.
> Thanks!
> 

In general we can improve our communication to the public. We can more
often talk about what we are doing, or can collect on a regular base the
fixes we have made. Herbert prepared a nice script that we can use. New
and bigger things can we highlight separately as we partly did already.
We can simply do more in this area.

The key point here is that people take responsibility, for example using
Herbert's script and convert the output in the wiki to document it. We
can play with different styles how to present such info best and where.

Juergen

Re: Symphony code in AOO 4.0

[Shenfeng Liu]

2013/1/11 Rob Weir 

> On Thu, Jan 10, 2013 at 8:03 PM, Andrea Pescetti 
> wrote:
> > Rob Weir wrote:
> >>
> >> I'm reading FUD, from the usual misinformed suspects ... I
> >>
> >> can certainly sympathize with leaders of communities that can only be
> >> held together by irrational fears.  It is not easy to maintain that
> >> peak level of paranoia.
> >
> >
> > Your personal opinions on the people involved (I admit I have very little
> > context, I only had the time to read the discussion here but nothing
> else so
> > far) are best kept separated from the important fact, that is that
> > apparently incorrect information is being circulated about the benefits
> that
> > the Symphony donation is bringing to OpenOffice and to the
> free/open-source
> > software world in general.
> >
> >
> >> Anyone who cares to look can
> >> see that we've actually integrated quite a but of Symphony code into
> >> the AOO trunk already.   For example, the following 167 bug fixes
> >
> >
> > People don't care to look, unfortunately... But I definitely agree that
> this
> > listing is impressive, as it is this page:
> >
> http://wiki.openoffice.org/wiki/Documentation/Fidelity_Improvement_Since_AOO341
> >
> > If you manage to co-author a blog post with Shenfeng Liu (or someone else
> > from the former Symphony team) about the integrated fixes/features, this
> > will be an important service to the OpenOffice users. But please, let's
> do
> > it because it's important in itself and because it's clearly overdue
> (aside
> > from a brief mention in the "top 10 questions" posts), not because
> someone
> > feels the need to address some particular wrong or misleading claim.
> >
>
> Clarifying the facts where misinformation is being spread is part of
> the necessary communications that any project needs to engage in.  We
> saw that as a podling, when the ASF itself addressed misinformation
> regarding this project.  Now this is our responsibility.
>
> Of course, misinformation about insubstantial matters is best ignored.
>  But where misinformation is propagated about substantial project
> operations, then that is sufficient motivation for the contents and
> timing of a post to correct such misinformation.
>
> In any case, pointing out the lie on this list already gives 90% of
> the benefit, since such FUD cannot survive the light of day.  A blog
> post is unnecessary.
>

IMHO, we can consider a blog post about our progress on the 4.0 release,
including the contents we are working on, e.g. fidelity,
performance&reliability, accessibility, usability, enhanced platform
support... Symphony's contribution is part of this story.
If we decided to post it, I'd like to be the co-author.
Thanks!

- Shenfeng (Simon)





>
> -Rob
>
> > Regards,
> >   Andrea.
>