Re: What would OpenOffice NON-retirement involve?

I am an a moderator for this and other AOO lists. Feel free to add me to the list of moderators. Regards Dave Original Message From: Patricia Shanahan To: dev@openoffice.apache.org Date: Fri, 2 Sep 2016 15:51:18 -0700 > Thanks. Any views on whether the archive

Office Writer Spell Check...

The Spell Check option “Ignore All” doesn’t work. Sent from Mail for Windows 10

Starting Introduction to Contributing to Apache OpenOffice Module

Hello there — Having read an article in Ars about your difficulties keeping a large group on the project, I’d like to join. It looks like you have a C++ code base, whereas my experience is primarily in C#. I have touched on and read upon C++ though. My day job is a dev in a C# base, and I’m

Re: What would OpenOffice NON-retirement involve?

I have requested creation of the mailing list, with Andrea and myself as moderators. On 9/2/2016 3:22 PM, Andrea Pescetti wrote: Patricia Shanahan wrote: If you can send me a pointer to documentation on the correct moderator tools, I can also do that. How soon can we get the list started?

Re: What would OpenOffice NON-retirement involve?

On September 3, 2016 12:38:56 AM toki wrote: >On 02/09/2016 19:06, Pedro Giffuni wrote: >>> What can Apache OpenOffice offer that related projects like > >LibreOffice cannot? > >> That is not an important question: >In terms of marketing that is the only question that is relevant. >It doesn't

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Sent from my iPhone > On Sep 2, 2016, at 5:37 PM, toki wrote: > >> On 02/09/2016 20:12, Dave Fisher wrote: >> >> I disagree with consumer vs corporate. Individuals have benefited greatly >> from all of the free projects like HTTPD, > > HTTPD is a Daemon, run for

Re: What would OpenOffice NON-retirement involve?

On 02/09/2016 19:06, Pedro Giffuni wrote: >> What can Apache OpenOffice offer that related projects like LibreOffice cannot? > That is not an important question: In terms of marketing that is the only question that is relevant. It doesn't matter if you are trying to get more developers, or

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

On 02/09/2016 20:12, Dave Fisher wrote: > I disagree with consumer vs corporate. Individuals have benefited greatly > from all of the free projects like HTTPD, HTTPD is a Daemon, run for websites --- corporate, not individuals. >tomcat, Web server. Again, corporate, not individuals. >poi

Re: What would OpenOffice NON-retirement involve?

Patricia Shanahan wrote: Any views on whether the archive should be private or public? We have no options here. Archives have to be public for this kind of lists (ASF archives are never really private, but this is another matter). Regards, Andrea.

Re: The AOO build system

On Fri, Sep 2, 2016 at 8:44 PM, Phillip Rhodes wrote: > Forgive my level of ignorance here, but I haven't been a very active > participant to this point, so there's a lot I don't know. > > In a lot of the discussion around this whole "retirement" thing (both on > the

Re: What would OpenOffice NON-retirement involve?

Jim Jagielski wrote: The issue, currently, is that the Mac OS X build requires, last I checked, an extremely old version of OSX, Xcode, et.al. No one has such a beast laying around. When did you check? And what does "extremely old" mean? OpenOffice 4.1.2 was built with a version of XCode

Re: What would OpenOffice NON-retirement involve?

Thanks. Any views on whether the archive should be private or public? Alternative volunteer for moderator? On 9/2/2016 3:22 PM, Andrea Pescetti wrote: Patricia Shanahan wrote: If you can send me a pointer to documentation on the correct moderator tools, I can also do that. How soon can we get

Re: What would OpenOffice NON-retirement involve?

Do we understand the reason for the old version of OSX etc.? On 9/2/2016 3:48 PM, Jim Jagielski wrote: The issue, currently, is that the Mac OS X build requires, last I checked, an extremely old version of OSX, Xcode, et.al. No one has such a beast laying around. I have tried creating a VMware

Re: What would OpenOffice NON-retirement involve?

The issue, currently, is that the Mac OS X build requires, last I checked, an extremely old version of OSX, Xcode, et.al. No one has such a beast laying around. I have tried creating a VMware Fusion guest but it is difficult finding all the bits and pieces. There was some discussion on

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Yes, still VERY valid! > On Sep 2, 2016, at 12:37 PM, Dave Fisher wrote: > > Hi Jim, > > I seem to recall that you made an offer to help with Mac builds. I know you > helped during incubation. Is your offer still valid? > > Regards, > Dave > > Sent from my iPhone >

