View Single Post
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#22
Originally Posted by onethreealpha View Post
many sites for open source applications (freshmeat for example) give VERY CLEAR details of development progress, which in turn can give people a fair idea if the application is actually being worked on.
It's of note that not all applications when using app manager provide a "description" under details.
For extras, a description is mandatory so soon after getting into -testing it should have one if it doesn't. For -devel, well, if you don't know exactly what it is, you shouldn't run it.

Originally Posted by onethreealpha View Post
Making this mandatory with a changelog would be a quick and easy way for users to actually find out if an application has been sitting in the repo for months and months with no active development.
At least one problem we ran into with changelogs is how much to show? Who knows when the user last updated and the way it was handled HAM didn't have a good way to grab all the changes inbetween.

Faster Application Manager allows for changelogs but that is because it queries maemo.org/packages for the information (I think?) which isn't too fast for a single package.

Originally Posted by onethreealpha View Post
including a separate "archive" repo (as previously suggested) to move apps that have had no devel for more than 12 months would also clean things up
just my two cents.....
-devel only really needs tidying for performance, you should know what you are touching and who the author is before touching a package. -testing is the one that could use cleanup since it is an in between and an assortment of people ("usually" testers) load up any application.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog