Hi Panu, Panu Kalliokoski wrote: >>Allow me a general comment on your descriptions: please do try to adapt >>them better to the situation of the average Debian user trying to decide >>whether to install the described package.
> I'm attempting to do this; but I don't think there's really hope that > somebody than doesn't know minesweeper, klotz and/or sokoban could > decide whether to install them, from the description. ksokoban's description might be a bit verbose if you have multiple games, but the first two paragraphs seem to be a good start for distilling something. > Actually, I don't know any implementation that _can't_ use the generated > level, since the Sokoban file format has been semi-standard from the > first Sokoban implementation, AFAIK. Ah. I didn't know. Maybe it'd be nice to say that and perhaps even list a couple of examples from the Debian pool (you could Suggest: them anyways). >>games might be useful in the cgames long description, I'm not sure that >>all users realize that "curses based" means "text-based gui"). > Good point. Although "text-based" does not imply it uses full-screen > mode. But maybe that's not so important. For the record, sarge > currently has 33 packages that have "curses-based" in their description. It's hard to come up with an ideal solution, but I'd guess that "text-based user interface" as opposed to "commandline interface" might be workable. Some of these (well, the 38 in unstable) use "text-based" as well or are arguably targetted at a more technical audience (3270 telnet programs). >>Also, please try to fit your (short and long) descriptions better into >>what's usual in Debian. Matthew Palmer's Debian-Mentors FAQ has helpful >>references. > I'm not sure what you're referring to; the section elaborating what to > put into RFS, perhaps? I was thinking of Colin Walters' article[1] linked to in the sponsorship checklist, not the FAQ itself, sorry. Kind regards T. 1. http://people.debian.org/~walters/descriptions.html -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
