Re: to get bug repositories

[Andrea Pescetti]

On 02/10/2014 dhyanendra singh wrote:

I am Dhyanandra Singh. I am pursuing M. Tech.  from Jaypee Institute
of Information Technology. As my thesis Work I have chosen Automatic
Duplicate bug Detection and want to use bug repository of Apache open
office for that.
I am very thankful to you if you will share your bug repository with me.


This was answered on the QA list. Follow-up there.
Andrea

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Concerns about the AOO community

[Andrea Pescetti]

On 02/10/2014 Roman Sausarnes wrote:

And I'm here to help, not just complain :) I'm still working out how I can
contribute...


Well, start by improving the wiki then! I agree that the building guide 
can be restructured better, especially in the steps that lead you from 
the main page to the individual platforms.


I've just created an account for you on the wiki. You have been sent a 
temporary password. Feel free to edit pages as you wish to make them 
easier to follow for newcomers.


Regards,
  Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

AOO4 General videos

[Drew Jensen]

JUST A PREVIEW -

So from the other day I thought to just take the firrst page from the 'Why
AOO' web page as a script.

Doing that I can get one paragraph into an appx 30 seconds.

I have Five different , original, graphic combinations. I figured Five vids.

The web page gives Four paragraphs of text.

Any suggestions on a Fifth.

I plan to use the same opening graphic for each - Take a second look at AOO
4 - might be a good title for that, and I think also a good start to the
Fifth text copy.

I can finish what a I have, as Four vids, in a full day I think.

Will hold off on this till Saturday after work, to give a day for your
feedback here.

Thanks
//drew

AOO4 ONE: http://youtu.be/VWiZ7iOtUs0

AOO4 TWO: http://youtu.be/IIMmoEsAuis

Re: Concerns about the AOO community

[Donald Harbison]

On Thu, Oct 2, 2014 at 6:01 PM, Dave Barton  wrote:

> Chuck Davis wrote:
> > I've seen quite a number of new people show up here lately
> > indicating interest coming from someplace.  If one out of 10 of them
> > sticks and becomes a regular contributor the project is in a very
> > good position I think.
>
> Agreed.
>
> > My observations regarding LO: 1)  They've copied some features from
> > MS Office that make it equally difficult to useIt's not as
> > pleasant to use as AOO.
>
> Can you please give some specific examples of what you mean by "copied
> some features from MS Office"?
>
> I have been an OOo user since Sun (theoretically) open sourced the code
> and today I use/test both AOO and LO. Can you please enlighten me in
> what way LO is more difficult to use than AOO? I am obviously missing
> something, because I find them equally pleasant to use.
>
> > It's very unfortunate the distributions have adopted LO in lieu of
> > AOO.
>
> That's mainly because a number of the distros were already unhappy about
> the control Sun/Oracle held over the code. When TDF/LO was formed some
> of code from the (distro driven) Go-OO fork was merged into LO. This
> happened well before Oracle gave the OOo trademark and domain name to
> the ASF.
>
> > 2)  Their constant AOO bashing is a real turn-off for me and I hope
> > others as well.  I don't think I want their people in our camp.
>
> Sorry, but this is just FUD. Ignoring the Weir - Vignoli blog battle and
> other external sources, please give examples of "Their constant AOO
> bashing" on any the TDF/LO controlled sources (eg. website, mailing
> lists, etc.). For every instance you can sight, I can match two for one
> the near vitriol I have seen poured out on this list alone.
>
> In another part of this thread there is talk of "better cooperation"
> between the two projects. Comments such as "I don't think I want their
> people in our camp." only serve to further promote the silly negative
> "us & them" attitude. It is not a competition, because neither project
> is selling anything.
>
> Reality Check: Other than the occasional "defector" :)) (in both
> directions) you don't have to concern yourself about "their people"
> moving into "your camp". There is no possibility that TDF is going give
> up years of hard work and expense and hand LO over to the ASF, any more
> than there is of the ASF handing AOO over to TDF.
>
> > 3) They seem to be very proud of getting rid of Java and replacing
> > it with Python.  I've looked at Python a little and it seems to me
> > any language dependent on indentation rather than syntax is
> > justdumb!  There is nothing wrong with Java -- especially
> > now that OpenJDK is the reference implementation and is being worked
> > on by every major player except MS.
>
> The movement to "get rid of" Java has been around even before Sun sold
> out to Oracle. There are developers working on AOO code today who are on
> record promoting the removal or reduced reliance on Java.
>
> Python is also supported by AOO.
>
> > 4)  LO seems to have major QC issues.  The quality is definitely
> > several notches below where AOO rests in my experience.
>
> Is this just "fan-boy" talk, or can you sight anything to substantiate
> this (apparently ill-informed) claim. I closely follow the development
> of both projects and my experience is very different to yours.
>
> > These are just my observations as a long time OpenOffice user.  And
> > Apache has some very interesting related projects (i.e. ODF Toolkit)
> > that can propel ODF as a standard reporting framework as well as the
> > new project to read and write OOXML for document exchange.
>
> True. Hopefully it will not be too long before the fruits of these
> projects are incorporated into AOO.
>
> The TDF has been closely involved with external projects working on
> improvements to the ODF <-> OOXML document compatibility. I don't have
> the details to hand right now, but IIRC the code improvements are, or
> will be, made available under Apache License, Version 2.0
>

Not so sure this is practical, but a noble goal, nonetheless; i.e. spirit
of genuine open source cooperation.

>
> > My advice:  stay the course.  Emphasize quality and dependability
> > over glitz.  If developers are not attracted to AOO on those terms
> > they're not developers the project needs.  Those of us in business
> > just need a tool to get our work done and it doesn't need to be fancy
> > -- just dependable.  LO falls on it's face at this point.
>
> Please, please, please can we stop this childish nonsense.


+1, let's move on from unproductive bashing. Pls.


> There is no
> reason why we should care, one way or the other, if LO is worse or
> better than AOO. Our only interests should be:
>
> 1. Making AOO as good as we can possibly make it.
>
> 2. Where possible work cooperatively with TDF and others in the interest
> of promoting and improving ODF. We already do this on matters of security.
>

Indeed.


>
> It 

Re: Concerns about the AOO community

[Dave Barton]

Chuck Davis wrote:
> I've seen quite a number of new people show up here lately
> indicating interest coming from someplace.  If one out of 10 of them
> sticks and becomes a regular contributor the project is in a very
> good position I think.

Agreed.

> My observations regarding LO: 1)  They've copied some features from
> MS Office that make it equally difficult to useIt's not as
> pleasant to use as AOO.

Can you please give some specific examples of what you mean by "copied
some features from MS Office"?

I have been an OOo user since Sun (theoretically) open sourced the code
and today I use/test both AOO and LO. Can you please enlighten me in
what way LO is more difficult to use than AOO? I am obviously missing
something, because I find them equally pleasant to use.

> It's very unfortunate the distributions have adopted LO in lieu of
> AOO.

That's mainly because a number of the distros were already unhappy about
the control Sun/Oracle held over the code. When TDF/LO was formed some
of code from the (distro driven) Go-OO fork was merged into LO. This
happened well before Oracle gave the OOo trademark and domain name to
the ASF.

> 2)  Their constant AOO bashing is a real turn-off for me and I hope 
> others as well.  I don't think I want their people in our camp.

Sorry, but this is just FUD. Ignoring the Weir - Vignoli blog battle and
other external sources, please give examples of "Their constant AOO
bashing" on any the TDF/LO controlled sources (eg. website, mailing
lists, etc.). For every instance you can sight, I can match two for one
the near vitriol I have seen poured out on this list alone.

In another part of this thread there is talk of "better cooperation"
between the two projects. Comments such as "I don't think I want their
people in our camp." only serve to further promote the silly negative
"us & them" attitude. It is not a competition, because neither project
is selling anything.

Reality Check: Other than the occasional "defector" :)) (in both
directions) you don't have to concern yourself about "their people"
moving into "your camp". There is no possibility that TDF is going give
up years of hard work and expense and hand LO over to the ASF, any more
than there is of the ASF handing AOO over to TDF.

> 3) They seem to be very proud of getting rid of Java and replacing
> it with Python.  I've looked at Python a little and it seems to me
> any language dependent on indentation rather than syntax is 
> justdumb!  There is nothing wrong with Java -- especially
> now that OpenJDK is the reference implementation and is being worked
> on by every major player except MS.

The movement to "get rid of" Java has been around even before Sun sold
out to Oracle. There are developers working on AOO code today who are on
record promoting the removal or reduced reliance on Java.

Python is also supported by AOO.

> 4)  LO seems to have major QC issues.  The quality is definitely 
> several notches below where AOO rests in my experience.

Is this just "fan-boy" talk, or can you sight anything to substantiate
this (apparently ill-informed) claim. I closely follow the development
of both projects and my experience is very different to yours.

> These are just my observations as a long time OpenOffice user.  And 
> Apache has some very interesting related projects (i.e. ODF Toolkit) 
> that can propel ODF as a standard reporting framework as well as the 
> new project to read and write OOXML for document exchange.

True. Hopefully it will not be too long before the fruits of these
projects are incorporated into AOO.

The TDF has been closely involved with external projects working on
improvements to the ODF <-> OOXML document compatibility. I don't have
the details to hand right now, but IIRC the code improvements are, or
will be, made available under Apache License, Version 2.0

> My advice:  stay the course.  Emphasize quality and dependability
> over glitz.  If developers are not attracted to AOO on those terms
> they're not developers the project needs.  Those of us in business
> just need a tool to get our work done and it doesn't need to be fancy
> -- just dependable.  LO falls on it's face at this point.

Please, please, please can we stop this childish nonsense. There is no
reason why we should care, one way or the other, if LO is worse or
better than AOO. Our only interests should be:

1. Making AOO as good as we can possibly make it.

2. Where possible work cooperatively with TDF and others in the interest
of promoting and improving ODF. We already do this on matters of security.

It is highly unlikely that AOO is going to die or disappear in the
foreseeable future and the same holds true for LO. If, for whatever
reason. the existence of TDF/LO upsets anyone here, I suggest they get
over it and move on.

Dave





-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h

to get bug repositories

[dhyanendra singh]

Hello,
  I am Dhyanandra Singh. I am pursuing M. Tech.  from Jaypee Institute
of Information Technology. As my thesis Work I have chosen Automatic
Duplicate bug Detection and want to use bug repository of Apache open
office for that.
I am very thankful to you if you will share your bug repository with me.

Re: Concerns about the AOO community

[Kay Schenk]

On 10/02/2014 11:18 AM, Alexandro Colorado wrote:
> On 10/2/14, Roman Sausarnes  wrote:
>> I swear I am technically savvy, but I have not found an easy link to the
>> materials you reference.
>>
>> I start at the homepage - www.openoffice.org
>>
>> I click on "I want to participate in OpenOffice" link which takes me here:
>> http://openoffice.apache.org/get-involved.html
>>
>> I clink on the New Volunteer Orientation Modules
>>  link which takes me
>> here: http://openoffice.apache.org/orientation/index.html
>>
>> I click on the Introduction to Development
>>  link
>> which takes me here:
>> http://openoffice.apache.org/orientation/intro-development.html
>>
>> I click on the Building Guide
>>  link
>> which takes me here:
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>>
>> That page has no instructions for how to build on Mac OS X, but it does
>> have a link titled Step-by-Step Building Guide for Different Platforms
>> 
>> which
>> of course looks very promising.
>>
>> But when you click on that link, it takes you here:
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>>
>> And that page offers detailed instructions for Ubuntu and Windows, but has
>> no links whatsoever to any materials regarding Mac OS X.
>>
>> When I click on the link that you provided, I see the requirements for Mac
>> OS X and I see how to get started that is very helpful.
>>
>> But compare that to the LibreOffice materials. I google "LibreOffice on Mac
>> OS X" and I get the following link:
>> https://wiki.documentfoundation.org/Development/BuildingOnMac
>>
>> I go to that link and it has step by step instructions on what to do.
>>
>> I'm smart enough to be able to find what I am looking for, but I'm just
>> saying that as a total newcomer to both projects LibreOffice made it much
>> easier.
> 
> Perhaps the thinking was that mantaining 3 guides is more dificult
> than having just 1 guide with annotation for each platform.

I think this is an accurate statement.

Of course, based on the comments in this thread, we certainly could
shorten the path to finding information.

The nice thing about having the development information on the wiki is
having developers contribute, especially, to the platform specific areas.

> 
> However it only took me a few seconds figuring out where the OSX
> information was. But if you think that mantaining 3 guides is the way
> to go, you can make the comment at doc@openoffice
> 
> There are also some formating that could definetly help like having
> special alerts and notes for the wiki which you can find here:
> {{Documentation/Caution| some text }}
> {{Documentation/Notes| some text }}
> 
>>
>> On Thu, Oct 2, 2014 at 10:38 AM, Alexandro Colorado  wrote:
>>
>>> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes
>>> >>>
>>> wrote:
>>>
 Hello,

 As a newcomer to development who is looking for a way to get involved
 in
 one project or the other, I thought I would share my impressions.

 The LibreOffice website and development materials seem friendlier to
 newcomers. It is easier to navigate and find simple instructions for
 how
>>> to
 get the code, set up a development environment, or contribute in other
 ways. I use a Mac, and almost right away I found a detailed set of
 instructions that was (relatively) current for how to build LO for the
 first time on my machine.

 The AOO website is confusing and disorganized for people approaching it
>>> for
 the first time and some of the information is outdated. I still haven't
 found simple instructions for how to build on a Mac. I have found a set
>>> of
 instructions but they are confusing, appear to be outdated, and suggest
 that I need to install older Xcode, etc., without any suggestions or
 resources on how to do it, if it is really necessary, etc.

>>>
>>> ​Can you please be more explicit on this. From our angle, we create
>>> modules
>>> so that people could easily find the right information of the way they
>>> want
>>> to contribute. Going to www.openoffice.org and selecting you want to
>>> contribute will lead you to a series of tutorials on how to better get
>>> involved. Development starts with building for different platforms,
>>> including OSX.
>>>
>>> All in all is 4 clicks:
>>> Homepage -> Contributing page -> Development -> Building -> OSX (
>>>
>>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
>>> )
>>>
>>> The instructions are for 4.1 so they are pretty current. ​
>>>
>>>
>>>

 I haven't given up on AOO, and part of me wants to figure out how to do
>>> it
 and then write the instructions clearly for 

Re: release manager for the next release

[Marcus]

Am 10/02/2014 03:04 PM, schrieb Jürgen Schmidt:

On 02/10/14 14:33, Rob Weir wrote:

On Thu, Oct 2, 2014 at 7:05 AM, Jürgen Schmidt  wrote:

Hi,

after a longer vacation and some silence in the past weeks I would like
to discuss the release manager role.

I think it's time that somebody else takes over this role and drives
active the next release. I did it since the beginning of OpenOffice at
Apache but I think it is a good opportunity for somebody to be more
active in the community and take over some responsibility.



Hi Juergen,

Thanks, from all I assume, for your efforts in this area.  Not only
were you the Release Manager, but you defined the role itself for AOO,
a project with more complicated release requirements than most others
at Apache.

If someone was considering stepping in as the Release Manager for the
next release, what should they be looking at?  Is there a wiki page or
other documentation that defines the process?


not yet but we should collect the different pieces in one place to make
it easier and to have a reference or some kind of check list ...


please write also a list about requirements for the release manager 
(e.g., has to do the dev/beta/release builds). When this is known it's 
easier to say for everybody yes or no to the role.


Thanks

Marcus




Also, are you able to review and update (if needed) the available
documentation and/or help mentor the next Release Manager?Or do
you think this is all documented enough that someone can just step in
and RTFM?


sure I will be available for any questions and will support the release
manager.

Juergen





Regards,

-Rob



We have released some important milestones over the years and have
enough experience and know what's necessary. Whoever takes over the
release manager role won't be alone and will get the support from the
community. In the same way I got it in the past.

We had discussions about the way how to communicate and track the
release planning and the progress and now it's the time that people can
realize this. It's always room for improvements.

The goal is that this somewhat important role is circulating and not
depending on one person only. The releases are anyway a community effort
and the release manager have to take care of some necessary formalism.

And to make it easier a further goal is to be able to take binary builds
from our build bots and release them. Currently we rely on builds made
by community members but I think it's better to use official build bots
for that. This means that we have to check the Windows build bot and the
binaries if they can be used already or what is missing. It means that
we need Linux build bots with the correct baseline or increase the
baseline. And finally we need a Mac build bot. But this discussion
should take place in a separate thread.

For now I would like to invite all of you to think about the release
manager role and if is something for you. I will not be available as
release manager for the next release.

Juergen


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

RE: Concerns about the AOO community

[Dennis E. Hamilton]

What gets me about development is that the most contorted possible ever 
development process is builds for Windows, yet a lot of interest is from people 
who want that case to work.  And, of course, we know that the sweet spot for 
Apache OpenOffice adoption is on the Windows platform.  

It is clear why that disparity exists, but the result is an awkward situation, 
especially for attracting developers and testers.

I have no idea how to streamline the build and also get to where there is an 
x64 release also.  My brain melts when I even consider it and I have avoided 
going through the developer training materials.  My bad.

 - Dennis

-Original Message-
From: Roman Sausarnes [mailto:romansausar...@gmail.com] 
Sent: Thursday, October 2, 2014 10:26
To: dev@openoffice.apache.org
Subject: Re: Concerns about the AOO community

Hello,

As a newcomer to development who is looking for a way to get involved in
one project or the other, I thought I would share my impressions.

The LibreOffice website and development materials seem friendlier to
newcomers. It is easier to navigate and find simple instructions for how to
get the code, set up a development environment, or contribute in other
ways. I use a Mac, and almost right away I found a detailed set of
instructions that was (relatively) current for how to build LO for the
first time on my machine.

[ ... ]


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Concerns about the AOO community

[Roman Sausarnes]

And I'm here to help, not just complain :) I'm still working out how I can
contribute...

On Thu, Oct 2, 2014 at 11:17 AM, Roman Sausarnes 
wrote:

