(→ISVs) |
|||
| Line 21: | Line 21: | ||
* lack of documentation (MSDN is often brought up) | * lack of documentation (MSDN is often brought up) | ||
* lack of relationship / partnership points with the community that are recognizable / make sense to them | * lack of relationship / partnership points with the community that are recognizable / make sense to them | ||
| + | * traditional tech support options | ||
The first two are out of scope of KDE itself, but we need to stress in our communications that we are involved in significant ways with both the LSB and Portland. | The first two are out of scope of KDE itself, but we need to stress in our communications that we are involved in significant ways with both the LSB and Portland. | ||
This page is a collection area for thoughts on how to construct a strategy for partnerships with independant software vendors (ISVs) and system integrators (SIs) as well as implementation notes for same. Other partners are surely on the map as well, but right now we are focussing on the ISV/SI issue.
The immediate game plan is:
As this plan is fleshed out and we achieve points one and two, the results will be taken to the MWG, e.V. and then the general community. This will allow a staged introduction with peer review at each point.
People working on this at the moment:
Contents |
The challenges we hear from ISVs tend to fall into a few common categories:
The first two are out of scope of KDE itself, but we need to stress in our communications that we are involved in significant ways with both the LSB and Portland.
The initial target SIs will be regional companies with 5-500 employees. Obviously these are not the "big boys" but they are probably more accessible targets. The goal is to raise the number of companies that provide service and support for KDE based installations.
KDE TechBase 