[Openupload-svn-update] SF.net SVN: openupload:[371] trunk/TODO

[<ts...@us...>]

Revision: 371
          http://openupload.svn.sourceforge.net/openupload/?rev=371&view=rev
Author:   tsdogs
Date:     2010-03-18 18:24:44 +0000 (Thu, 18 Mar 2010)

Log Message:
-----------
version 0.5 modifications

Modified Paths:
--------------
    trunk/TODO

Modified: trunk/TODO
===================================================================
--- trunk/TODO	2010-03-18 18:24:11 UTC (rev 370)
+++ trunk/TODO	2010-03-18 18:24:44 UTC (rev 371)
@@ -2,57 +2,45 @@
 
 ******* TARGETED FOR RELEASE 0.5  *******
 
-Administration
- - Move the logic of administration inside the modules (where possibile)
- - A way to add / remove plugins and a way to sort them out
-
-Users
- - Add paging to new "My Files" feature
- - Add more personal options (defaults)
-
-Setup
+- New upload method with perl cgi
+- Remove prototype and use jquery
+- Add a single click upload
+  - options can be set before upload (and must be, as long as possible, checked before the upload)
+  - add option to logout after the upload
+  - add option to notify the user if something goes wrong
+- Move administration options inside modules/plugins
+- review the "step" functionality
+- New GUI (multi file selection, options, administration,etc)
+- Add invitation logic
+- Separate LDAP from AD authentication (they differ too much, use ADLdap)
+- TXTdb migration to gladiusDB
+- Create a new setup script which uses the single plugins and modules for the configuration
+  - first thing, paths then everything else.
   - Check for required paths to be writable...
-  - Check for zip/tar ?
-  - Enable TXTDB initialization
+  - checks and configuration options moved into the modules/plugins
+- Upgrade/Migration script
+- Plugin sorting should not impact gui
+- SQL backend should be more versatile (joins and so on, probably using some direct sql templates would help)
+- Add user options (defaults for options/plugins)
+- Users may be part of more than one group in the db auth.
+- Files can be assigned to other users/groups
+- Expiration can be decided by the user
+- cron job script that allows to do the cleanup of expired files
+- Email templating
+- Files can be imported from the FS
+- User accounts can expire
+- Better urls/admin, maybe mod_rewrite could be used
+- mime types handled on the server side
+- a file can be edited after the upload is complete
+- data tables for files users, etc.
+- api to upload/download from outside the application
 
-Templates
-  - Review the template (and maybe add a new one)
-  - Better multifile selection
+Other things which probably will be postponed
+- Antivirus plugin
+- Encryption plugin
+- (?) use apache authentication so can be integrated with the system users
 
-Database
-  - Change the txtdb to something like gladius
-  - Add the join function
-  - Review the database structure
-  - Add a way to upgrade the structure/data
 
-LDAP
-  - AD and LDAP behave too much different, separate the module (or at least the differences)
-  - use ADLdap ?
-
-New features
-  - Files visible to groups, could also add the possibility to decide wether the file is "public" or "private"
-  - API
-  - "guest" functionality
-  - User might decide duration of a file
-  - Cronjob for removal/maintainence
-  - Add perl CGI for upload
-  - Email personalization (templating)
-  - Add possibility to select a file already on the server FS.
-  - Possibility to add personalized fields to be completed (on registration, file upload, etc)
-  - User account expiration 
-
-Things to modify
-  - Change upload tracking technology (no prototype.js)
-  - Don't like all that step etc.
-  - review the ACL/function names to be more self explaining
-  - Edit file properties 
-  - Maybe a single step upload, change/add properties 
-  - Mime types must be handled on the server (not from the browser)
-  - directory structure for "volatile" data
-
-Plugins
-  - Review the plugins as to permit to extend all the app functionality
-
 Documentation
   - Will this ever be done :) ?
 
@@ -97,14 +85,14 @@
 - Authentication with NTLM (mainly on LDAP module)
 
 
-Plugins 
+Plugins
 - (Following are some ideas)
   Download bandwith limiting depending on group (of upload user probably better)
   Download wait time (is this really needed?)
   User additional fields for registration request.
   Antivirus on upload
 
-Translation 
+Translation
 - Add a database translator? not until base isn't complete.
 
 Template


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.