> Okay, I'm going to fess up and admit my mistake. I found the link on the
> "Building Guide" page (
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO) that
> takes you to the Mac OS X information.
>
> I see it now - I don't know why I didn't see it before - I was blind to
> it, except it was halfway down a very long page and not at all where I
> would expect to find it. I would expect to find it in the location titled:
> Step-by-Step Building Guide for Different Platforms. At the very top of the
> page is a link that claims to give step-by-step instructions for different
> platforms, but when you click on it, it says nothing about Mac OS X. And I
> still think that the information offered is not as clear or structured as
> the information on the LO site.
>
> I know that all of the information is there somewhere. I have found it in
> the past. It just always feels like I have to dig for it with AOO, whereas
> on LO it is easier.
>
> Hey, programming isn't for wimps. But other noobs have now raised similar
> points, so its more than just "user error".
>
> And I second the observation that the website is confusing - there are
> multiple sites with very different structures, sometimes with contradictory
> or outdated information, and no real semblance of common organization
> between them.
>
> On Thu, Oct 2, 2014 at 11:04 AM, Roman Sausarnes  > wrote:
>
>> I swear I am technically savvy, but I have not found an easy link to the
>> materials you reference.
>>
>> I start at the homepage - www.openoffice.org
>>
>> I click on "I want to participate in OpenOffice" link which takes me
>> here: http://openoffice.apache.org/get-involved.html
>>
>> I clink on the New Volunteer Orientation Modules
>>  link which takes
>> me here: http://openoffice.apache.org/orientation/index.html
>>
>> I click on the Introduction to Development
>>  link
>> which takes me here:
>> http://openoffice.apache.org/orientation/intro-development.html
>>
>> I click on the Building Guide
>>  link
>> which takes me here:
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>>
>> That page has no instructions for how to build on Mac OS X, but it does
>> have a link titled Step-by-Step Building Guide for Different Platforms
>> 
>>  which
>> of course looks very promising.
>>
>> But when you click on that link, it takes you here:
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>>
>> And that page offers detailed instructions for Ubuntu and Windows, but
>> has no links whatsoever to any materials regarding Mac OS X.
>>
>> When I click on the link that you provided, I see the requirements for
>> Mac OS X and I see how to get started that is very helpful.
>>
>> But compare that to the LibreOffice materials. I google "LibreOffice on
>> Mac OS X" and I get the following link:
>> https://wiki.documentfoundation.org/Development/BuildingOnMac
>>
>> I go to that link and it has step by step instructions on what to do.
>>
>> I'm smart enough to be able to find what I am looking for, but I'm just
>> saying that as a total newcomer to both projects LibreOffice made it much
>> easier.
>>
>> On Thu, Oct 2, 2014 at 10:38 AM, Alexandro Colorado 
>> wrote:
>>
>>> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes <
>>> romansausar...@gmail.com>
>>> wrote:
>>>
>>> > Hello,
>>> >
>>> > As a newcomer to development who is looking for a way to get involved
>>> in
>>> > one project or the other, I thought I would share my impressions.
>>> >
>>> > The LibreOffice website and development materials seem friendlier to
>>> > newcomers. It is easier to navigate and find simple instructions for
>>> how to
>>> > get the code, set up a development environment, or contribute in other
>>> > ways. I use a Mac, and almost right away I found a detailed set of
>>> > instructions that was (relatively) current for how to build LO for the
>>> > first time on my machine.
>>> >
>>> > The AOO website is confusing and disorganized for people approaching
>>> it for
>>> > the first time and some of the information is outdated. I still haven't
>>> > found simple instructions for how to build on a Mac. I have found a
>>> set of
>>> > instructions but they are confusing, appear to be outdated, and suggest
>>> > that I need to install older Xcode, etc., without any suggestions or
>>> > resources on how to do it, if it is really necessary, etc.
>>> >
>>>
>>> ​Can you please be more explicit on this. From our angle, we create
>>> modules
>>> so that people could easily find the right information of the way they
>>> want
>>> to cont

Re: Concerns about the AOO community

[Alexandro Colorado]

On 10/2/14, Roman Sausarnes  wrote:
> I swear I am technically savvy, but I have not found an easy link to the
> materials you reference.
>
> I start at the homepage - www.openoffice.org
>
> I click on "I want to participate in OpenOffice" link which takes me here:
> http://openoffice.apache.org/get-involved.html
>
> I clink on the New Volunteer Orientation Modules
>  link which takes me
> here: http://openoffice.apache.org/orientation/index.html
>
> I click on the Introduction to Development
>  link
> which takes me here:
> http://openoffice.apache.org/orientation/intro-development.html
>
> I click on the Building Guide
>  link
> which takes me here:
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>
> That page has no instructions for how to build on Mac OS X, but it does
> have a link titled Step-by-Step Building Guide for Different Platforms
> 
> which
> of course looks very promising.
>
> But when you click on that link, it takes you here:
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>
> And that page offers detailed instructions for Ubuntu and Windows, but has
> no links whatsoever to any materials regarding Mac OS X.
>
> When I click on the link that you provided, I see the requirements for Mac
> OS X and I see how to get started that is very helpful.
>
> But compare that to the LibreOffice materials. I google "LibreOffice on Mac
> OS X" and I get the following link:
> https://wiki.documentfoundation.org/Development/BuildingOnMac
>
> I go to that link and it has step by step instructions on what to do.
>
> I'm smart enough to be able to find what I am looking for, but I'm just
> saying that as a total newcomer to both projects LibreOffice made it much
> easier.

Perhaps the thinking was that mantaining 3 guides is more dificult
than having just 1 guide with annotation for each platform.

However it only took me a few seconds figuring out where the OSX
information was. But if you think that mantaining 3 guides is the way
to go, you can make the comment at doc@openoffice

There are also some formating that could definetly help like having
special alerts and notes for the wiki which you can find here:
{{Documentation/Caution| some text }}
{{Documentation/Notes| some text }}

>
> On Thu, Oct 2, 2014 at 10:38 AM, Alexandro Colorado  wrote:
>
>> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes
>> > >
>> wrote:
>>
>> > Hello,
>> >
>> > As a newcomer to development who is looking for a way to get involved
>> > in
>> > one project or the other, I thought I would share my impressions.
>> >
>> > The LibreOffice website and development materials seem friendlier to
>> > newcomers. It is easier to navigate and find simple instructions for
>> > how
>> to
>> > get the code, set up a development environment, or contribute in other
>> > ways. I use a Mac, and almost right away I found a detailed set of
>> > instructions that was (relatively) current for how to build LO for the
>> > first time on my machine.
>> >
>> > The AOO website is confusing and disorganized for people approaching it
>> for
>> > the first time and some of the information is outdated. I still haven't
>> > found simple instructions for how to build on a Mac. I have found a set
>> of
>> > instructions but they are confusing, appear to be outdated, and suggest
>> > that I need to install older Xcode, etc., without any suggestions or
>> > resources on how to do it, if it is really necessary, etc.
>> >
>>
>> ​Can you please be more explicit on this. From our angle, we create
>> modules
>> so that people could easily find the right information of the way they
>> want
>> to contribute. Going to www.openoffice.org and selecting you want to
>> contribute will lead you to a series of tutorials on how to better get
>> involved. Development starts with building for different platforms,
>> including OSX.
>>
>> All in all is 4 clicks:
>> Homepage -> Contributing page -> Development -> Building -> OSX (
>>
>> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
>> )
>>
>> The instructions are for 4.1 so they are pretty current. ​
>>
>>
>>
>> >
>> > I haven't given up on AOO, and part of me wants to figure out how to do
>> it
>> > and then write the instructions clearly for the next person who comes
>> > along, but you can understand how a person who is given two
>> > opportunities
>> > is tempted to choose the one that is easier to get started on (the hard
>> > work comes later - entry should be easy) and more clearly structured.
>> >
>> > Just my two cents.
>> >
>> > On Thu, Oct 2, 2014 at 10:06 AM, Chuck Davis 
>> > wrote:
>> >
>> > > I've seen quite a number of new people show up here lately indicating
>> > > intere

Re: Concerns about the AOO community

[Roman Sausarnes]

Okay, I'm going to fess up and admit my mistake. I found the link on the
"Building Guide" page (
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO) that
takes you to the Mac OS X information.

I see it now - I don't know why I didn't see it before - I was blind to it,
except it was halfway down a very long page and not at all where I would
expect to find it. I would expect to find it in the location titled:
Step-by-Step Building Guide for Different Platforms. At the very top of the
page is a link that claims to give step-by-step instructions for different
platforms, but when you click on it, it says nothing about Mac OS X. And I
still think that the information offered is not as clear or structured as
the information on the LO site.

I know that all of the information is there somewhere. I have found it in
the past. It just always feels like I have to dig for it with AOO, whereas
on LO it is easier.

Hey, programming isn't for wimps. But other noobs have now raised similar
points, so its more than just "user error".

And I second the observation that the website is confusing - there are
multiple sites with very different structures, sometimes with contradictory
or outdated information, and no real semblance of common organization
between them.

On Thu, Oct 2, 2014 at 11:04 AM, Roman Sausarnes 
wrote:

> I swear I am technically savvy, but I have not found an easy link to the
> materials you reference.
>
> I start at the homepage - www.openoffice.org
>
> I click on "I want to participate in OpenOffice" link which takes me here:
> http://openoffice.apache.org/get-involved.html
>
> I clink on the New Volunteer Orientation Modules
>  link which takes me
> here: http://openoffice.apache.org/orientation/index.html
>
> I click on the Introduction to Development
>  link
> which takes me here:
> http://openoffice.apache.org/orientation/intro-development.html
>
> I click on the Building Guide
>  link
> which takes me here:
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
>
> That page has no instructions for how to build on Mac OS X, but it does
> have a link titled Step-by-Step Building Guide for Different Platforms
> 
>  which
> of course looks very promising.
>
> But when you click on that link, it takes you here:
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
>
> And that page offers detailed instructions for Ubuntu and Windows, but has
> no links whatsoever to any materials regarding Mac OS X.
>
> When I click on the link that you provided, I see the requirements for Mac
> OS X and I see how to get started that is very helpful.
>
> But compare that to the LibreOffice materials. I google "LibreOffice on
> Mac OS X" and I get the following link:
> https://wiki.documentfoundation.org/Development/BuildingOnMac
>
> I go to that link and it has step by step instructions on what to do.
>
> I'm smart enough to be able to find what I am looking for, but I'm just
> saying that as a total newcomer to both projects LibreOffice made it much
> easier.
>
> On Thu, Oct 2, 2014 at 10:38 AM, Alexandro Colorado  wrote:
>
>> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes <
>> romansausar...@gmail.com>
>> wrote:
>>
>> > Hello,
>> >
>> > As a newcomer to development who is looking for a way to get involved in
>> > one project or the other, I thought I would share my impressions.
>> >
>> > The LibreOffice website and development materials seem friendlier to
>> > newcomers. It is easier to navigate and find simple instructions for
>> how to
>> > get the code, set up a development environment, or contribute in other
>> > ways. I use a Mac, and almost right away I found a detailed set of
>> > instructions that was (relatively) current for how to build LO for the
>> > first time on my machine.
>> >
>> > The AOO website is confusing and disorganized for people approaching it
>> for
>> > the first time and some of the information is outdated. I still haven't
>> > found simple instructions for how to build on a Mac. I have found a set
>> of
>> > instructions but they are confusing, appear to be outdated, and suggest
>> > that I need to install older Xcode, etc., without any suggestions or
>> > resources on how to do it, if it is really necessary, etc.
>> >
>>
>> ​Can you please be more explicit on this. From our angle, we create
>> modules
>> so that people could easily find the right information of the way they
>> want
>> to contribute. Going to www.openoffice.org and selecting you want to
>> contribute will lead you to a series of tutorials on how to better get
>> involved. Development starts with building for different platforms,
>> including OSX.
>>
>> All in all is 4 clicks:
>> Homepage -> Contributing page 

