![lotus symphony not responding lotus symphony not responding](https://image.slidesharecdn.com/ibmmessagingandcollaboration-notesdominoroadmapdec2012-121214100437-phpapp02/95/ibm-messaging-and-collaboration-roadmap-notes-and-domino-update-december-2012-20-638.jpg)
- #Lotus symphony not responding install
- #Lotus symphony not responding software
- #Lotus symphony not responding code
- #Lotus symphony not responding license
To be fair to IBM, I'm not sure it was "purely political". I know that we'll be adding more developers to the Apache project, so you might want to spin the FUD in exactly the opposite direction, especially if you want to keep a few steps ahead of reality. But that didn't turn out to be true either.Īnd then now, when we end the fork and contribute the Symphony code, what is the new conspiracy theory? That we're trying to get others to develop Symphony for us? Really? Is that the best you can think of? Take a few more days and think it over. We were going to dominate and control the project. Then, after IBM put in a bunch of developers to work on Apache OpenOffice, the conspiracy theory changed from IBM not doing anything, to IBM was to do much.
#Lotus symphony not responding code
They heory was that IBM would not contribute any code or developers.
![lotus symphony not responding lotus symphony not responding](https://cdn.ghacks.net/wp-content/uploads/2009/10/symphony_desktop.png)
When Apache OpenOffice first started, the theory was that IBM wanted to suck in free OpenOffice code so we could integrate that with our proprietary Symphony. So your argument fails to really get started.īut I'm still trying to grok your conspiracy theory. > This ends the Symphony fork here with Apache OpenOffice.Īnd many (most in fact) of the Apache OpenOffice folks used to be people. > contribution and help determine how best to use it going forward for the > the community will invest time and energy to study and understand this > of Apache OpenOffice 3.4 has now made it possible to move forward. > We announced our plan to do this on July 15, 2011. > This is just a short announcement to get the ball rolling. > descriptive content to the list tomorrow when our China team wakes up. > 'Contribution" into svn when they're ready. This action means infra can begin to prepare to receive the
#Lotus symphony not responding license
> Corporate Contributor License Agreement for IBM Lotus Symphony
#Lotus symphony not responding software
> A few minutes ago, I submitted the IBM Software Grant Agreement and On Tue, at 4:19 PM, Donald Harbison wrote: We have our ideas, but recognize that we are allĮqual in the project and are dedicated to working in the Apache Way. How we get to this goal will depend on all of us IBM willĬontinue to maintain and support Symphony for our customers until we areĪble to offer Apache OpenOffice with what we hope will be most of the value We hope everyone is as excited about this contribution as we are. Globalization, and last but not least, accessibility support. There is excellent work in Microsoft Office file format support, Productivity, performance and stability of Apache OpenOffice. Rich set of features with the potential to significantly improve user We invite you to think about this code as providing a In order to help everyone better understand the value of Symphony, we are It's something we've looked forward to doing This is going to be a lot ofįun and a lot of hard work. With the best developers who have mastered it. This is about envisioning a futureįor Apache OpenOffice that builds on the best code we can offer together Our grant with the the Apache Software Foundation and initiate this new The successful delivery of Apache OpenOffice 3.4 has enabled us to finalize Only be dealing with the source code, not the binaries.
#Lotus symphony not responding install
Install sets is dependent only on the IBM Beijing team. The availability of the standalone Symphony The IBM team responsible for the Lotus Symphony product is pleased toĪnnounce that the Symphony source code for Windows, Linux and Mac will beĪvailable as soon as our intrepid Infra team can accommodate this largeĬontribution in svn here at Apache. Re: IBM SGA/CCLA Submitted for Symphony Source Code Contribution