Please use this Linux forum for providing COMMUNITY BASED SELF-SUPPORT for problems you have with the LightZone for Linux BETA Release.
As Grant has pointed out, at this time, the release is currently in Beta, and that means that Light Crafts cannot commit to responding to nor resolving technical problems that are reported to us during the Beta period. On the other hand, we are terribly curious to discover what problems are being found, and we will attempt to address them on a best effort basis while also trying to make timely progress to a commercial release candidate. Chances are that if the problem is inside the LZ codebase and it isn't reported, then it probably will remain unfixed. So it definitely benefits us all if these problems are reported, as long as we all have reasonable and common expectations about how such reports will (and will not) be handled.
Issues the Light Crafts Product Release team hopes to determine during the Beta period
Obviously, we want to know if (and when) the current release is ready for commercial release. It has been many months since the last LightZone for Linux release was shipped, and there are several new enhancements in this version which have never been subjected to testing on Linux outside of our engineering lab and alpha test team. Because much of our code is platform independent, we are very hopeful that this testing will go quickly and verify our belief that LightZone for Linux is robust enough for a commercial release.
But while much of the LightZone application code is shared, there are Operating System specific dependencies that may be a significant source of difficult to resolve problems (because the root of those problems may lie within code that is written and maintained by the Operating System (OS) vendor, or by the Java Runtime Environment (JRE) supplier). In fact Light Crafts may be totally dependent upon the OS or JRE vendor to quickly resolve such problems.
So, part of what the Light Crafts product release team need to assess during the Beta test is how many Linux specific installation, configuration and OS or JRE bugs our LightZone for Linux users are likely to encounter.
I want to be very transparent with all our active Linux users about the challenges we face moving from Beta release to commercial availability; because you are in the greatest position to influence how we resolve these problems.
As you all know, there is a huge diversity in Linux platforms, versions, and configurations. This makes it extremely challenging for Light Crafts to QA and validate against so many permutations. It also makes it difficult for us reproduce or fix platform or configuration specific problems, and could require us to have a large dedicated Linux support team to cover all the possibilities -- or even a reasonable subset of the major ones.
In short, there is a very real risk of substantially greater support costs for Linux than for Mac and Windows (if Light Crafts has to maintain all that Linux experience internally). At the same time because of the smaller overall market size of Linux GUI desktop/Laptop vs. Windows and Mac markets we have reason to be concerned that LightZone for Linux revenues will not be sufficient to cover these additional Linux specific costs.
Your help is needed!
As 2.4 Linux users recall, concerns about these problems led to the withdrawal of a Linux product once before. I'd like things to be different this time. So while there are lots of things we MIGHT expect will happen concerning the cost of Linux support and potential revenue, I am looking to use the Beta period to get some evidence of what is LIKELY to happen if we move to commercial release.
If the LZ for Linux community itself is willing and able to assist new LightZone for Linux users with resolving *Linux specific* installation/configuration/version/platform problems, and Light Crafts' Technical Support Team only needs to focus on LightZone platform independent issues, then I can see that it might be very reasonable for us to offer a commercial version for even to a fairly small Linux customer base.
But such a release would be based around a shared support paradigm -- with Technical Support for platform independent LightZone issues provided by the company, and Linux specific support provided by the community itself via the Linux forum.
Obviously, sharing support responsibilities this way benefits Light Crafts, and relies on the good will, hard work and commitment of our Linux community to do their part. I believe that such a pact between Light Crafts and its Linux users also benefits Linux users, and recognizes the faith, effort and commitment of Light Crafts to the Linux Community as well. I like to think of it as a kind of mutual defense pact. But as with all such agreements it is not written terms of the agreement which matter -- it is in the voluntary observance of such agreements by both parties that we measure whether they work or whether they fail.
I love Linux and the Linux community and I want to make sure we do our part to facilitate the creation of such a vendor-customer base partnership.
I am very curious to see (and hopeful about) whether robust community based Linux self-support will develop naturally, thus enabling us to swiftly offer a commercial Linux product.




Reply With Quote

