I assume everyone received the email (below) from Jeff Stanier this morning regarding LCCS being shut down for good at the end of the year. My question is what everyone is doing in the face of this news?
We've built a large part of our company on LCCS and are scrambling for a solution that we can implement to replace LCCS before the end of the year. There was no transition plan or any details at all given in the email.
Any other LCCS users discussing transition plans? Is there any opportunity for us to collaborate so that those of us dependent on LCCS aren't totally left in the cold?
Dear LCCS Customer,
I am writing to inform you of Adobe‚s plan with respect to LiveCycle Collaboration Services (LCCS). Due to recent changes in Adobe‚s strategic direction the decision has been made to end of life the LCCS product. Adobe will continue to provide LCCS production service for an additional 9 months until December 31, 2012. At that time the service will be shut down. Beginning March 23, 2012 the following changes will be made to the service:
In order to support your continued patronage while we ramp down the service, Pay Per Usage (PPU) accounts will no longer be charged and a free account quota of $1000/month will be granted. As a result of this change, monthly billing statements will no longer be issued.
Free subscribers will no longer be able to upgrade to a PPU account.
No new accounts will be created.
We apologize for any inconvenience the termination of the service causes you. Thank you for being an Adobe LiveCycle Collaboration Services customer.
Jeff Stanier Group Product Manager Adobe LiveCycle
Again, I realize you're just the messenger, so I bear no animosity towards you, but this decision by Adobe and the way it's being handled (again) makes absolutely no sense to me.
If the user provisioning and billing is the only major aspect which is holding up releasing this technology to Spoon (if indeed that is the case), then why do we have to assume that the "partner" taking over this tech has to make any money off it? Why could a company not use this to install on their own servers, much like FMS? Why assume that a hosting provider has to be involved? The tech could be released to Spoon with the understanding that certain aspects, previously tied into Adobe billing backend, will only work once the community rearchitects them to work with an open source version. LCCS as it's given over to the community would be "broken," as it were, but only for as long as it takes for the community to redesign those missing aspects, assuming they are merely administrative backend aspects and not a part of the core technology.
And if some of the aspects of the tech are the same as what are in other current Adobe offereings, why does LCCS have to come in a complete package? Would it not be possible to "license" the NDA aspects of the tech to Spoon or another "angel partner" (for free, since you're letting it go anyways), and liberate the rest of LCCS to spoon?
C'mon Adobe (and I don't mean you Jeff), you can't have it both ways: you all but admitted that after all this time you still have not figured out how to monetize your own technologies, so you're gradually giving them away. Well, then give them away already, and stop holding the rest of us hostage. Please.