Dictator and Lieutenants Workflow Patterns for Managing Source Code Branches Workflows Summary Contributing to a Project Commit Guidelines Private Small Team Private Managed Team Forked Public Project Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking Projects The GitHub Flow Advanced Pull Requests GitHub Flavored Markdown Adding Collaborators Managing Pull Requests Mentions and Notifications Special Files README CONTRIBUTING Project Administration Managing an organization Organization Basics Teams Audit Log Scripting

Dictator and Lieutenants Workflow Patterns for Managing Source Code Branches Workflows Summary Contributing to a Project Commit Guidelines Private Small Team Private Managed Team Forked Public Project Setup and Configuration SSH Access Your Avatar Your Email Addresses Two Factor Authentication Contributing to a Project Forking Projects The GitHub Flow Advanced Pull Requests GitHub Flavored Markdown Adding Collaborators Managing Pull Requests Mentions and Notifications Special Files README CONTRIBUTING Project Administration Managing an organization Organization Basics Teams Audit Log Scripting

让你的 GitHub 公共仓库保持更新 维护项目 创建新的版本库 添加合作者 管理合并请求 提醒和通知 通知页面 网页通知 邮件通知 特殊文件 README 贡献 CONTRIBUTING 项目管理 管理组织 组织的基本知识 团队 审计日志 脚本 GitHub 服务与钩子 GitHub API 基本用途 在一个问题上评论 修改 Pull Request 数；如果参数是目录的路径，该命令将递归地跟踪该目录下的所有文件。 暂存已修改的文件 现 在 我 们 来 修 改 一 个 已 被 跟 踪 的 文 件 。 如 果 你 修 改 了 一 个 名 为 CONTRIBUTING.md 的已被跟踪的文件，然后运行 git status 命令，会看到下 面内容： $ git status On branch master Your branch is up-to-date "git checkout -- ..." to discard changes in working directory) modified: CONTRIBUTING.md 文件 CONTRIBUTING.md 出现在 Changes not staged for commit 这行下面，说 明已跟踪文件的内容发生了变化，但还没有放到暂存区。 要暂存这次更新， 需要运行

Improvements and new features Added code of conduct reference file to the root directory Moved contributing file to the root directory Added better templates for new issue requests Mark public static placeholder JavaScript and SASS. We no longer use develop.py; we now use manage.py for all development tasks. See Contributing a patch for examples. We’ve moved our widgets.py JavaScript to static/cms/js/widgets. Code formatting formatting We’ve switched from tabs (in some places) to four spaces everywhere. See Contributing code for more on formatting. gulp.js We now use gulp.js for linting, compressing and bundling of frontend

Improvements and new features Added code of conduct reference file to the root directory Moved contributing file to the root directory Added better templates for new issue requests Mark public static placeholder JavaScript and SASS. We no longer use develop.py; we now use manage.py for all development tasks. See contributing_patch for examples. We’ve moved our widgets.py JavaScript to static/cms/js/widgets. Code formatting formatting We’ve switched from tabs (in some places) to four spaces everywhere. See Contributing code for more on formatting. gulp.js We now use gulp.js for linting, compressing and bundling of frontend files

Frontend editing for Page and Django models Sitemap Guide Page Types Content creation wizards Contributing a patch Key topics Using touch-screen devices with django CMS How the menu system works Publishing Development & community django CMS’s development community Development policies Contributing code Contributing documentation Contributing translations Code and project management Running and writing tests Code Page Types Selecting a Page Type Content creation wizards Create a content-creation wizard Contributing a patch The basics How to write a test Submitting your code Installing django CMS by hand This

Search and the Django-CMS 6.1. Haystack Contributing to the CMS 1. Contributing to Django-CMS 1.1. Community 1.2. In a nutshell 1.3. Contributing Code 1.4. Contributing Documentation 1.5. Translations Indices Lauber. Created using Sphinx 1.3.5. previous | modules | index django cms 2.1.5 documentation » 1. Contributing to Django-CMS Like every open-source project, Django-CMS is always looking for motivated individuals good enough for inclusion, “send us a pull request”, by using the nice Github web interface. 1.3. Contributing Code 1.3.1. Getting the source code If you’re interested in developing a new feature for the cms

1. Model fields 7.2. Form fields Contributing to django CMS 1. Contributing to django CMS 1.1. Community 1.2. In a nutshell 1.3. Contributing Code 1.4. Contributing Documentation 1.5. Translations Indices Created using Sphinx 1.3.5. index modules | previous | django cms 2.2.1 documentation » 1. Contributing to django CMS Like every open-source project, django CMS is always looking for motivated individuals [http://help.github.com/send-pull-requests/]”, by using the nice GitHub web interface. 1.3. Contributing Code 1.3.1. Getting the source code If you’re interested in developing a new feature for the

multiple languages 4.1. Basic concepts Contributing to django CMS 1. Contributing to django CMS 1.1. Community 1.2. In a nutshell 1.3. Contributing Code 1.4. Contributing Documentation 1.5. Translations 2. using Sphinx 1.3.5. previous | next | modules | index django cms 2.4.3-support documentation » 1. Contributing to django CMS Like every open-source project, django CMS is always looking for motivated individuals request [http://help.github.com/send-pull-requests/]”, by using the nice GitHub web interface. 1.3. Contributing Code 1.3.1. Getting the source code If you’re interested in developing a new feature for the CMS

Architecture Kyuubi v.s. HiveServer2 Kyuubi v.s. Spark Thrift JDBC/ODBC Server (STS) Contributing Contributing Code Get Started Code Style Guide Building From Source Building A Runnable Distribution Developer Tools IntelliJ IDEA Setup Guide Contributing Documentations Get Started Documentation Style Guide Building Documentation Community Community Contributing to Apache Kyuubi Collaborators Kyuubi concurrency and service stability of the service itself. Contributing Code These sections explain the process, guidelines, and tools for contributing code to the Kyuubi project. Get Started Good First Issues