In the interest of full disclosure, I am a contributor to AOO, albeit one who has not been as active as I should have been in the past. Which makes me part of the problem. But that aside... Rumors of the demise of AOO are very premature. Some internal speculation aside, there's no particular reason to think the project will be shut down. Yes, the ASF board wants to see certain things happen, but none of them are thin…
>We're starting a new, more focused recruiting effort to recruit developers to the cause. Perhaps you yourself have given some thought to working on an OSS office suite? Why would I want to waste my time working on a has-been office suite when I can work on the leading FOSS office suite, which is LibreOffice? Why would I want to commit my time to a project that seems to only seems to exist because of a licensing disp…
Why would I want to waste my time working on a has-been office suite when I can work on the leading FOSS office suite, which is LibreOffice?
Because you like competition and you want to knock that "leading FOSS office suite" off its perch.
Why would I want to commit my time to a project that seems to only seems to exist because of a licensing dispute?
1. The license thing does matter, because it's easier for other projects to incorporate patches that are licensed under the ALv2. And even where that's not actually true, it is the perception. In either case, I'd posit that contributions to AOO stand to benefit everybody, whether they're using AOO, LO or something else.
2. The Apache Way. Some people will just find that they enjoy the style of collaboration that results from the way Apache projects operate. It won't be for everybody, and it's probably a minor point, but it matters to some people.
3. Everybody loves an underdog and here's your chance to be a hero. Contribute to other projects and you're "Just another person who contributed some patches". Help AOO (especially right now) and you get a chance to feel like you're really making a difference.
Why would I want to join a chronically understaffed project when I could instead join its competitor, which has far more development support?
You can probably have more impact working on AOO. There's more room to influence major technical decisions exactly because there aren't as many active developers. Want to radically re-invent how office suites work and create something truly novel? There's probably more opportunity to to that within the AOO project than others.
Why would I want to join a project which all major Linux distros have abandoned, when I could instead join its competitor, which all major Linux distros have switched to?
Meh... I don't see how that matters for anything. Why should someone else's decisions influence what you decide to work on?
I'm sorry, I haven't seen any good answers to these questions at all.
And truth be told, that's at least in part because we haven't spent a lot of time trying to come up with answers to them. We've been content to just accept that some people will want to work on AOO for their own reasons, and others will prefer to work on other projects for their reasons. We'll see if that changes in the future. I just started a thread on the AOO dev list trying to provoke some discussion around this very topic.
Working on a FOSS project that is popular and stands a chance of becoming even more popular among non-techies is laudable.
Yes, that's why we do it. :-)