The Skooppa Software Doctrine

Posted By on Apr 4, 2015

Skooppa will be a Javascript web application development platform first and this doctrine is created mainly for developers, who make ideas come to life.


As a platform, we must make some opinionated decisions and have limits about what should be done and how. However, quality, with as much flexibility and agility as possible, will always be a core concept of the system. At the end of the day, you will create your or your client’s ideas faster, built on a system that can grow with those ideas, without any worries.

Those ideas are what we call “applications” or “extensions”.

Although applications and extensions can be so unique, that you or your clients may want to keep them for yourselves and only offer the services they represent to end users, you might also want to “pre-build” applications as developers, to give or even support. We expect all kinds of pre-built applications to bubble up and out of Skooppa.

Whatever developed applications or extensions you decide to offer, we must find a common ground, so that all sides, us – the platform developers, you – the application developers and the fantastic users (the real reason why we are all doing all this), are fairly treated.

This doctrine is a set of rules, which will be followed and will constantly evolve throughout Skooppa’s existence. It forms a basic understanding of what software is all about on Skooppa and what the rewards for creating and using it can be within Skooppa. It also represents the core thinking of cloud computing, which is, “Pay for what you use!”


The Skooppa Software Doctrine

  1. An application is software that represents a number of features, which form a number of workflows and must use a number of data objects.
  2. An extension represents one or more additional features to an application or to the platform itself. It may or may not have workflows or use data objects.
  3. Applications can be given to users for free. If an application is free, it is free in the sense of open source software (OSS). It is up to you, as the developer, to decide which OSS license type to use. It should just fit in with a SaaS model. We suggest the MIT license.
  4. All extensions for applications or for the Skooppa platform must be free and open source. The same OS license choice applies, as in point 3.
  5. OSS based applications and extensions can also have technical support. This support can also be commercial.
  6. Applications can also be commercial. These applications are called “Supported Commercial Applications”. These applications can have closed source code. For the purpose of extension creations and the applications popularity, we suggest to leave the code open. Skooppa will make the choice available.
  7. Supported Commercial Applications will be “locked” source code. No direct changes can be made to the software by site owners.
  8. Continually developed or technically supported OSS applications and extensions are called “Supported Applications” or “Supported Extensions”. The can be locked source code. This is an option.
  9. OSS based applications and extensions are called “Unsupported Applications” or “Unsupported Extensions”. The source code is never locked and is “use at your own risk” for site owners.
  10. All applications and extensions will be offered on Skooppa’s own central marketing platform. Currently (see revision date below), the plan is to call this marketing platform “SkooppaCode”. In order to support that platform, Skooppa will be taking part of the revenues earned from supported applications. The amount is TBA. Currently the plan is 30%.
  11. Any developer wishing to develop on Skooppa must enter the Skooppa Developer Program. The cost for this program is $64 yearly. This will entitle the developer to a complete Skooppa instance for development (some limits on usage will apply*). Should the developer wish to market his or her developed application on Skooppa with a Skooppa site, the developer is then a normal customers of Skooppa for that site. A developer may market and technically support an application on her own site/ server.
  12. The price for supported applications is based on user license types, which are based on the Skooppa platform user license types. The number of licenses is determined by the user and will be equal to or less than the number of platform licenses available.
  13. Any services created and offered to end users are the full responsibility of the site owners, the operators of the software, and all commercial activity on them belongs to them within that realm of responsibility. Any discrepancies between the end user and the site owner, must be dealt with by the site owner.
  14. Discrepancies between developers and site owners about the software will be dealt with by the developer.
  15. Discrepancies between Skooppa and the developer about the development platform services will be dealt with by Skooppa.
  16. Discrepancies between Skooppa and the site owners about the platform website services will be dealt with by Skooppa.
  17. Just like with Skooppa licenses, there are two types of licenses for supported commercial applications. Admin and Staff licenses.
  18. Staff licenses are always the less costly licenses. Admin licenses must always offer more functionality and control.
  19. Technical support costs must never be part of the license price and thus, if offered, must be an additional service. If you offer a supported commercial application, you must also offer technical support for that application. The level of support and whether or not the customer must pay for it, is up to the developer.
  20. If at any point, a supported commercial application will be no longer be supported, either in development or with technical support, then the software must be changed to open source and will be free of charge. As open source, it can however, be technically supported and further developed by other developers. The software, after that point, will stay open source.
  21. Looks and feels offered on Skooppa also fall under the term “application”, and thus the same rules apply.
  22. The developer must inform Skooppa within 90 days of any ending of either types of support for any types of applications or extensions.
  23. And lastly, as is the standard and highest rule for Skooppa….. always have fun!
    (Rev. 1 – Last Update 04.04.2015)
*According to the Skooppa developer program rules (TBA).

If you have any comments or suggestions or critique to this doctrine, please let us know in our project forum.

Article Name
The Skooppa Software Doctrine
This doctrine describes the grounds for working with software on Skooppa.