CK uses standard 3-clause (new) BSD license. Contributions are welcome to
either improve existing functionality or add new functionality possibly using
new modules.

Contributors should clearly mark their contributions including date and remark.

You can easily contribute to CK and all related repositories by forking them 
on GitHub and then submitting a pull request. Alternatively, you can submit
patches via collective-knowledge@googlegroups.com .

CK bugs can be reported here:
* https://github.com/ctuning/ck/issues

Bugs related to shared repositories (predictive analytics, reproducible
experimentation, autotuning, etc) should be reported via their corresponding
GitHub pages. For example, you can report bugs about autotuning here:
* https://github.com/ctuning/ck-autotuning/issues

Thank you for all your help to support this community project!

=================================================================================
Acknowledgments:

N: Grigori Fursin (alias: FGG)
E: Grigori.Fursin@cTuning.org
H: http://fursin.net
O: cTuning foundation, France
C: original concept and design
W: since Nov.1, 2014 

N: Anton Lokhmotov
E: anton@dividiti.com
H: https://www.hipeac.net/~anton
O: dividiti, UK
C: use cases, marketing
W: since Mar.1, 2015

N: Graham Markall
E: graham.markall@continuum.io
O: Continuum Analytics, UK
C: feedback on basic usage and help with Conda packaging (Anaconda scientific python distribution)
W: 

N: Alexey Kravets
E: 
H: 
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W: 

N: Sven van Haastregt
E: 
H: 
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W: 

N: Vincent Grevendonk
E: 
H: 
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W: 

N: Abdul Wahid Memon
E: engrwahidmemon@gmail.com
O: 
C: checking how to convert GCC optimization flags to CK format for autotuning
W: 

N: Valentin Dalibard
E: valentin.dalibard@cl.cam.ac.uk
O: University of Cambridge, UK
C: feedback on autotuning and run-time adaptation
W: 

N: Eiko Yoneki
E: eiko.yoneki@cl.cam.ac.uk
O: University of Cambridge, UK
C: feedback on autotuning and run-time adaptation
W: 

N: Cedric Nugteren
E: web@cedricnugteren.nl
O: The Netherlands
C: testing CK on MacOS, validating OpenCL autotuning 
W: 

N: Sergey Yakushkin
E: 
O: Synopsys
C: feedback, suggestions 
W: 

N: Lucas Nussbaum
E:
O: Universite de Lorraine, France
C: feedback on Debian packaging
W:

N: Andrei Lascu
E: andrei.lascu10@imperial.ac.uk
O: Imperial College, UK
C: including clsmith to CK (OpenCL compiler testing)
W: 

N: Alastair Donaldson
E: alastair.donaldson@imperial.ac.uk
O: Imperial College, UK
C: including clsmith to CK (OpenCL compiler testing)
W: 

N: Egor Pasko
E: 
O: Google
C: feedback on basic usage
W: 

N: Gianfranco Costamagna
E:
O: 
C: feedback on Debian packaging
W:

N: Michael Kruse
E: MichaelKruse@meinersbur.de
O: ENS Paris, France
C: evaluating CK-based gemmbench (http://github.com/dividiti/gemmbench)
   and providing feedback about autotuning and experiment reproducibility
W:

N: Chandan Reddy Gopal 
E: 
O: ENS Paris, France
C: evaluating CK for polyhedral autotuning (Pencil and PPCG from CARP project)
   and providing various feedback
W:

N: Michel Steuwer 
E: 
O: University of Edinburgh, UK
C: feedback about documentation
W:

N: Ed Plowman 
E: 
O: ARM, UK
C: CK feedback and discussions 
W:
