We are now looking for additional funding and projects to improve CK-related technology.
In the mean time, you can help us by improving CK documentation,
writing blog articles and making (video) tutorials about your own CK use cases,
share more CK artifacts and workflows,
unify research APIs
and provide extra tests!
We use GitHub
to develop the core CK functionality
for sharing and reusing artifacts and workflows
via third-party CK repositories
We made a special effort to stabilize CK core and avoid major changes
since 2017 (similar to Git or programming languages)
apart from adding internal tests or productivity functions requested
by the CK users
We have the following considerations in mind when developing CK and CK-based workflows:
See this wiki
about CK development conventions and testing.
Researchers can then use CK to provide a common structure to their local ad-hoc code and data,
and pack them with associated CK Python wrappers and JSON API into unified CK repositories
(a - typical ad-hoc experimental packs for Artifact Evaluation
b - unified and reusable experimental repositories such as the one for
Such repositories can be easily shared and reused via public or private services including GitHub, BitBucket and GitLab.
Please check further details at the CK GitHub documentation wiki
and practical use cases page.
Don't hesitate to reach the community via CK public mailing list.
If you are interested in long term CK plans, please contact CK authors.