Re: What would OpenOffice NON-retirement involve?

Patricia Shanahan wrote: If you can send me a pointer to documentation on the correct moderator tools, I can also do that. How soon can we get the list started? Request form is here: https://infra.apache.org/officers/mlreq and requests are usually honored within 48 hours. You'll have to

Re: What would OpenOffice NON-retirement involve?

On 9/2/2016 10:37 AM, Patricia Shanahan wrote: On 9/2/2016 10:18 AM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Friday, September 2, 2016 09:26 To: dev@openoffice.apache.org Subject: Re: What would OpenOffice NON-retirement

Re: What would OpenOffice NON-retirement involve?

Message posted on the EN forum: https://forum.openoffice.org/en/forum/viewtopic.php?f=49=84952 If you need the message to be changed, don't hesitate, I can edit it. Hagar Le 02/09/2016 à 18:25, Patricia Shanahan a écrit : On 9/2/2016 7:59 AM, Phillip Rhodes wrote: OK, counter-point to the

Re: What would OpenOffice NON-retirement involve?

Am 02.09.2016 um 16:59 schrieb Phillip Rhodes: > > What has to happen next? What is the most important thing/things we could > be > working on? What could I do *right now* to help move things in a positive > direction? > As I wrote before: If we want to recruit new developer, we need a

Re: The AOO build system

I was actually (mostly) joking about the OS/2 thing. Not that I wasn't a raving OS/2 fan up until about 2000. But for AOO, I think the answers to the other five questions are more important at the moment. Does anybody have any commentary on those topics? Thanks, Phil This message

Re: What would OpenOffice NON-retirement involve?

