History for ArchPackage TODO

changed:
-
ArchPackage - Remaining issues

====
Bugs
====

- None? :)

=======
General
=======

- Priority #1: ATManagedFile support (or similar) - we don't want to store the file blobs in the ZODB. [deo]

- Container for Download Section - like PloneHelpCenter. You add a Download area, which allows the Software Projects to be added. This also contains Category metadata and all the other stuff that is currently configured on the FS. [natea]

- Proper integration of the Proposal type, you need to be able to add a reference between a Proposal (aka. PLIP) and a Release, and list these relationships.

- Roadmap generation for releases from the Proposal type - when you enter a Release, you should be able to see what Proposals are scheduled to go into it.

- RSS feed for Latest Releases

- DOAP feed support (Description of a Project)
  http://www-106.ibm.com/developerworks/xml/library/x-osproj3/
  - This will require us to expand the Software Project schema (Package) a bit, to incorporate info about CVS/SVN etc, but it's all useful. :)

- i18n support - right now there is no multilingual support.


=========
Design/UI
=========

- Correct platform icons for the download links.

- Page that lists the 5 latest releases in each category (needs template work)

- Page that lists all the downloads in a category, with batching. (needs template work)

- More descriptive text for Short Name and Description in Release and File.

- Portlet listing the latest published Releases, with Category.

========================
Nice-to-have-but-not-yet
========================

- Have a marshaller for 'Release'. When you upload a .tgz, .zip, .bz2
  file, it should try to extract the PKGINFO, or maybe setup.py and
  populate the objects.

- Maybe have a custom setup.py that is able to register with plone.org
  and populate the objects (also doing upload, and asking for username
  and password).

- SVN integration, you could be able to do the following:

  - Tag a release in the SVN repository

  - Add a release in Plone

  - Select which tag you want the release to be based on

  - Automatically get tar.gz and .zip files for the release

Dependencies, here's Sidnei's comments:

- Add a 'dependencies' tab to release, that shows the existing
  dependencies on a nice layout and allows for adding a dependency
  directly if the user has permission to do so.

- Filter the 'versions' for a choosen package on 'Dependency', as soon
  as the user chooses a package (maybe using javascript?)

- Add pluggable content creation to a 'Package' (or is that a
  'Release'?), so that an instance of a given object is created and
  initialized as soon as the user creates the object. This should also
  be allowed to change after the object has been added (only allowed
  to enable new features, not disable?).