Move full PyQ development to Github

[sashkab]

Historically, PyQ was developed in-house using internal source-control system and CI (we utilized Gitlab). Our CI pipeline has more than 40 jobs which are run for each push into the repository. The tests are ran using multiple versions of both 32-bit and and 64-bit kdb+ (as of 2018.02.28 we testing with kdb+ 2.8., 3.2, 3.3, 3.4, 3.5 and 3.6t). Internal CI allowed us to simplify bootstrap process and not to worry about users getting access to kdb+ binaries — only internal users have access to the system.
With Travis, we have no secure way of bootstrapping kdb+, and this is main obstacle in moving kdb+ development to Github.

TODO

1. Come up with a secure way of bootstrapping kdb+ in public CI.
2. Migrate all jobs from the internal Gitlab CI to public CI
3. Implement testing of examples in PyQ documentation (KxSystems/docs)

[abalkin]

An ideal solution for Travis CI would be to add q as a Community-Supported Language there.

[github-actions]

Stale issue message

[abalkin]

Closing because a decision has been made to continue development in the internal enlnt repository and use github only for publishing releases.