wiki:DevGuide

Version 1 (modified by rjollos, 9 months ago) (diff)

Just a start, but hopefully it gain some momentum.

Plugin Development Guide

This document captures some best practices and guidelines for plugin development. It is a community driven document, and everyone is encouraged to contribute to it. If you have questions or comments, please raise them on the MailingList.

License

Plugin authors are encouraged to clearly indicate how the contribution is licensed. This is important for both users and future developers of your plugin. Having a clearly defined license allows someone else to adopt and carry on development of the plugin if you choose to no longer support it. It is also important for users and administrators who need to understand the terms and conditions under which they can use or modify the code.

Trac-Hacks is an open source community driven by voluntary contributions and made successful by collaboration. Therefore we encourage the use of licenses that foster collaboration and minimal restrictions on future use of the code. Trac has adopted the BSD 3-Clause license, and use of the same license in any plugin code is encouraged. One of the many benefits to adopting this license is that any plugin code can potentially be integrated into the Trac core down the road.

The following steps are suggeted:

  1. Add the license keyword in setup.py (example).
  2. Add a license header to every Python source file (example).
    # -*- coding: utf-8 -*-
    #
    # Copyright (C) your name here <your email here>
    # All rights reserved.
    #
    # This software is licensed as described in the file COPYING, which
    # you should have received as part of this distribution.
    
  3. Add a license header to every HTML template (example: TBD).
    <!--!
      Copyright (C) your name here <your email here>
      All rights reserved.
    
      This software is licensed as described in the file COPYING, which
      you should have received as part of this distribution.
    -->
    
    The use of the XML comment marker as shown is important so that the text does not get rendered to the output. Make sure not to use the alternate form, which is rendered to the output as a hidden comment: <!-- This is also a comment -->
  4. Add a COPYING file with the license text in the top-level directory of the project (example).

Currently it is not recommended to add license text to static resources (i.e. file in htdocs), since doing so will increase the size of the content that is sent to the client. This issue will be addressed in the Trac core when support is added for minimization (trac:#10672).

Coding Style

Authors are encouraged to conform to the Trac Style Guide and PEP-0008 style guide.