Re: Concerns about the AOO community

[Roman Sausarnes]

I swear I am technically savvy, but I have not found an easy link to the
materials you reference.

I start at the homepage - www.openoffice.org

I click on "I want to participate in OpenOffice" link which takes me here:
http://openoffice.apache.org/get-involved.html

I clink on the New Volunteer Orientation Modules
 link which takes me
here: http://openoffice.apache.org/orientation/index.html

I click on the Introduction to Development
 link
which takes me here:
http://openoffice.apache.org/orientation/intro-development.html

I click on the Building Guide
 link
which takes me here:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

That page has no instructions for how to build on Mac OS X, but it does
have a link titled Step-by-Step Building Guide for Different Platforms

which
of course looks very promising.

But when you click on that link, it takes you here:
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step

And that page offers detailed instructions for Ubuntu and Windows, but has
no links whatsoever to any materials regarding Mac OS X.

When I click on the link that you provided, I see the requirements for Mac
OS X and I see how to get started that is very helpful.

But compare that to the LibreOffice materials. I google "LibreOffice on Mac
OS X" and I get the following link:
https://wiki.documentfoundation.org/Development/BuildingOnMac

I go to that link and it has step by step instructions on what to do.

I'm smart enough to be able to find what I am looking for, but I'm just
saying that as a total newcomer to both projects LibreOffice made it much
easier.

On Thu, Oct 2, 2014 at 10:38 AM, Alexandro Colorado  wrote:

> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes  >
> wrote:
>
> > Hello,
> >
> > As a newcomer to development who is looking for a way to get involved in
> > one project or the other, I thought I would share my impressions.
> >
> > The LibreOffice website and development materials seem friendlier to
> > newcomers. It is easier to navigate and find simple instructions for how
> to
> > get the code, set up a development environment, or contribute in other
> > ways. I use a Mac, and almost right away I found a detailed set of
> > instructions that was (relatively) current for how to build LO for the
> > first time on my machine.
> >
> > The AOO website is confusing and disorganized for people approaching it
> for
> > the first time and some of the information is outdated. I still haven't
> > found simple instructions for how to build on a Mac. I have found a set
> of
> > instructions but they are confusing, appear to be outdated, and suggest
> > that I need to install older Xcode, etc., without any suggestions or
> > resources on how to do it, if it is really necessary, etc.
> >
>
> ​Can you please be more explicit on this. From our angle, we create modules
> so that people could easily find the right information of the way they want
> to contribute. Going to www.openoffice.org and selecting you want to
> contribute will lead you to a series of tutorials on how to better get
> involved. Development starts with building for different platforms,
> including OSX.
>
> All in all is 4 clicks:
> Homepage -> Contributing page -> Development -> Building -> OSX (
>
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
> )
>
> The instructions are for 4.1 so they are pretty current. ​
>
>
>
> >
> > I haven't given up on AOO, and part of me wants to figure out how to do
> it
> > and then write the instructions clearly for the next person who comes
> > along, but you can understand how a person who is given two opportunities
> > is tempted to choose the one that is easier to get started on (the hard
> > work comes later - entry should be easy) and more clearly structured.
> >
> > Just my two cents.
> >
> > On Thu, Oct 2, 2014 at 10:06 AM, Chuck Davis  wrote:
> >
> > > I've seen quite a number of new people show up here lately indicating
> > > interest coming from someplace.  If one out of 10 of them sticks and
> > > becomes a regular contributor the project is in a very good position I
> > > think.
> > >
> > > My observations regarding LO:
> > > 1)  They've copied some features from MS Office that make it equally
> > > difficult to useIt's not as pleasant to use as AOO.  It's very
> > > unfortunate the distributions have adopted LO in lieu of AOO.
> > > 2)  Their constant AOO bashing is a real turn-off for me and I hope
> > > others as well.  I don't think I want their people in our camp.
> > > 3)  They seem to be very proud of getting rid of Java and replacing it
> > > with Python.  I've looked at Python a little and it seems to me any
> > > language depende

Re: Concerns about the AOO community

[Alexandro Colorado]

On Thu, Oct 2, 2014 at 12:46 PM, Alain Sanguinetti 
wrote:

> Le 02.10.2014 19:38, Alexandro Colorado a écrit :
>
>  On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes <
>> romansausar...@gmail.com>
>> wrote:
>>
>>  Hello,
>>>
>>> As a newcomer to development who is looking for a way to get involved in
>>> one project or the other, I thought I would share my impressions.
>>>
>>> The LibreOffice website and development materials seem friendlier to
>>> newcomers. It is easier to navigate and find simple instructions for how
>>> to
>>> get the code, set up a development environment, or contribute in other
>>> ways. I use a Mac, and almost right away I found a detailed set of
>>> instructions that was (relatively) current for how to build LO for the
>>> first time on my machine.
>>>
>>> The AOO website is confusing and disorganized for people approaching it
>>> for
>>> the first time and some of the information is outdated. I still haven't
>>> found simple instructions for how to build on a Mac. I have found a set
>>> of
>>> instructions but they are confusing, appear to be outdated, and suggest
>>> that I need to install older Xcode, etc., without any suggestions or
>>> resources on how to do it, if it is really necessary, etc.
>>>
>>>
>> ​Can you please be more explicit on this. From our angle, we create
>> modules
>> so that people could easily find the right information of the way they
>> want
>> to contribute. Going to www.openoffice.org and selecting you want to
>> contribute will lead you to a series of tutorials on how to better get
>> involved. Development starts with building for different platforms,
>> including OSX.
>>
>> All in all is 4 clicks:
>> Homepage -> Contributing page -> Development -> Building -> OSX (
>> https://wiki.openoffice.org/wiki/Documentation/Building_
>> Guide_AOO/Building_on_MacOsX
>> )
>>
>> The instructions are for 4.1 so they are pretty current. ​
>>
>>
>>
>>
> I am a newcomer as well to the Apache OpenOffice community and I have the
> same feeling.
> One thing that struck me is the number of websites/wiki that exists.
> You have openoffice.org. ( which actually looks a little different from
> openoffice.org/fr ! )
> Then you have http://openoffice.apache.org
> And there are Confluence and MediaWiki Wikis.
> All websites looks great but I think it needs consolidation at one place.
>
> But the new volunteer orientation modules are great.


​When OOo join apache we were stuck with a website and wiki that apache
used for their projects (Confluence and .apache.org). That's where the
duplication happened. Semantically on the project we delegate the apache
website/wiki to project-related information (new launch, etc). And
openoffice.org website/wiki to product-related information (release notes,
etc). Ideally the apache.org assets should be on an extranet while the
openoffice.org should be public. This being a public project we have them
both. In principle I agreed, that it would be easier if we just forward
everything to the openoffice.org sites.​ Confluence has proven to be a pain
in the butt while the apache.org website have content that can easily be
handled on the main openoffice.org site. I guess is just a decision the
project most make.



>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: Concerns about the AOO community

[Alexandro Colorado]

On Thu, Oct 2, 2014 at 12:38 PM, Alexandro Colorado  wrote:

>
>
> On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes  > wrote:
>
>> Hello,
>>
>> As a newcomer to development who is looking for a way to get involved in
>> one project or the other, I thought I would share my impressions.
>>
>> The LibreOffice website and development materials seem friendlier to
>> newcomers. It is easier to navigate and find simple instructions for how
>> to
>> get the code, set up a development environment, or contribute in other
>> ways. I use a Mac, and almost right away I found a detailed set of
>> instructions that was (relatively) current for how to build LO for the
>> first time on my machine.
>>
>> The AOO website is confusing and disorganized for people approaching it
>> for
>> the first time and some of the information is outdated. I still haven't
>> found simple instructions for how to build on a Mac. I have found a set of
>> instructions but they are confusing, appear to be outdated, and suggest
>> that I need to install older Xcode, etc., without any suggestions or
>> resources on how to do it, if it is really necessary, etc.
>>
>
> ​Can you please be more explicit on this. From our angle, we create
> modules so that people could easily find the right information of the way
> they want to contribute. Going to www.openoffice.org and selecting you
> want to contribute will lead you to a series of tutorials on how to better
> get involved. Development starts with building for different platforms,
> including OSX.
>
> All in all is 4 clicks:
> Homepage -> Contributing page -> Development -> Building -> OSX (
> https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
> )
>