On Fri, Sep 2, 2016 at 3:55 PM, Marcus wrote: > > >> The bad things are: > - we need a release manager for a 4.2.0 or 4.1.3 version. > - we need hardware to get builds for Wndows, Linux and Mac. > - we need a possibility to build on Mac (buildbot or an individual >

Re: The AOO build system

Am 09/02/2016 09:24 PM, schrieb Fernando Cassia: On Fri, Sep 2, 2016 at 3:44 PM, Phillip Rhodes wrote: 6. Do we still build for OS/2? :-) (Sorry, I'm sentimental old fool). please have a look here [1] and here [2] for newer OS/2 builds that are indeed not part of

Re: What would OpenOffice NON-retirement involve?

Am 09/02/2016 04:59 PM, schrieb Phillip Rhodes: OK, counter-point to the other thread... let's talk specifically about what needs to happen next, given that some (plenty|most|all|???) of us want this project to continue moving forward. hm, I can only hope that it the *very* most of us. ;-)

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

On 02/09/2016 12:52, RA Stehmann wrote: >> being an end-user focused effort. I would suggest we focus on not >> being one, but instead being a framework or library that can be consumed >> by actual end-user implementations. > If AOO is not an end-user focused project AOo is one of the few ---

Re: What would OpenOffice NON-retirement involve?

Then you should give the project every encouragement to get the build process properly prepared. Our outgoing PMC chair should consider the same. Regards, Dave Sent from my iPhone > On Sep 2, 2016, at 12:41 PM, Marvin Humphrey wrote: > > > >> On 2016-09-02 09:43

Re: Resigning from Apache OpenOffice

This is clearly a bad day for OpenOffice. I don't like to read such mails and much less when it comes from you. I know you since our start as Apache podling and even a bit longer. So, I'm very said that you have decided to leave the project and I'm very disappointed about the reason - which

Re: What would OpenOffice NON-retirement involve?

Am 09/02/2016 06:25 PM, schrieb Patricia Shanahan: On 9/2/2016 7:59 AM, Phillip Rhodes wrote: OK, counter-point to the other thread... let's talk specifically about what needs to happen next, given that some (plenty|most|all|???) of us want this project to continue moving forward. What has to

Re: What would OpenOffice NON-retirement involve?

On 2016-09-02 09:43 (-0700), Pedro Giffuni wrote: > At this time I am unsure what the Board wants from the project. My primary concern as a Board member is that the project respond promptly and effectively to security reports. Marvin Humphrey

Re: What would OpenOffice NON-retirement involve?

Hi - Awesome. These are the kinds of questions that should energize the project. Base is a problem, but there are many Java bridges that can be plugged if we open up the configuration. Regards, Dave Sent from my iPhone On Sep 2, 2016, at 11:40 AM, Phillip Rhodes

Re: What would OpenOffice NON-retirement involve?

On 02/09/2016 17:21, Phillip Rhodes wrote: >> a Mac Mini with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. > Is such a machine sufficiently powerful for building AOO, Yes. >and doing so in a reasonable period of time? That depends upon what the user considers "reasonable". For

Re: What would OpenOffice NON-retirement involve?

> If you excuse the comment from an outsider, I suggest the question you > need to answer is: What can Apache OpenOffice offer that related > projects like LibreOffice cannot? > That's a good question. The one obvious thing, which matters to some people, but not others, is "be licensed under the

Re: What would OpenOffice NON-retirement involve?

On September 2, 2016 10:59:55 AM Phillip Rhodes wrote: >OK, counter-point to the other thread... let's talk specifically about >what needs to happen next, given that some (plenty|most|all|???) of us >want this project to >continue moving forward. > >What has to happen next? What is the most

Re: What would OpenOffice NON-retirement involve?

On 9/2/16 12:25 PM, Patricia Shanahan wrote: > On 9/2/2016 7:59 AM, Phillip Rhodes wrote: >> OK, counter-point to the other thread... let's talk specifically about what >> needs to happen next, given that some (plenty|most|all|???) of us want this >> project to >> continue moving forward. >> >>

Re: What would OpenOffice NON-retirement involve?

Doing some reading, it looks like it may indeed be possible to run OS X on VirtualBox at least under Windows (not sure about Linux). If so, I might be willing to spend some money on an EC2 instance to do Mac builds, especially if it doesn't need to be up 24x7. Question: Does the ASF have any

Re: What would OpenOffice NON-retirement involve?

On 9/2/2016 10:18 AM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Friday, September 2, 2016 09:26 To: dev@openoffice.apache.org Subject: Re: What would OpenOffice NON-retirement involve? On 9/2/2016 7:59 AM, Phillip Rhodes wrote:

Re: What would OpenOffice NON-retirement involve?

I understand your problem. Until now, I have only owned one Apple desktop, the Apple II I bought in 1980. I took a dislike to Macs the first time I tried one. On 9/2/2016 10:32 AM, Phillip Rhodes wrote: No doubt. My problem on this is that I hate Apple, Macintosh, and everything to do with

Re: What would OpenOffice NON-retirement involve?

No doubt. My problem on this is that I hate Apple, Macintosh, and everything to do with their proprietary, closed-source, walled-garden ecosystem. I could possibly pinch my nose shut and buy a cheap Mac to help with AOO development, but there's a limit to how much I'd be willing to spend. Phil

Re: What would OpenOffice NON-retirement involve?

On 9/2/2016 10:21 AM, Phillip Rhodes wrote: On Fri, Sep 2, 2016 at 1:18 PM, Patricia Shanahan wrote: Looking at it the other way round, for under $500 I could have a Mac Mini with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That is less than 10 months of

Re: What would OpenOffice NON-retirement involve?

On Fri, Sep 2, 2016 at 1:18 PM, Patricia Shanahan wrote: > Looking at it the other way round, for under $500 I could have a Mac Mini > with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That is less > than 10 months of macincloud. Is such a machine sufficiently

Re: What would OpenOffice NON-retirement involve?

Looking at it the other way round, for under $500 I could have a Mac Mini with 500 GB hard disk and Mac OS Yosemite delivered on Sunday. That is less than 10 months of macincloud. On 9/2/2016 10:11 AM, Phillip Rhodes wrote: That's unfortunate. And Apple doesn't allow running OSX under a VM

RE: What would OpenOffice NON-retirement involve?

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Friday, September 2, 2016 09:26 > To: dev@openoffice.apache.org > Subject: Re: What would OpenOffice NON-retirement involve? > > On 9/2/2016 7:59 AM, Phillip Rhodes wrote: > > OK, counter-point to the other

Re: What would OpenOffice NON-retirement involve?

On 9/2/2016 10:09 AM, Patricia Shanahan wrote: I looked at some of those services a few weeks ago. For the ones I found, the relatively inexpensive options did not have the capability of building software, let alone the capacity for build a substantial body of software. The options with the

Re: What would OpenOffice NON-retirement involve?

That's unfortunate. And Apple doesn't allow running OSX under a VM on another OS do they? Phil This message optimized for indexing by NSA PRISM On Fri, Sep 2, 2016 at 1:09 PM, Patricia Shanahan wrote: > I looked at some of those services a few weeks ago. For the ones I >

Re: What would OpenOffice NON-retirement involve?

I looked at some of those services a few weeks ago. For the ones I found, the relatively inexpensive options did not have the capability of building software, let alone the capacity for build a substantial body of software. The options with the capability and capacity would cost more than a Mac

Re: What would OpenOffice NON-retirement involve?

Sadly, I don't own a Mac. I use one at work, but all of my personal hardware is PC based, running Linux. I wonder if it would work to use something like this: http://www.macincloud.com/ Anybody have any experience with something like that? Phil This message optimized for indexing by NSA

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Hi Jim, I seem to recall that you made an offer to help with Mac builds. I know you helped during incubation. Is your offer still valid? Regards, Dave Sent from my iPhone > On Sep 2, 2016, at 6:59 AM, Jim Jagielski wrote: > > >>> On Sep 2, 2016, at 9:48 AM, Jörg Schmidt

Re: What would OpenOffice NON-retirement involve?

Hello; At this time I am unsure what the Board wants from the project. They probably want to see more activity and may recur to artificial numbers like number of commits, number of active developers, or releases. I very much doubt actions from the Board will solve anything, it's the PMC and

Re: What would OpenOffice NON-retirement involve?

Really? Substantial work is done on list to improve the build process for Windows and you don't think about mentioning that? Someone who has a Mac and time could help with that build! Regards, Dave Sent from my iPhone > On Sep 2, 2016, at 9:05 AM, Dennis E. Hamilton

Re: What would OpenOffice NON-retirement involve?

On 9/2/2016 7:59 AM, Phillip Rhodes wrote: OK, counter-point to the other thread... let's talk specifically about what needs to happen next, given that some (plenty|most|all|???) of us want this project to continue moving forward. What has to happen next? What is the most important

Re: What would OpenOffice NON-retirement involve?

On 02/09/2016 14:59, Phillip Rhodes wrote: > What is the most important thing/things we could be working on? On your own hardware: Repeat: Build a Mac OS X Binary; Fix the error messages you get; Write notes about what you did; Test the program functionality; Until it builds

RE: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

> -Original Message- > From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] > Sent: Thursday, September 1, 2016 22:08 > To: dev@openoffice.apache.org > Subject: RE: [DISCUSS] What Would OpenOffice Retirement Involve? (long) > > > > > -Original Message- > > From: Phillip

