[maemo-developers] ... and QA of closed source applications?

[From: Quim Gil]

ext Attila Csipa wrote:
> I think one of the key issues is not if it is possible to install non-free 
> software, but rather to be in the clear that people *know* which software is, 
> and which isn't free and then decide for themselves if they want it or not. 
> In the spirit of recalling the history of the wheel, I'll mention the Debian 
> and Ubuntu families solve this by putting them in a separate repository (just 
> as available as the free ones). Since we already have a nokia/extras split, 
> this could be just as extension to that.

Done since years ago.

http://repository.maemo.org/extras-devel/pool/fremantle/free/
http://repository.maemo.org/extras-devel/pool/fremantle/non-free/

http://repository.maemo.org/extras-devel/pool/diablo/free/
http://repository.maemo.org/extras-devel/pool/diablo/non-free/

etc.

> In the same vein, Ubuntu solves the question of 'I just ported but I have no 
> clue how it works' with the main/universe/multiverse repo split, so you know 
> which package is really cared for and when are you treading more dangerous 
> waters with regard to support (this also defines where the bugreports go -> 
> for a universe package most of the stuff will go upstream -> unlike packages 
> in main which have maintainers/packagers who actually have the knowledge to 
> check/fix bugs and decide if a bug is worth sending upstream or not.

Applied to Diablo, the Ubuntu/Canonical repo structure can be more or
less mapped, in different terms

Main
http://repository.maemo.org/pool/maemo4.1/free/

Restricted
http://repository.maemo.org/pool/maemo4.1/non-free/
plus binary-only packages from catalogue.tableteer.nokia.com

Universe
http://repository.maemo.org/extras/pool/diablo/free/

Multiverse
http://repository.maemo.org/extras/pool/diablo/non-free/

Canonical's Partner
catalogue.tableteer.nokia.com - certified


> There is a downside, of course - dependencies get more tricky with multiple 
> repositories, but with a clearly defined procedure and repository purpose 
> that can be remedied in most cases. The alternative, shoveling everything 
> into a single giant melting pot repo (regardless of license, level of support 
> or origin) did not work for Debian or Ubuntu, so I'm a bit skeptical if it's 
> the right way to go in Maemo, either.

As you see we never have gone that way. Actually Nokia is the least
interested mixing open and closed licenses, supported and unsupported
software.

-- 
Quim Gil
open source advocate
Maemo Software @ Nokia