Steve Langasek wrote: > But for new packages, where Canonical is striking out on its own > to deliver significant new functionality and the folks working on these > packages are not DDs, there's a clear pragmatic argument for doing the work > directly in Ubuntu rather than blocking the work on finding folks able to > upload to Debian and willing to maintain the packages there.
To be a devil's advocate: when the Debian Developers that a company has been able to contact (inside or outside the company) do not consider a package to be ready for upload, it is not hard to contribute the packaging to Debian in an RFP bug to avoid duplication of effort. If the company considers the package suitable for ongoing use (for example via inclusion in Ubuntu universe), it's probably suitable for Debian experimental, too, and it doesn't take much time to upload and sync from there. So I don't see the delay as an important reason not to cooperate. Some important reasons not to cooperate publically would be avoiding revealing business plans too early, or lack of expertise regarding Debian processes by the people working on a particular package. Jonathan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130423065832.GA1390@elie.Belkin