bruce@pixar.com (Bruce Perens) writes: > > These are exactly the same issues we will need to deal with when somebody > > chooses to use Debian and dpkg as a base for a value-added commercial > > distribution. > > Are you sure they are exactly the same? When someone makes a value-added > commercial distribution, they make a committment to service that > distribution. So far, I haven't seen any need for committment attached to > the unofficial package repository. Well, I assume anybody doing this will want to service bugs themselves (from their own bug system) and create lots of non-maintainer releases -- if they want too release a quality product. Relying on unpaid Debian maintainers who might not respond for weeks or months is not going to fly when you take your business plan to your banker to raise some capital. > The Debian JP project seems to be organized much the way we are. I believe > they'll be around when service is necessary. Yes - but it is organized differently, they have their own versions of Debian packages, and a separate bug system. I don't see this changing given the language barrier. So we still need to have mechanisms and policies in place to cooperate with other "side distributions" that may make non-maintainer releases and otherwise complicate things. > Maybe you need to make some > rules (Chorus: "WE DON'T NEED NO STINKING RULES!") about what committments > people make when they drop a package in your archive. I made the rules already - primarily "No Warez". I'll make more rules when the time is right -- if they are needed. I'm doing this to enhance Debian, rather than trying to take away from it. Cheers, - Jim
Attachment:
pgptNCg54w9jN.pgp
Description: PGP signature