How to publish a module on drupal.org

Before users are allowed to publish their Drupal modules or themes as full projects on drupal.org they have to go through a one time approval process. We do that as quality assurance, to detect security problems, licensing issues and wrong usage of Drupal’s APIs early. I'm an active review administrator on drupal.org and will present the current workflow and how new contributors get involved with their projects on drupal.org. In particular, we will discuss:

• The way your module becomes a sandbox and then a full project
• Avoiding duplication: The Drupal community mindset to prefer collaboration over competition
• Security review: writing secure code and common mistakes new contributors make. This will be a significant part of the presentation, as this is the most important topic to get right when you publish your code.
• Coding standards: keep your code in line with other Drupal code to make it easier to understand
• Automated review and fixing tools: Coder Sniffer, pareview.sh, ESLint
• Licensing: only GPLv2+ allowed
• Review checklist
• The project application workflow
• Review bonus: speeding up the process by reviewing other code
• Community networking: connect with others that might be interested in your code
• Problems with the current review process and plans to improve it

I'm the maintainer of Coder Sniffer (the implementation of Drupal Coding Standards in a tool) and pareview.sh and I'm also a member of the Drupal Security team. I have reviewed over 1500 project applications and know the problems in new modules.

I will leave enough time for discussion after the talk to address any questions, especially for new contributors.