Welcome to the Zotero Issue Tracker

Guidelines

1. This is primarily a developers' tool, not a discussion forum or feedback medium. Comments should generally be limited to those that provide new information or offer concrete implementation ideas. Larger/ongoing discussions should be carried out on the dev list or in the forums.
2. New ticket creation is currently restricted to core developers and admins as we work to ramp up our triage and support infrastructure. If you believe you've found a bug or have a feature request that isn't already in Trac, please post a note in the ​forums.
3. Patches to be incorporated into the official codebase will need to have an associated ticket and be reviewed by a core dev before they can be committed. If you don't see a ticket for a patch you've written or would like to work on, drop us a note on the dev list, in the forums, or via e-mail to trac@….
4. Don't modify other people's bugs. This applies in particular to the priority, target milestone and assignee fields. If you'd like to suggest a change or offer to work on a bug owned by someone else, add a comment instead.
5. To quote ​Mozilla's Bugzilla Etiquette page (which is also worth reading): "Some of these rules may not apply to you. If they do not, you will know exactly which ones do not, and why they do not apply. If you are not sure, then they definitely all apply to you."

Comment Access

Only authenticated users can add comments and modify tickets. To request a Trac account, please fill out the ​SVN/Trac Access Form.

Source code access

In addition to Trac's graphical repository browser, anonymous read-only access is available to the Zotero source code repository. You can checkout the latest version of the code with the official Subversion client using the following command:

svn co https://www.zotero.org/svn/extension/branches/1.0/ zotero

This will create a new zotero directory with a "working copy" of the 1.0 branch. (The trunk is currently quite outdated.) For instructions for running Zotero from a working copy, see ​SVN and Trac Access.

Note: If you're not planning to make code changes and just want to try out updates to Zotero as they are committed, you can use the ​development XPI rather than an SVN install.

Planning Documents

Add links to planning documents here

Other resources

• ​Zotero Developer Documentation — overview of Zotero, file descriptions, API documentation, coding guidelines, a sample utility, etc.
• ​Zotero Forums
• ​zotero-dev mailing list