RE: What would OpenOffice NON-retirement involve?

We all have these questions, Phil. What we are awaiting is someone to provide an actionable answer. There is nothing to do about the FUD (as is already remarked elsewhere on the What would ... thread). That's a waste of energy. What we need is energy put into having an AOO that serves its

RE: Release Manager for 4.2.0?

I don't have a good place to put this, and 4.2.0 may not be the way to consider it, if we are also counting on an early (this year) 4.2.0 to also provide important maintenance fixes and any security catch-ups too. One major change that the TDF made to LibreOffice is very important. Instead of

RE: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Also, . The article itself is very straightforward. The comments wander around all over the place with the usual pontifications about corporate influence, etc. An important point is made, by the way, over how it is that LibreOffice deployment is far easier

What would OpenOffice NON-retirement involve?

OK, counter-point to the other thread... let's talk specifically about what needs to happen next, given that some (plenty|most|all|???) of us want this project to continue moving forward. What has to happen next? What is the most important thing/things we could be working on? What could I do

Re: Resigning from Apache OpenOffice

On Sep 2, 2016 4:03 PM, "Andrea Pescetti" wrote: > > Kay Schenk wrote: >> >> I'm resigning from Apache OpenOffice. > > > Seeing your enthusiasm until yesterday, I think I can easily guess the reason. Rest assured, I am feeling bullied too. > > So, what can we, the people who

Re: Resigning from Apache OpenOffice

Kay Schenk wrote: I'm resigning from Apache OpenOffice. Seeing your enthusiasm until yesterday, I think I can easily guess the reason. Rest assured, I am feeling bullied too. So, what can we, the people who actively work (as volunteers) on OpenOffice, and who plan releases, and who have

