Are Web-API packages need to be in the 'main' repo ?
- To: firstname.lastname@example.org
- Subject: Are Web-API packages need to be in the 'main' repo ?
- From: Alexey Eromenko <email@example.com>
- Date: Sun, 4 Dec 2011 20:04:10 +0200
- Message-id: <CAOJ6w=ETvgm4mkZFHFQXjfMD1tHn0F6Hx-=M+V56T7TGteTCgQ@mail.gmail.com>
- In-reply-to: <CAOJ6w=EhP-5S-p03=8DQXTo_OUz0ygqAQzdM692zWo=1JY2Ydg@mail.gmail.com>
- References: <CAOJ6w=EhP-5S-p03=8DQXTo_OUz0ygqAQzdM692zWo=1JY2Ydg@mail.gmail.com>
Hello Debian People !
Debian 6.0 (Squeeze) ships packages  that integrate with web services
(called in modern term 'Cloud Computing' or SaaS,
'Software-as-a-Service' if you will), such as the Facebook API.
What if Facebook decides to close down it's APIs tomorrow ?
Will Debian drop those packages from 6.0-stable release ?
I'm not saying such packages must not exist in Debian. They should.
But (!) those packages interface non-free web services, which is
politically no different than non-free software. Technically even
worse, because web-software is likely to break at any moment, change
APIs, or close down free access to it, and demand either NDA contracts
or fee-based licensing.
Perhaps they should be moved to 'contrib' category, because they
interface non-free web-services. Debian's 'main' repository seems not
the right place for any such web APIs.
 Debian project clarifies the diff. between 'main' and 'contrib' here:
 "grep -i facebook" on the package list
What's your opinion ?
-Alexey Eromenko "Technologov"