The lack of any package description on the source page is a real problem for me. It's helpful when you're working with a large number of packages (say MOTU Science team with 500+ packages) since you can't remember what all the packages do. I end up running between apt-cache and LP trying to do work which is a bit of a pain. Perhaps if a source produces only a single binary the description from that could be used straight away. If multiple binaries are produced then perhaps the short descriptions with a dropdown area for the full description would work?
Overall the overview page is nice from a publishing perspective, but not really much help when you want to know about the software itself (like Homepage, if it's maintained in VCS, etc.) I realize that some information (maintainer, build-deps, component, section) are release-dependent but I feel like having the latest information from the development release is too useful to have to dig around for all the time.
The lack of any package description on the source page is a real problem for me. It's helpful when you're working with a large number of packages (say MOTU Science team with 500+ packages) since you can't remember what all the packages do. I end up running between apt-cache and LP trying to do work which is a bit of a pain. Perhaps if a source produces only a single binary the description from that could be used straight away. If multiple binaries are produced then perhaps the short descriptions with a dropdown area for the full description would work?
Overall the overview page is nice from a publishing perspective, but not really much help when you want to know about the software itself (like Homepage, if it's maintained in VCS, etc.) I realize that some information (maintainer, build-deps, component, section) are release-dependent but I feel like having the latest information from the development release is too useful to have to dig around for all the time.