Development Roadmap
Both the Osprey and Permaseed packages are currently in alpha release form. Development will move toward release candidate (RC), then to generally available (GA) status. This is a far-from-comprehensive list of features to implement and does not include the much-needed testing, tuning, and bug fixing. The items do have differing priorities. However, the ordering below doesn't necessarily reflect those priorities.
Release feature priorities
1.0
- Hierarchical objects (parent/child relationships)
- Object typing & categorization
- RSS feeds for front page blocks
- Permaseed batch mode for torrent generation and uploading
- Permaseed drop priv support to facilitate init script use
- Standalone tracker drop priv support
1.1
- Integrated torrent generation and seeding from file upload
1.2
- Lucene-based full-text search
- PostgreSQL support
Features on the to-do list
Web application
- Review and fixing of all input validation
- Osprey tracker and distributed searching
- Integrated OAI provider
- XML import-export tool
- Wordpress plugin for automatic torrent-izing of blog/podcast attachments.
Standalone tracker
- Keep state in memory and dump peer list to mysql table on an interval. Save state to mysql table on SIGINT
- NAT checks
- Retain previous checking timestamp for peers for calculating xfer rate info
Permaseed
- Config & torrent reread on HUP, need to purge entries from cache, storage layer, disconnect clients on missing torrents
- Transfer logging in apache-like format to keep track of bytes transferred to BT clients
- For torrent mappings, add mysql support or something similar to facilitate remote management. Or possibly add support for multiple torrent mapping config files.
- Many, many performance and stability tests
- Possibly rewrite in c or c++
