You are viewing the PKP Support Forum | PKP Home Wiki

Development Guidelines

OCS development discussion, enhancement requests, third-party patches and plug-ins.

Moderators: jmacgreg, michael

Forum rules
Developer Resources:

Documentation: The OJS Technical Reference and the OJS API Reference are both available from the OJS Documentation page. While these are OJS-specific, the OCS codebase is similar enough to OJS they should be of help. There is also an [url=http://pkp.sfu.ca/ocs_documentation[/url]OCS Documentation[/url] page with some more general documentation that might also be of interest.

Git: You can access our public Git Repository here. Comprehensive Git usage instructions are available on the wiki.

Bugzilla: You can access our Bugzilla report tracker here.

Search: You can use our Google Custom Search to search across our main website, the support forum, and Bugzilla.

Questions and discussion are welcome, but if you have a workflow or usability question you should probably post to the OCS Conference Support and Discussion subforum; if you have a technical support question, try the OCS Technical Support subforum.

Development Guidelines

Postby asmecher » Tue Jul 03, 2007 10:31 am

Contributing Code

The PKP team is happy to accept patches and development discussion in this forum. If you would like to have your patch included in the OCS codebase, we suggest discussing it with the development team before implementation to ensure that it suits upcoming development plans.

For code that is intended for inclusion in the main codebase:
  • Patches against a current CVS checkout are preferred; alternately, patches against the most recent release version are acceptable.
  • Unless agreed with the development team, users should be able to toggle contributed features between enabled and disabled with a single setting; the system behavior should not be modified when the feature is disabled.
  • The design patterns used in OCS 2.x should be understood and adhered to.
  • Localization standards should be maintained.
  • Database IDs should be checked as in the current codebase.
  • XSS (cross-site scripting) attacks should be checked as in the current codebase.
  • Contributors are responsible for writing code compatible with the primary platforms listed in README.
  • Contributions should be delivered to the team via this forum as a patch.
  • OCS 2.x management features should be kept in mind, such as upgrade and installation; all database schema information should be maintained in the dbscripts/xml/ocs_schema.xml file; etc.
  • The development team is happy to review contributed patches, but we have a limited amount of time to spend integrating patches with the codebase or modifying contributed code. If aspects of the code need work, we would rather inform the author and have them perform the modifications.

For contributions that are distributed separately as patches or plugins:
  • If contributors haven't met all the conditions above, they are welcome to distribute additional features as patches or plugins. However, the development team won't be able to provide support in this case.
  • If the option is available, coding a feature as a plugin is the preferred method.

Additional coding standards and information are available in the CVS repository in docs/README-DEV. The OJS 2.x technical reference may also be useful; see the "Documentation" section of the OJS homepage.
Posts: 10015
Joined: Wed Aug 10, 2005 12:56 pm

Return to OCS Development

Who is online

Users browsing this forum: No registered users and 1 guest