It's up to you, really, but the recommends tag doesn't do much in the application manager. I would still say POP3/IMAP/SMTP sort of stuff is really basic, which I would recommend for depends, and any additional (facebook, twitter, whatever) would in my book be optional (=separately installable). But as said, it's really up to you, we're just making suggestions here (though the metapackage really should disappear :)

Attila, but we already have yet another plugin for russian social network: http://maemo.org/packages/view/qmf-vkontakte/. And soon will be plugins for facebook social network, livejournal blogs system and vBulletin forum. We are working on it.

In new devel build I moved plugins from depends to recommends section.

Yes, if there is a bug in the web interface, we should fix that, and not create packages - it's much harder to resolve later. Also, as long as you don't have additional plugin packs, just this one (which you need for normal operation), it does not have to be in the user section (plus, if you put the plugins in the user section they will require separate QA and you won't be able to promote the client until the plugins pass).

Excuse for persistence, what do you think of this package's architecture? http://oss.fruct.org/w/images/3/3f/Qmf_package_architecture.png

You're Right. And now the "stock" plugins in the client's dependencies, because qmfmail it test/example application and for demonstration the necessary plugins... qt4-messagingframework package was created because the page http://maemo.org/packages/view/qt4-messagingframework/ was empty, but link on this package shows in Latest packages (http://maemo.org/packages/repository/latest/fremantle_extras-devel_free_armel/all/), because it name of sources (Source: qt4-messagingframework in control file). Well, I can to remove the qt4-messagingframework metapackage and only qmfmail will be in user/network section. It will be a correct action, in your opinion?

IMHO something is wrong with the naming if a framework depends on its client :) From what you describe I would say your only real user visibe installable is the client (personally, I would even include the "stock" plugins in the client's dependencies).

Mikko, we agree with you. Server should be invisible for users. Project consist of server, client, plugins and over. And client doesn't directly depend on plugins, because some users may want to use only over (third party) plugins, for example, our qmf-vkontakte plugin and they don't want to install the basic plugins or part of it. Maybe divide package of plugins into several parts: pop, imap and smtp and to remove them from dependences of the client. But default plugins it part of qmf and this is an excuse to create a qt4-messagingframework metapackage depending on the client and plug-ins. Then qmfmail, plugins and qt4-messagingframework should be in user section, but, i agree with you, for all of these packages should be detailed and clear descriptions. What do you think about this? Thanks!

There is one end user usable application (QMF Mail Client) and three use visible packages (QMF Mail Client, qmfserver, qt4-messagingframework)? I hope you could hide other packages than this end user application from Application Manager list, because multiple packages create only confusion.

It could be useful to trim "sales speech" (description) because now it's not very understandable.