Re: Resigning from Apache OpenOffice

Am 02.09.2016 um 15:43 schrieb Kay Schenk: > I'm resigning from Apache OpenOffice. I've been an unpaid volunteer with > OpenOffice.org and Apache OpenOffice since April, 2001. At this point, I'm > thinking it's time to move on. > . > Thank you very much for your great work. And good luck for the

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

> On Sep 2, 2016, at 9:48 AM, Jörg Schmidt wrote: > >> From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > >> Patricia, we are still discussing. We are balancing reasons, >> advantages >> and disadvantages, for different solutions. There is no

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

> From: Roberto Galoppini [mailto:roberto.galopp...@gmail.com] > We are on the same page here, and if security issues (real > ones) would be > left uncovered it would be fine if you and/or the board will step in. > > In the meanwhile PLEASE let us work, and let's see if we can > keep changing

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

This whole discussion is a chance to "prove me wrong" (as someone "out of touch") as well as to prove to the entire OO community what those "positive things" are. I am glad that the status-quo of today != the status-quo as of (today - 3weeksAgo). I am reminded of this scene from Pulp Fiction

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

> From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > Patricia, we are still discussing. We are balancing reasons, > advantages > and disadvantages, for different solutions. There is no decision made. > > And more and more I believe, it was a good idea to start that >

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

On Sep 2, 2016 3:29 PM, "Jim Jagielski" wrote: > > Yes, I would assume that many existing people would leave. > > But, as I mentioned, I would assume (hope) that many people > would join, and many of those would be from others in the > entire OO eco-system. > > Your reply seems

Resigning from Apache OpenOffice

I'm resigning from Apache OpenOffice. I've been an unpaid volunteer with OpenOffice.org and Apache OpenOffice since April, 2001. At this point, I'm thinking it's time to move on. A big THANK YOU to all the developers that made OpenOffice the outstanding open source product it is today. THANK

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Am 02.09.2016 um 15:08 schrieb Patricia Shanahan: > > This discussion has a serious self fulfilling prophecy downside. The > less ASF's commitment to AOO, the less my commitment is. I had been > thinking of buying a Mac and learning to do builds on it. That is an > investment of time, energy,

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

BTW, can we drop private@ on this and simply continue the discussion on dev@? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Yes, I would assume that many existing people would leave. But, as I mentioned, I would assume (hope) that many people would join, and many of those would be from others in the entire OO eco-system. Your reply seems to suggest that with the current status of AOO, maintaining an end-user focus is

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

On 9/2/2016 5:52 AM, RA Stehmann wrote: Am 02.09.2016 um 14:14 schrieb Jim Jagielski: What is obvious is that the AOO project cannot support, at the present time, being an end-user focused effort. I would suggest we focus on not being one, but instead being a framework or library that can be

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

> From: Jim Jagielski [mailto:j...@jagunet.com] > Secondly, as alluded to above, we should prepare ourselves > for the FUD, > the "AOO is dead" victory chants, the numerous anti-AOO and > anti-Apache > spewings, etc... There are some who will use this as a self-serving > soapboxing

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Dennis, thanks for opening up this conversation. As noted over the last few months, it has become obvious to the board that AOO has not been a healthy project for some time. Again, there are many, many reasons for this, and it doesn't help to go into them here and now. The simple fact is that we

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Hello, our discussion became public: http://www.linux-magazin.de/content/view/full/106599 This shows a public interest. So "going public" seems not to difficult. Kind regards Michael signature.asc Description: OpenPGP digital signature

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Quick top note: to avoid multiple mails I'll comment this and the others messages here. First, I totally agree with Andrea, let's focus on what needs to be done, it's inappropriate at best to discuss anything related to the shutdown at this time. Yet if someone enjoys the exercise of style that's

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Hello, > From: Dr. Michael Stehmann [mailto:anw...@rechtsanwalt-stehmann.de] > the situation as I see it (I am no developer) is, that we need > "developers, developers, developers, developers ... ". > [...] This is not wrong, but ... Developers will participate primarily in projects which

Re: [DISCUSS] What Would OpenOffice Retirement Involve? (long)

Dennis E. Hamilton wrote: One option for remedy that must be considered is retirement of the project. ... There are those who fear that discussing retirement can become a self-fulfilling prophecy. This is becoming too much. There are other options. Namely, a new release will invalidate the