​Furthermore I went to LibreOffice tutorials and they are mostly the same
process:
  Homepage -> Community/Development -> Development wiki -> OSX​

​What I can say is that you dont have to read an intro in Development to
find the link to OSX since Development is not an 'article' but a macro menu
where you can find ways to jumpstart things like 'Getting Started' and/or
'​Easy Hacks'. However I find it confusing on the first Development menu as
Learning is not the first option but instead is getting the code.

Perhaps having a visual menu would be better than just filling out pages
with text.



>
> The instructions are for 4.1 so they are pretty current. ​
>
>
>
>>
>> I haven't given up on AOO, and part of me wants to figure out how to do it
>> and then write the instructions clearly for the next person who comes
>> along, but you can understand how a person who is given two opportunities
>> is tempted to choose the one that is easier to get started on (the hard
>> work comes later - entry should be easy) and more clearly structured.
>>
>> Just my two cents.
>>
>> On Thu, Oct 2, 2014 at 10:06 AM, Chuck Davis  wrote:
>>
>> > I've seen quite a number of new people show up here lately indicating
>> > interest coming from someplace.  If one out of 10 of them sticks and
>> > becomes a regular contributor the project is in a very good position I
>> > think.
>> >
>> > My observations regarding LO:
>> > 1)  They've copied some features from MS Office that make it equally
>> > difficult to useIt's not as pleasant to use as AOO.  It's very
>> > unfortunate the distributions have adopted LO in lieu of AOO.
>> > 2)  Their constant AOO bashing is a real turn-off for me and I hope
>> > others as well.  I don't think I want their people in our camp.
>> > 3)  They seem to be very proud of getting rid of Java and replacing it
>> > with Python.  I've looked at Python a little and it seems to me any
>> > language dependent on indentation rather than syntax is
>> > justdumb!  There is nothing wrong with Java -- especially now
>> > that OpenJDK is the reference implementation and is being worked on by
>> > every major player except MS.
>> > 4)  LO seems to have major QC issues.  The quality is definitely
>> > several notches below where AOO rests in my experience.
>> >
>> > These are just my observations as a long time OpenOffice user.  And
>> > Apache has some very interesting related projects (i.e. ODF Toolkit)
>> > that can propel ODF as a standard reporting framework as well as the
>> > new project to read and write OOXML for document exchange.
>> >
>> > My advice:  stay the course.  Emphasize quality and dependability over
>> > glitz.  If developers are not attracted to AOO on those terms they're
>> > not developers the project needs.  Those of us in business just need a
>> > tool to get our work done and it doesn't need to be fancy -- just
>> > dependable.  LO falls on it's face at this point.
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> > For additional commands, e-mail: dev-h...@openoffice.apache.org
>> >
>> >
>>
>
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7

Re: Concerns about the AOO community

[Alain Sanguinetti]

Le 02.10.2014 19:38, Alexandro Colorado a écrit :
On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes 


wrote:


Hello,

As a newcomer to development who is looking for a way to get involved 
in

one project or the other, I thought I would share my impressions.

The LibreOffice website and development materials seem friendlier to
newcomers. It is easier to navigate and find simple instructions for 
how to

get the code, set up a development environment, or contribute in other
ways. I use a Mac, and almost right away I found a detailed set of
instructions that was (relatively) current for how to build LO for the
first time on my machine.

The AOO website is confusing and disorganized for people approaching 
it for
the first time and some of the information is outdated. I still 
haven't
found simple instructions for how to build on a Mac. I have found a 
set of
instructions but they are confusing, appear to be outdated, and 
suggest

that I need to install older Xcode, etc., without any suggestions or
resources on how to do it, if it is really necessary, etc.



​Can you please be more explicit on this. From our angle, we create 
modules
so that people could easily find the right information of the way they 
want

to contribute. Going to www.openoffice.org and selecting you want to
contribute will lead you to a series of tutorials on how to better get
involved. Development starts with building for different platforms,
including OSX.

All in all is 4 clicks:
Homepage -> Contributing page -> Development -> Building -> OSX (
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
)

The instructions are for 4.1 so they are pretty current. ​





I am a newcomer as well to the Apache OpenOffice community and I have 
the same feeling.

One thing that struck me is the number of websites/wiki that exists.
You have openoffice.org. ( which actually looks a little different from 
openoffice.org/fr ! )

Then you have http://openoffice.apache.org
And there are Confluence and MediaWiki Wikis.
All websites looks great but I think it needs consolidation at one 
place.


But the new volunteer orientation modules are great.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Concerns about the AOO community

[Alexandro Colorado]

On Thu, Oct 2, 2014 at 12:25 PM, Roman Sausarnes 
wrote:

> Hello,
>
> As a newcomer to development who is looking for a way to get involved in
> one project or the other, I thought I would share my impressions.
>
> The LibreOffice website and development materials seem friendlier to
> newcomers. It is easier to navigate and find simple instructions for how to
> get the code, set up a development environment, or contribute in other
> ways. I use a Mac, and almost right away I found a detailed set of
> instructions that was (relatively) current for how to build LO for the
> first time on my machine.
>
> The AOO website is confusing and disorganized for people approaching it for
> the first time and some of the information is outdated. I still haven't
> found simple instructions for how to build on a Mac. I have found a set of
> instructions but they are confusing, appear to be outdated, and suggest
> that I need to install older Xcode, etc., without any suggestions or
> resources on how to do it, if it is really necessary, etc.
>

​Can you please be more explicit on this. From our angle, we create modules
so that people could easily find the right information of the way they want
to contribute. Going to www.openoffice.org and selecting you want to
contribute will lead you to a series of tutorials on how to better get
involved. Development starts with building for different platforms,
including OSX.

All in all is 4 clicks:
Homepage -> Contributing page -> Development -> Building -> OSX (
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_MacOsX
)

The instructions are for 4.1 so they are pretty current. ​



>
> I haven't given up on AOO, and part of me wants to figure out how to do it
> and then write the instructions clearly for the next person who comes
> along, but you can understand how a person who is given two opportunities
> is tempted to choose the one that is easier to get started on (the hard
> work comes later - entry should be easy) and more clearly structured.
>
> Just my two cents.
>
> On Thu, Oct 2, 2014 at 10:06 AM, Chuck Davis  wrote:
>
> > I've seen quite a number of new people show up here lately indicating
> > interest coming from someplace.  If one out of 10 of them sticks and
> > becomes a regular contributor the project is in a very good position I
> > think.
> >
> > My observations regarding LO:
> > 1)  They've copied some features from MS Office that make it equally
> > difficult to useIt's not as pleasant to use as AOO.  It's very
> > unfortunate the distributions have adopted LO in lieu of AOO.
> > 2)  Their constant AOO bashing is a real turn-off for me and I hope
> > others as well.  I don't think I want their people in our camp.
> > 3)  They seem to be very proud of getting rid of Java and replacing it
> > with Python.  I've looked at Python a little and it seems to me any
> > language dependent on indentation rather than syntax is
> > justdumb!  There is nothing wrong with Java -- especially now
> > that OpenJDK is the reference implementation and is being worked on by
> > every major player except MS.
> > 4)  LO seems to have major QC issues.  The quality is definitely
> > several notches below where AOO rests in my experience.
> >
> > These are just my observations as a long time OpenOffice user.  And
> > Apache has some very interesting related projects (i.e. ODF Toolkit)
> > that can propel ODF as a standard reporting framework as well as the
> > new project to read and write OOXML for document exchange.
> >
> > My advice:  stay the course.  Emphasize quality and dependability over
> > glitz.  If developers are not attracted to AOO on those terms they're
> > not developers the project needs.  Those of us in business just need a
> > tool to get our work done and it doesn't need to be fancy -- just
> > dependable.  LO falls on it's face at this point.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> >
>



-- 
Alexandro Colorado
Apache OpenOffice Contributor
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Re: Concerns about the AOO community

[Roman Sausarnes]

Hello,

As a newcomer to development who is looking for a way to get involved in
one project or the other, I thought I would share my impressions.

The LibreOffice website and development materials seem friendlier to
newcomers. It is easier to navigate and find simple instructions for how to
get the code, set up a development environment, or contribute in other
ways. I use a Mac, and almost right away I found a detailed set of
instructions that was (relatively) current for how to build LO for the
first time on my machine.

The AOO website is confusing and disorganized for people approaching it for
the first time and some of the information is outdated. I still haven't
found simple instructions for how to build on a Mac. I have found a set of
instructions but they are confusing, appear to be outdated, and suggest
that I need to install older Xcode, etc., without any suggestions or
resources on how to do it, if it is really necessary, etc.

I haven't given up on AOO, and part of me wants to figure out how to do it
and then write the instructions clearly for the next person who comes
along, but you can understand how a person who is given two opportunities
is tempted to choose the one that is easier to get started on (the hard
work comes later - entry should be easy) and more clearly structured.

Just my two cents.

On Thu, Oct 2, 2014 at 10:06 AM, Chuck Davis  wrote:

> I've seen quite a number of new people show up here lately indicating
> interest coming from someplace.  If one out of 10 of them sticks and
> becomes a regular contributor the project is in a very good position I
> think.
>
> My observations regarding LO:
> 1)  They've copied some features from MS Office that make it equally
> difficult to useIt's not as pleasant to use as AOO.  It's very
> unfortunate the distributions have adopted LO in lieu of AOO.
> 2)  Their constant AOO bashing is a real turn-off for me and I hope
> others as well.  I don't think I want their people in our camp.
> 3)  They seem to be very proud of getting rid of Java and replacing it
> with Python.  I've looked at Python a little and it seems to me any
> language dependent on indentation rather than syntax is
> justdumb!  There is nothing wrong with Java -- especially now
> that OpenJDK is the reference implementation and is being worked on by
> every major player except MS.
> 4)  LO seems to have major QC issues.  The quality is definitely
> several notches below where AOO rests in my experience.
>
> These are just my observations as a long time OpenOffice user.  And
> Apache has some very interesting related projects (i.e. ODF Toolkit)
> that can propel ODF as a standard reporting framework as well as the
> new project to read and write OOXML for document exchange.
>
> My advice:  stay the course.  Emphasize quality and dependability over
> glitz.  If developers are not attracted to AOO on those terms they're
> not developers the project needs.  Those of us in business just need a
> tool to get our work done and it doesn't need to be fancy -- just
> dependable.  LO falls on it's face at this point.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Concerns about the AOO community

