Open source Invoicing psi-Planning for the UI

This topic is caused by the PSI Open source protocol, and I use this article to talk about my plan for the PSI UI.

1, because at present I am an individual, has not registered the company, therefore buys ExtJS the commercial license aspect, has many troublesome things.

2, PSI is a commercial project, but the business model has code open source. Therefore, after the establishment of the company, will buy ExtJS business license, thereby resolving the official PSI products

The issue of ExtJS distribution.

If this is the case, then of course there is no planning. Here, let's imagine.

1, for enterprise applications, I understand the importance of the UI framework. Therefore, the development of a set of its own framework, of course, is necessary.

2. The most natural evolutionary path is the purchase of ExtJS's commercial license and the development of a derivative version of the derivative version of open source as Apache license.

The derivative products here naturally include the optimization and downsizing of the PSI.

The development of derivative products, this aspect ExtJS company may not be allowed, so there will certainly be a difficult business negotiation process.

So, here is the core idea to solve this problem is business ideas, not from the technical point of view to solve.

(Frankly speaking, business ideas = = Money can solve the problem, is not a problem)

To get to this point, the PSI itself has a pretty good financial support. Before financial support is reached, it must be on the brink of law.

The ideal is to have, in case the realization of it?

Open source Invoicing psi-Planning for the UI