{
"info": {
"author": "Morten W. Petersen",
"author_email": "morphex@gmail.com",
"bugtrack_url": null,
"classifiers": [
"Development Status :: 3 - Alpha",
"Framework :: Zope2",
"Intended Audience :: Developers",
"Intended Audience :: End Users/Desktop",
"License :: OSI Approved :: GNU General Public License v2 (GPLv2)",
"Natural Language :: English",
"Operating System :: OS Independent",
"Programming Language :: Python",
"Topic :: Internet :: WWW/HTTP",
"Topic :: Software Development :: Bug Tracking"
],
"description": "What is it?\n\n The Issue Dealer is a tool for managing issues, currently\n it focuses on the information in, and structuring of, issues.\n\n It can be used as a generic issue tracker, a knowledge management\n tool, a weblog or an outliner.\n\n It also contains an experimental framework for creating content\n classes through the web.\n\n It has been tested to work with 2.13.22 but is believed to\n work with older versions of Zope as well.\n\nWhy have you created it?\n\n Initially the company I work for (Nidelven IT) needed a tool that\n could help organize and share information. It started as a basic\n 'folder and document' archive on my computer, now it's evolving\n into an advanced (but simple to use!) information management and\n distribution system.\n\n Some years ago I took it over as a personal project, and since I've\n spent so much time on it already and it works well for its purpose\n and that the LAF system is interesting, I'm going to keep updating\n it. I don't know what the future for Zope 2 will be, but seeing how\n different systems can survive I wouldn't be surprised if Zope 2 is\n well maintained 5-10 years down the road.\n\nWhy is it free?\n\n It started out free, and distributing it under the GPL version 2 is\n practical, as it is a well-known software license .\n\n I'd like to start a community around this application eventually, so\n if you think this is an interesting application, get in touch and\n maybe we can do something together.\n\nHow are you developing it?\n\n The project has recently been moved to GitHub, and will be located\n there for the forseeable future. Bug-tracking etc. hasn't been\n setup, but emails and patches are welcome, as are suggestions on\n where to manage the project from.\n\nWhat happens next?\n\n The focus for the 1.0 release is to make the application manage\n information, the focus for the 2.0 release is a complete LAF\n system.\n\nIs it secure?\n\n Yes and no. It is has been built so that access can be restricted\n to different features and levels, but once someone has access to\n viewing, adding, editing or something else, you should assume that\n they can access any part of the system.\n\nDoes it scale?\n\n Probably not. This product is primarily focused on small groups of\n people, and hasn't been stress-tested with big groups of users.\n\nWhat are the main features?\n\n The main features of the Issue Dealer are:\n\n Issue Tracking\n\n - Tracks issues which can be of the type goal, idea, info,\n problem, question and undefined\n\n - Can notify users of new issues or changes to issues assigned\n to them\n\n Information management\n\n - Enables structuring and searching of data\n\n - Advanced search, with saved searches (filters)\n\n Publishing\n\n - A weblog publisher\n\n - Can publish issues to other weblogs\n\n - A local weblog publisher\n\n - Acts as a weblog server\n\n - Supports Atom-enabled clients\n\n - Enables many forms of subscriptions, through Atom as well as\n email\n\n - WebDAV publisher\n\n - Can publish issues along with their images to WebDAV-enabled\n servers\n\n - FAQ publisher\n\n - Generates FAQs based on questions and solutions\n\n - Category publisher\n\n - Publishes issues as categories; these categories can in turn\n be used in feedback forms on websites, as the publisher\n accepts incoming issues as well\n\n - Tree publisher\n\n - Publishes and issues and its contents to a given URL as a\n static page\n\n Advanced HTML/CSS interface\n\n - Many different views of issues in simple interfaces making the\n issues easy to work with\n\n - WYSIWYG editing with support for images\n\n\n0.9.133- (2015-02-12)\n\n - Various fixes to make IssueDealer work.\n\n0.9.132 (2015-02-12)\n\n - Making the IssueDealer Zope 2.13.22 compatible.\n\n - Fixing bug where atom feed failed.\n\n - Fixing bug where creating an IssueDealer instance failed.\n\n - Updated readme.\n\n - Updated copyright time.\n\n0.9.131 (2012-08-22)\n\n - Fixing bug where KeyError was raised under update_catalog\n\n - Fixing bug where AttributeError was raised under update_catalog\n\n - Fixing hyperlinking of URLs in text issues, adding $ as part of a\n valid URL\n\n - Disabling advanced search\n\n0.9.130 (2012-08-22)\n\n - Re-enabling various issue formats\n - Sorting issues in weblog atom feed based on modification date\n - Adding try-except for enclosures in atom feed\n - Escaping HTML entities in weblog for atom feed\n\n0.9.129:\n\n - Repackaging as an egg for dependant packages\n - Fixing CatalogAware imports\n - Making use of ZCTextIndex instead of TextIndex\n - Adding stub utilities.hyperlink_urls method\n - Added separate tools to hide/display issue info\n - Disabled changing issue format (conversion tools broken)\n - Disabled HTML editing (editor broken)\n\n0.9.128:\n\n - Experimenting with various changes\n - Implemented lightweight application framework\n\n0.9.127:\n\n - Added method for generating nonces\n - Added experimental search interface\n\n0.9.126:\n\n - Fixed bug where verification of email wouldn't work\n - Fixing up on Epoz\n\n0.9.125:\n\n - Fixed bug where searching for the word \"zope\"\n would return all issues.\n - Adding count for contained action issues in\n calendar listings\n - Making IssueDealerEpoz forwards compatible,\n with Zope 2.11\n - Fixed bug where it wasn't possible to add\n multiple issues\n - Fixed render_owner bug in session index\n\n0.9.124:\n\n - Added issue past due date to notification email\n - Added documentation on how to setup notifications\n - Implemented past due date listing of events\n\n0.9.123:\n\n - Fixed bug where search_string wasn't found (due to\n double ??)\n - Fixed bug where some URLs included in a text were\n not detected properly\n\n0.9.122:\n\n - Changed things around so that issues can have\n multiple owners\n - Implemented support for setting owner on incoming\n mail issues\n\n0.9.121:\n\n - Added support for removing and adding tags to\n multiple issues at once.\n - Fixed bug where mail messages going through\n verification lost their from info.\n\n0.9.120:\n\n - Added support for tagging incoming issues through\n the mail handler.\n\n0.9.119:\n\n - Added ability to reschedule events directly in the\n calendar view\n\n0.9.118:\n\n - Implemented filter for viewing owned/unowned issues\n on the calendar view\n - Made calendar view remember the date range viewed\n when changing display preferences\n\n0.9.117:\n\n - Fixed bug where transforming the format of\n non-action issues would raise a KeyError\n\n0.9.116:\n\n - Fixed bug where regular (non-action) issues would\n pop-up a message about non-existing calendars\n\n0.9.115:\n\n - Added calendar selection widget for due dates\n - Fixed bug where due with either hour or minute\n set to 0 would remove all time/hour information\n\n0.9.114:\n\n - Making upgrades from \"very old\" versions of\n the Issue Dealer possible\n - Removed try/except in catalog_update so that\n we can get told what's wrong\n - Implemented calendar view (for action items with due date)\n\n0.9.113:\n\n - Cleaning up print statements\n - Fixed RDF bug on filter listing\n - Implemented full support for tags\n - Fixed bug where users couldn't validate their email\n\n0.9.112:\n\n - Updated copyright period on footer\n - Added tag support to issues\n - Fixed bug where HTML mail messages were stored\n without to/cc\n - Added cleaning of incoming HTML messages\n - Overriding AbstractFormatter to format
\n tags properly in text\n - Added feedparser for paranoid cleaning of HTML\n - Implemented spam protection scheme for mail handler\n\n0.9.111:\n\n - Minor fixes for escaping HTML content in the mail handler\n - Implemented threading support for mail handling\n - Implemented skipping of sending of messages to recipients\n already on To/Cc\n\n0.9.110:\n\n - Made the Issue Dealer work with non-standard product locations\n - Implemented mail gateway (mailing list/mail archive interface)\n\n0.9.109:\n\n - Removed the undefined issue type, replacing it with info\n - Fixed bug where update_catalog would choke on images without\n callable ids.\n\n0.9.108:\n\n - Added ability to strip