[Chuck Davis]

I've seen quite a number of new people show up here lately indicating
interest coming from someplace.  If one out of 10 of them sticks and
becomes a regular contributor the project is in a very good position I
think.

My observations regarding LO:
1)  They've copied some features from MS Office that make it equally
difficult to useIt's not as pleasant to use as AOO.  It's very
unfortunate the distributions have adopted LO in lieu of AOO.
2)  Their constant AOO bashing is a real turn-off for me and I hope
others as well.  I don't think I want their people in our camp.
3)  They seem to be very proud of getting rid of Java and replacing it
with Python.  I've looked at Python a little and it seems to me any
language dependent on indentation rather than syntax is
justdumb!  There is nothing wrong with Java -- especially now
that OpenJDK is the reference implementation and is being worked on by
every major player except MS.
4)  LO seems to have major QC issues.  The quality is definitely
several notches below where AOO rests in my experience.

These are just my observations as a long time OpenOffice user.  And
Apache has some very interesting related projects (i.e. ODF Toolkit)
that can propel ODF as a standard reporting framework as well as the
new project to read and write OOXML for document exchange.

My advice:  stay the course.  Emphasize quality and dependability over
glitz.  If developers are not attracted to AOO on those terms they're
not developers the project needs.  Those of us in business just need a
tool to get our work done and it doesn't need to be fancy -- just
dependable.  LO falls on it's face at this point.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: release manager for the next release

[Kay Schenk]

On Thu, Oct 2, 2014 at 6:04 AM, Jürgen Schmidt 
wrote:

> On 02/10/14 14:33, Rob Weir wrote:
> > On Thu, Oct 2, 2014 at 7:05 AM, Jürgen Schmidt 
> wrote:
> >> Hi,
> >>
> >> after a longer vacation and some silence in the past weeks I would like
> >> to discuss the release manager role.
> >>
> >> I think it's time that somebody else takes over this role and drives
> >> active the next release. I did it since the beginning of OpenOffice at
> >> Apache but I think it is a good opportunity for somebody to be more
> >> active in the community and take over some responsibility.
> >>
> >
> > Hi Juergen,
> >
> > Thanks, from all I assume, for your efforts in this area.  Not only
> > were you the Release Manager, but you defined the role itself for AOO,
> > a project with more complicated release requirements than most others
> > at Apache.
>

Juergen's role as release manager has been outstanding as far as I'm
concerned! Thank you, Juergen.


> >
> > If someone was considering stepping in as the Release Manager for the
> > next release, what should they be looking at?  Is there a wiki page or
> > other documentation that defines the process?
>
> not yet but we should collect the different pieces in one place to make
> it easier and to have a reference or some kind of check list ...
>

This kind of check list is vital to passing on the release manager role.

I also fully agree that we should take future client distributions from the
Apache buildbot. We need to make the Mac buildbot a priority for this.


>
>
> >
> > Also, are you able to review and update (if needed) the available
> > documentation and/or help mentor the next Release Manager?Or do
> > you think this is all documented enough that someone can just step in
> > and RTFM?
>
> sure I will be available for any questions and will support the release
> manager.
>
> Juergen
>
>
>
> >
> > Regards,
> >
> > -Rob
> >
> >
> >> We have released some important milestones over the years and have
> >> enough experience and know what's necessary. Whoever takes over the
> >> release manager role won't be alone and will get the support from the
> >> community. In the same way I got it in the past.
> >>
> >> We had discussions about the way how to communicate and track the
> >> release planning and the progress and now it's the time that people can
> >> realize this. It's always room for improvements.
> >>
> >> The goal is that this somewhat important role is circulating and not
> >> depending on one person only. The releases are anyway a community effort
> >> and the release manager have to take care of some necessary formalism.
> >>
> >> And to make it easier a further goal is to be able to take binary builds
> >> from our build bots and release them. Currently we rely on builds made
> >> by community members but I think it's better to use official build bots
> >> for that. This means that we have to check the Windows build bot and the
> >> binaries if they can be used already or what is missing. It means that
> >> we need Linux build bots with the correct baseline or increase the
> >> baseline. And finally we need a Mac build bot. But this discussion
> >> should take place in a separate thread.
> >>
> >> For now I would like to invite all of you to think about the release
> >> manager role and if is something for you. I will not be available as
> >> release manager for the next release.
> >>
> >> Juergen
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
-
MzK

"You only get one chance at a first impression.
 I suggest Julia Child, because it's easy to do."
   -- Phil Dunphy (Modern Family)

RE: Concerns about the AOO community

[Dennis E. Hamilton]

A side comment.  It seems that it has escaped everyone's attention that the 
latest release(s) of LibreOffice are not under [L]GPL.  The releases are under 
MPL 2.0 (the Mozilla license).  

The LibreOffice codebase itself is now a combination of Apache licensed code 
(from guess where?) and MPL 2.0 modifications.  It appears to me that the 
source code is now multi-licensed (not dual-licensed) under both Apache License 
2.0 (for the base code) and MPL (for the changes made by the TDF to make their 
core source code).

I agree that the osmosis between the projects is still one-way and it is not 
easy to change because the contributors to LibO have only granted a dual MPL 
and LGPL license to their contributions.  TDF has taken the MPL option.  That 
is still toxic for incorporation as source code in any Apache Software 
Foundation Project code base.

With regard to potential remedies, I am in complete accord with Ian's 
appraisal.  Especially for matters applicable to the interoperable usage of 
ODF, the lack of cooperation is very troublesome and may, if not addressed, be 
fatal to both projects.  

 - Dennis

-Original Message-
From: Ian Lynch [mailto:ianrly...@gmail.com] 
Sent: Thursday, October 2, 2014 05:47
To: dev@openoffice.apache.org
Subject: Re: Concerns about the AOO community

It would be better for the projects to merge, but the details (license,
community)  clearly matter a lot to some people. If there was a better
spirit of cooperation most of the effort could go into AOO with just some
minor things for the GPL version derived from it in an agreed way so that
that could satisfy the needs of that particular market. But to do that we
would have to get a lot more trust and "friendliness" between the two
projects. It doesn't seem too likely at present.

[ ... ]


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [EXTENSIONS] how is the extension constructor called

