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.
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.
There is obvious appeal to SAs and companies built around their professional services given the information on the wiki. There is overlap here with SIs, but it may be worthwhile to look at the implications unique to SAs.
The SMP relies on parties with vested interests in KDE. While there are many such entities today, this partner program will be used to widen the top of the prospects funnel by creating vested interests and identifying existing ones. It should be a natural consequence for those most involved with this program will become interested over time in the SMP.
In one sense, this program and the SMP work in opposite directions: this program gives information and interface to the outside world and the SMP is a means for the beneficiaries of the program to give back to KDE.