Contributing to Drupal.
Patches, modules, themes, distributions, etc.
Creating and maintaining projects.
Docs:
- Best practices for creating and maintaining projects
- Tips for a great project page
- README Template
- Module documentation guidelines
- Best practices for co-maintaining projects
- Granting Issue Credit as a Maintainer
- Commit messages - providing history and credit
- Status settings of issues
- Release naming conventions
- What are alpha, beta releases and release candidates?
- Creating a project release
Notes:
- Make sure you've adhered to the Drupal coding standards. Use Coder project and it's online version http://pareview.sh/ to check your Drupal code against coding standards and other best practices.
- Always add README.txt file to your project. Use README Template.
- If your module creates any hooks or has an associated API, add examples of these hooks in a file named modulename.api.php.
- Grant issue credits appropriately when maintaining a project.
- Attribute authorship of provided by community patch by adding a commit author if applied with no or minimal changes.
- You should not need to set Closed (fixed) issue status yourself.
- Once you've created an official or development release (node) on a branch, you cannot alter git history on this branch anymore.
Patches.
Docs:
Git.
TBD.