[John D'Orazio]

Does this mean it's a bug in the way open office is implementing the java
add-ins generated by the NetBeans plugin? (I'm the one that opened the
issue about this in the forum, seeing I'm trying to create a Writer add-in
using the NetBeans plugin.)

don John R. D'Orazio
cappellano coordinatore

Servizio di Cappellania - Università degli Studi Roma Tre
Piazzale San Paolo 1/d - 00120 Città del Vaticano
Tel. 06.69.88.08.09 - Cell. +39 333.25.45.447
E-mail: cappella...@uniroma3.it, cappellania.uniro...@gmail.com
Sito Web: http://www.cappellaniauniroma3.org
Facebook: https://www.facebook.com/cappellania.uniroma3
Twitter: https://twitter.com/CappellaniaR3

Il 02/ott/2014 14:19 "Jürgen Schmidt"  ha scritto:

> On 01/10/14 12:19, Carl Marcum wrote:
> >
> > On 10/01/2014 02:25 AM, Jürgen Schmidt wrote:
> >> On 01/10/14 02:19, Carl Marcum wrote:
> >>> Amenel,
> >>>
> >>> I am cross posting to dev since the original message didn't get copied:
> >>>
> >>> On 09/30/2014 09:39 AM, Amenel VOGLOZIN wrote:
>  Hi Carl,
>  I don't know whether it was intended behavior or not. I have ran into
>  this problem in an extension that I started writing in May or June and
>  it was an issue in that the constructor was called about as many times
>  as i opened the menu.
> 
>  I posted a message similar to yours to this mailing list and Ariel
>  gave me a solution which was to use a singleton. As a result, I moved
>  the construction code, and handlers, and event listeners, and most of
>  my code actually, into a helper class which implemented a Singleton
>  pattern. From then on, things went smoothly, with the notable
>  exception that the application exit event is posted as many times as
>  there are frames opened. A specific boolean variable can guard a code
>  section so no problem there either.
> >>
> >> And this is the preferred way to do it, the NB plugin wizard generates a
> >> very basic and simplified skeleton only. There were plans to extend it
> >> and include a little bit more logic but it was never implemented.
> >>
> >> Juergen
> >>
> >>
> >
> > I was checking in to a new issue opened on the netbeans plugin. [1]
> >
> > For every menu item for the AddOn in the current context (ex Writer),
> > the constructor is called then the Menu is first clicked.
> > If there are 2 menu items the constructor is ran twice.
> > This only happens on the first time per context opened.
> >
> > Is this expected behavior?
> >
> > Is the constructor called from office?
> >
> > If so it's not a bug in the plugin.
>
> I don't think it's a bug in the plugin
>
> Juergen
>
> >
> > [1] https://issues.apache.org/ooo/show_bug.cgi?id=125691
> >
> > Thanks,
> > Carl
> >
> 
>  You might want to search the archives for Ariel's reply to my message.
>  Cheers,
>  -Amenel.
> 
> 
> 
> 
>  Le Dimanche 28 septembre 2014 20h36, Carl Marcum 
>  a écrit :
> 
> 
> 
>  Hi All,
> 
>  I was checking in to a new issue opened on the netbeans plugin. [1]
> 
>  For every menu item for the AddOn in the current context (ex Writer),
>  the constructor is called then the Menu is first clicked.
>  If there are 2 menu items the constructor is ran twice.
>  This only happens on the first time per context opened.
> 
>  Is this expected behavior?
> 
>  [1] https://issues.apache.org/ooo/show_bug.cgi?id=125691
> 
>  Thanks,
>  Carl
> 
>  -
>  To unsubscribe, e-mail: api-unsubscr...@openoffice.apache.org
>  For additional commands, e-mail: api-h...@openoffice.apache.org
> 
> >>>
> >>> Do you remember which list the post was on?
> >>>
> >>> Thanks,
> >>> Carl
> >>>
> >>>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: release manager for the next release

[Jürgen Schmidt]

On 02/10/14 14:33, Rob Weir wrote:
> On Thu, Oct 2, 2014 at 7:05 AM, Jürgen Schmidt  wrote:
>> Hi,
>>
>> after a longer vacation and some silence in the past weeks I would like
>> to discuss the release manager role.
>>
>> I think it's time that somebody else takes over this role and drives
>> active the next release. I did it since the beginning of OpenOffice at
>> Apache but I think it is a good opportunity for somebody to be more
>> active in the community and take over some responsibility.
>>
> 
> Hi Juergen,
> 
> Thanks, from all I assume, for your efforts in this area.  Not only
> were you the Release Manager, but you defined the role itself for AOO,
> a project with more complicated release requirements than most others
> at Apache.
> 
> If someone was considering stepping in as the Release Manager for the
> next release, what should they be looking at?  Is there a wiki page or
> other documentation that defines the process?

not yet but we should collect the different pieces in one place to make
it easier and to have a reference or some kind of check list ...


> 
> Also, are you able to review and update (if needed) the available
> documentation and/or help mentor the next Release Manager?Or do
> you think this is all documented enough that someone can just step in
> and RTFM?

sure I will be available for any questions and will support the release
manager.

Juergen



> 
> Regards,
> 
> -Rob
> 
> 
>> We have released some important milestones over the years and have
>> enough experience and know what's necessary. Whoever takes over the
>> release manager role won't be alone and will get the support from the
>> community. In the same way I got it in the past.
>>
>> We had discussions about the way how to communicate and track the
>> release planning and the progress and now it's the time that people can
>> realize this. It's always room for improvements.
>>
>> The goal is that this somewhat important role is circulating and not
>> depending on one person only. The releases are anyway a community effort
>> and the release manager have to take care of some necessary formalism.
>>
>> And to make it easier a further goal is to be able to take binary builds
>> from our build bots and release them. Currently we rely on builds made
>> by community members but I think it's better to use official build bots
>> for that. This means that we have to check the Windows build bot and the
>> binaries if they can be used already or what is missing. It means that
>> we need Linux build bots with the correct baseline or increase the
>> baseline. And finally we need a Mac build bot. But this discussion
>> should take place in a separate thread.
>>
>> For now I would like to invite all of you to think about the release
>> manager role and if is something for you. I will not be available as
>> release manager for the next release.
>>
>> Juergen
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Concerns about the AOO community

[Ian Lynch]

It would be better for the projects to merge, but the details (license,
community)  clearly matter a lot to some people. If there was a better
spirit of cooperation most of the effort could go into AOO with just some
minor things for the GPL version derived from it in an agreed way so that
that could satisfy the needs of that particular market. But to do that we
would have to get a lot more trust and "friendliness" between the two
projects. It doesn't seem too likely at present.

On 2 October 2014 12:55, Jürgen Schmidt  wrote:

> On 02/10/14 01:44, Rob Weir wrote:
> > On Wed, Oct 1, 2014 at 4:34 PM, Alexandro Colorado 
> wrote:
> >> On G+ I have hold a conversation with Bruce Byfield and Jos from KDE
> >> about the continuation of the Apache OpenOffice community and how the
> >> way that the community has enter lately into a dormant stage with very
> >> little traffic.
> >>
> >> Althought I do seem that is an exageration, I feel that is true that
> >> traffic has reach its lowest in several months. I wonder what is going
> >> on with the community as well as overal adoption and concern of a lack
> >> of marketing strategy.
> >>
> >> I would love to hear from the community managers to have an evaluation.
> >>
> >
> > Community mangers?  Come on, you know that is not how we roll at Apache!
> >
> > What is amazing to be is how much LO sees a merger of the projects as
> > a threat to them.
> >
> > Here's the background.  At the LO conference one of the presenters
> > spoke in favor of merging LO with AOO, of combining the efforts.  This
> > was the IT Head from the Swiss Supreme Court IT office, who also said
> > that they preferred to use AOO for its superior stability compared to
> > LO.
> >
> >
> https://joinup.ec.europa.eu/community/osor/news/open-and-libre-office-projects-should-reunite
> >
> > As you can imagine, having a speaker at a LO conference say nice
> > things about AOO and to suggest cooperation with AOO was an insult
> > that could not be permitted.   So LO marketing went into over-drive to
> > try to kill that message.  That's why we see articles like this, and
> > recent related blog posts by Simon and Charles.
> >
> > But it does make me wonder:  What are they so afraid of?  Why do they
> > think the idea of cooperation so dangerous?   Why do they think that
> > users are so wrong to value stability and to think that the two
> > projects would work better together?
>
> This is indeed a good question. I believe the TDF and LO community did a
> really good job to setup the foundation, the community and the project.
> But it is also a fact that LO benefits a lot of the things we have done
> and do in AOO.
>
> It's still a valid question why both projects doesn't cooperate better
> and focus together on important improvements. From my perspective it
> simply doesn't make sense and together we could reach much more.
>
> Juergen
>
> >
> >
> > -Rob
> >
> >> --
> >> Alexandro Colorado
> >> Apache OpenOffice Contributor
> >> 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> >> For additional commands, e-mail: dev-h...@openoffice.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 
Ian

Ofqual Accredited Qualifications


Headline points in the 2014, 2015, 2016 school league tables

Baseline testing and progress measures


The Learning Machine Limited, Reg Office, Unit 4D Gagarin, Lichfield
Road Industrial Estate, Tamworth, Staffordshire, B79 7GN. Reg No:
05560797, Registered in England and Wales. +44 (0)1827 305940

Re: release manager for the next release

[Rob Weir]

On Thu, Oct 2, 2014 at 7:05 AM, Jürgen Schmidt  wrote:
> Hi,
>
> after a longer vacation and some silence in the past weeks I would like
> to discuss the release manager role.
>
> I think it's time that somebody else takes over this role and drives
> active the next release. I did it since the beginning of OpenOffice at
> Apache but I think it is a good opportunity for somebody to be more
> active in the community and take over some responsibility.
>

Hi Juergen,

Thanks, from all I assume, for your efforts in this area.  Not only
were you the Release Manager, but you defined the role itself for AOO,
a project with more complicated release requirements than most others
at Apache.

If someone was considering stepping in as the Release Manager for the
next release, what should they be looking at?  Is there a wiki page or
other documentation that defines the process?

Also, are you able to review and update (if needed) the available
documentation and/or help mentor the next Release Manager?Or do
you think this is all documented enough that someone can just step in
and RTFM?

Regards,

-Rob


> We have released some important milestones over the years and have
> enough experience and know what's necessary. Whoever takes over the
> release manager role won't be alone and will get the support from the
> community. In the same way I got it in the past.
>
> We had discussions about the way how to communicate and track the
> release planning and the progress and now it's the time that people can
> realize this. It's always room for improvements.
>
> The goal is that this somewhat important role is circulating and not
> depending on one person only. The releases are anyway a community effort
> and the release manager have to take care of some necessary formalism.
>
> And to make it easier a further goal is to be able to take binary builds
> from our build bots and release them. Currently we rely on builds made
> by community members but I think it's better to use official build bots
> for that. This means that we have to check the Windows build bot and the
> binaries if they can be used already or what is missing. It means that
> we need Linux build bots with the correct baseline or increase the
> baseline. And finally we need a Mac build bot. But this discussion
> should take place in a separate thread.
>
> For now I would like to invite all of you to think about the release
> manager role and if is something for you. I will not be available as
> release manager for the next release.
>
> Juergen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [EXTENSIONS] how is the extension constructor called

[Jürgen Schmidt]

On 01/10/14 12:19, Carl Marcum wrote:
> 
> On 10/01/2014 02:25 AM, Jürgen Schmidt wrote:
>> On 01/10/14 02:19, Carl Marcum wrote:
>>> Amenel,
>>>
>>> I am cross posting to dev since the original message didn't get copied:
>>>
>>> On 09/30/2014 09:39 AM, Amenel VOGLOZIN wrote:
 Hi Carl,
 I don't know whether it was intended behavior or not. I have ran into
 this problem in an extension that I started writing in May or June and
 it was an issue in that the constructor was called about as many times
 as i opened the menu.

 I posted a message similar to yours to this mailing list and Ariel
 gave me a solution which was to use a singleton. As a result, I moved
 the construction code, and handlers, and event listeners, and most of
 my code actually, into a helper class which implemented a Singleton
 pattern. From then on, things went smoothly, with the notable
 exception that the application exit event is posted as many times as
 there are frames opened. A specific boolean variable can guard a code
 section so no problem there either.
>>
>> And this is the preferred way to do it, the NB plugin wizard generates a
>> very basic and simplified skeleton only. There were plans to extend it
>> and include a little bit more logic but it was never implemented.
>>
>> Juergen
>>
>>
> 
> I was checking in to a new issue opened on the netbeans plugin. [1]
> 
> For every menu item for the AddOn in the current context (ex Writer),
> the constructor is called then the Menu is first clicked.
> If there are 2 menu items the constructor is ran twice.
> This only happens on the first time per context opened.
> 
> Is this expected behavior?
> 
> Is the constructor called from office?
> 
> If so it's not a bug in the plugin.

I don't think it's a bug in the plugin

Juergen

> 
> [1] https://issues.apache.org/ooo/show_bug.cgi?id=125691
> 
> Thanks,
> Carl
> 

 You might want to search the archives for Ariel's reply to my message.
 Cheers,
 -Amenel.




 Le Dimanche 28 septembre 2014 20h36, Carl Marcum 
 a écrit :



 Hi All,

 I was checking in to a new issue opened on the netbeans plugin. [1]

 For every menu item for the AddOn in the current context (ex Writer),
 the constructor is called then the Menu is first clicked.
 If there are 2 menu items the constructor is ran twice.
 This only happens on the first time per context opened.

 Is this expected behavior?

 [1] https://issues.apache.org/ooo/show_bug.cgi?id=125691

 Thanks,
 Carl

 -
 To unsubscribe, e-mail: api-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: api-h...@openoffice.apache.org

>>>
>>> Do you remember which list the post was on?
>>>
>>> Thanks,
>>> Carl
>>>
>>>
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Concerns about the AOO community

[Jürgen Schmidt]

On 02/10/14 01:44, Rob Weir wrote:
> On Wed, Oct 1, 2014 at 4:34 PM, Alexandro Colorado  wrote:
>> On G+ I have hold a conversation with Bruce Byfield and Jos from KDE
>> about the continuation of the Apache OpenOffice community and how the
>> way that the community has enter lately into a dormant stage with very
>> little traffic.
>>
>> Althought I do seem that is an exageration, I feel that is true that
>> traffic has reach its lowest in several months. I wonder what is going
>> on with the community as well as overal adoption and concern of a lack
>> of marketing strategy.
>>
>> I would love to hear from the community managers to have an evaluation.
>>
> 
> Community mangers?  Come on, you know that is not how we roll at Apache!
> 
> What is amazing to be is how much LO sees a merger of the projects as
> a threat to them.
> 
> Here's the background.  At the LO conference one of the presenters
> spoke in favor of merging LO with AOO, of combining the efforts.  This
> was the IT Head from the Swiss Supreme Court IT office, who also said
> that they preferred to use AOO for its superior stability compared to
> LO.
> 
> https://joinup.ec.europa.eu/community/osor/news/open-and-libre-office-projects-should-reunite
> 
> As you can imagine, having a speaker at a LO conference say nice
> things about AOO and to suggest cooperation with AOO was an insult
> that could not be permitted.   So LO marketing went into over-drive to
> try to kill that message.  That's why we see articles like this, and
> recent related blog posts by Simon and Charles.
> 
> But it does make me wonder:  What are they so afraid of?  Why do they
> think the idea of cooperation so dangerous?   Why do they think that
> users are so wrong to value stability and to think that the two
> projects would work better together?

This is indeed a good question. I believe the TDF and LO community did a
really good job to setup the foundation, the community and the project.
But it is also a fact that LO benefits a lot of the things we have done
and do in AOO.

It's still a valid question why both projects doesn't cooperate better
and focus together on important improvements. From my perspective it
simply doesn't make sense and together we could reach much more.

Juergen

> 
> 
> -Rob
> 
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> 882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: create instance of XTextTable service c++

[Jürgen Schmidt]

On 02/10/14 10:21, Semen Gubarev wrote:
> Hello,
> I trying to create simple executable application for connect to OpenOffice
> 4.1.1 and create table in writer.
> I successfully create connection with OpenOffice and do some work (like
> insert texts), but I can't create a table.
> I have a problem with creation "com.sun.star.text.XTextTable" interface
> 
> some example of cpp code:
> Reference< XMultiServiceFactory > xMutiServiceFactory =
> ooConnect("uno:socket,host=localhost,port=2002;urp;
> StarOffice.ServiceManager");
> 
> Reference< XInterface > _xInterface = xMutiServiceFactory->
> createInstance(OUString::createFromAscii("com.sun.star.text.XTextTable"));
> if (!_xInterface.is()) { //here I always get false! (also I
> tring to get "com.sun.star.text.TextTable" the same truble
> return 0;
> }
> 
> what can be wrong?
> 

Do you know the Developers Guide? I recommend the DevGuide [1] as
reference and to get some basic knowledge about the API. You can also
check the SDK and the samples in the SDK. There exist Java samples that
insert a table in a text document.

The problem here is that some services are only available in the context
of a text document and that a text document have it own service factory.
The easiest way is to check the samples in the SDK.

Juergen

[1] https://wiki.openoffice.org/wiki/Documentation/DevGuide

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: create instance of XTextTable service c++

[Semen Gubarev]

Thanks for reply!
I just want to clarify this moment for other who need to create instance of
XTextTable

//... we have already connection with OpenOffice ... and we have Reference
 xDesktop instance

//read some document file
OUString sDocURL;
osl::FileBase::getFileURLFromSystemPath(OUString::createFromAscii("D:\\W\\OpenOfficeTest\\Test2\\Debug\\test.odt"),
sDocURL);
Reference< XComponent > xComponent = Reference(xDesktop,
UNO_QUERY)->loadComponentFromURL(
sDocURL,
OUString::createFromAscii("_default"),
0,
Sequence< ::com::sun::star::beans::PropertyValue>());

//and create instance of XTextTable service
Reference  xTextTable = Reference ((Reference
(xComponent,
UNO_QUERY))->createInstance(OUString::createFromAscii("com.sun.star.text.TextTable")),
UNO_QUERY);
//check is xTextTable is available
if (!xTextTable.is()) {
  return 0;
}

I just write the first time, so I do not undestand do I need to send the
example of finished code if I get success with my issue or not.

2014-10-02 14:53 GMT+06:00 Miklos Vajna :

> Hi Semen,
>
> On Thu, Oct 02, 2014 at 02:21:27PM +0600, Semen Gubarev 
> wrote:
> > I trying to create simple executable application for connect to
> OpenOffice
> > 4.1.1 and create table in writer.
> > I successfully create connection with OpenOffice and do some work (like
> > insert texts), but I can't create a table.
> > I have a problem with creation "com.sun.star.text.XTextTable" interface
> >
> > some example of cpp code:
> > Reference< XMultiServiceFactory > xMutiServiceFactory =
> > ooConnect("uno:socket,host=localhost,port=2002;urp;
> > StarOffice.ServiceManager");
> >
> > Reference< XInterface > _xInterface = xMutiServiceFactory->
> >
> createInstance(OUString::createFromAscii("com.sun.star.text.XTextTable"));
> > if (!_xInterface.is()) { //here I always get false! (also I
> > tring to get "com.sun.star.text.TextTable" the same truble
> > return 0;
> > }
> >
> > what can be wrong?
>
> com.sun.star.text.TextTable is the right form, see e.g.
>
> http://opengrok.libreoffice.org/xref/core/scripting/examples/python/pythonSamples/TableSample.py
>
> The trick is that you have to call the createInstance() method on the
> created Writer component, not on the generic xMutiServiceFactory, since
> that one has no idea in what document the table would created, so it
> doesn't create anything. ;-)
>
> Regards,
>
> Miklos
>



-- 
Best Regards
Губарев Семен

release manager for the next release

[Jürgen Schmidt]

Hi,

after a longer vacation and some silence in the past weeks I would like
to discuss the release manager role.

I think it's time that somebody else takes over this role and drives
active the next release. I did it since the beginning of OpenOffice at
Apache but I think it is a good opportunity for somebody to be more
active in the community and take over some responsibility.

We have released some important milestones over the years and have
enough experience and know what's necessary. Whoever takes over the
release manager role won't be alone and will get the support from the
community. In the same way I got it in the past.

We had discussions about the way how to communicate and track the
release planning and the progress and now it's the time that people can
realize this. It's always room for improvements.

The goal is that this somewhat important role is circulating and not
depending on one person only. The releases are anyway a community effort
and the release manager have to take care of some necessary formalism.

And to make it easier a further goal is to be able to take binary builds
from our build bots and release them. Currently we rely on builds made
by community members but I think it's better to use official build bots
for that. This means that we have to check the Windows build bot and the
binaries if they can be used already or what is missing. It means that
we need Linux build bots with the correct baseline or increase the
baseline. And finally we need a Mac build bot. But this discussion
should take place in a separate thread.

For now I would like to invite all of you to think about the release
manager role and if is something for you. I will not be available as
release manager for the next release.

Juergen

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

create instance of XTextTable service c++

[Semen Gubarev]

Hello,
I trying to create simple executable application for connect to OpenOffice
4.1.1 and create table in writer.
I successfully create connection with OpenOffice and do some work (like
insert texts), but I can't create a table.
I have a problem with creation "com.sun.star.text.XTextTable" interface

some example of cpp code:
Reference< XMultiServiceFactory > xMutiServiceFactory =
ooConnect("uno:socket,host=localhost,port=2002;urp;
StarOffice.ServiceManager");

Reference< XInterface > _xInterface = xMutiServiceFactory->
createInstance(OUString::createFromAscii("com.sun.star.text.XTextTable"));
if (!_xInterface.is()) { //here I always get false! (also I
tring to get "com.sun.star.text.TextTable" the same truble
return 0;
}

what can be wrong?