Fixed an issue which could lead to an apphook without a slug Fixed numerous frontend issues Added contribution policies documentation Corrected an issue where someone could see and use the internal placeholder CMS come from across the world, and have a wide range and levels of skills and expertise. Every contribution, however small, is valued. As an open source project, anyone is welcome to contribute in whatever documentation, and testing the Contribute to django CMS How to contribute Development policies Guidelines for django CMS projects Code and project management Running and writing tests Code of Conduct

Fixed an issue which could lead to an apphook without a slug Fixed numerous frontend issues Added contribution policies documentation Corrected an issue where someone could see and use the internal placeholder CMS come from across the world, and have a wide range and levels of skills and expertise. Every contribution, however small, is valued. As an open source project, anyone is welcome to contribute in whatever documentation, and testing the Contribute to django CMS How to contribute Development policies Guidelines for django CMS projects Code and project management Running and writing tests Code of Conduct

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/divio/django-cms] GitHub repository to your own GitHub account 2. Clone your mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/divio/django-cms] GitHub repository to your own GitHub account 2. Clone your mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/divio/django-cms] GitHub repository to your own GitHub account 2. Clone your mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/divio/django-cms] GitHub repository to your own GitHub account 2. Clone your mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/django-cms/django-cms] GitHub repository to your own GitHub account 2. Clone your mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

to be aware of the guidelines and policies for django CMS project development. Adhering to them will make much easier for the core developers to validate and accept your contribution. The basics The basic basic workflow for a code contribution will typically run as follows: 1. Fork the django CMS project [https://github.com/divio/django-cms] GitHub repository to your own GitHub account 2. Clone your fork mix of unit tests, functional tests, regression tests and integration tests. Depending on your contribution, you will write a mix of them. Let’s start with something simple. We’ll assume you have set up

4. Running Tests 5. Debugging Kyuubi 6. Developer Tools Community 1. Collaborators 2. Contribution Guidelines 3. Kyuubi Project Improvement Proposals (KPIP) 4. Kyuubi Release Guide 5. Community Appendix --replace to update dev/dependencyList in your Pull request. Community 1. Collaborators 2. Contribution Guidelines 2.1. Prepare github environment 2.2. Creating a Pull Request 3. Kyuubi Project Improvement at contributors [https://github.com/apache/incubator- kyuubi/graphs/contributors]. 2. Contribution Guidelines Kyuubi is an Apache License v2.0 [https://github.com/apache/incubator- kyuubi/blob/master/LICENSE]

4. Running Tests 5. Debugging Kyuubi 6. Developer Tools Community 1. Collaborators 2. Contribution Guidelines 3. Kyuubi Project Improvement Proposals (KPIP) 4. Kyuubi Release Guide 5. Community Appendix --replace to update dev/dependencyList in your Pull request. Community 1. Collaborators 2. Contribution Guidelines 2.1. Prepare github environment 2.2. Creating a Pull Request 3. Kyuubi Project Improvement at contributors [https://github.com/apache/incubator- kyuubi/graphs/contributors]. 2. Contribution Guidelines Kyuubi is an Apache License v2.0 [https://github.com/apache/incubator- kyuubi/blob/master/LICENSE]