| |||||||||||
|
| |||||||||||
Debian debates amd64 portDebian debates amd64 portPosted Jul 23, 2004 15:30 UTC (Fri) by mmealman (guest, #9223)In reply to: Debian debates amd64 port by markc Parent article: Debian debates amd64 port The problem is that Debian actually has a very closed developer process. I once used Debian and ran an app called mirrordir that wasn't updated as it needed to be. I contacted the developer for it and had permission to take the package over(he didn't have the time to keep it updated), but it took 8 months for me to get approved as a developer so I could actually update it. By that time the origional developer had already gotten back to updating it. Compare that to Gentoo where anybody can submit ebuilds or even build systems and they'll see them incorporated into the core very quickly. This allows it to scale. Under Debian anyone who can actually do anything is always busy, so hardly anything new happens. With more open dists, anyone can easily contribute, so you're not brain draining your core team for things like amd64, KDE or PHP5 support.
(Log in to post comments)
Debian debates amd64 port Posted Jul 23, 2004 19:02 UTC (Fri) by oak (subscriber, #2786) [Link] Why this is reminding of the recent xfree86 split?
Debian debates amd64 port Posted Jul 24, 2004 7:39 UTC (Sat) by tzafrir (subscriber, #11501) [Link] Indeed you didn't have time to keep it up-to-date. Debian wants to have a "father" for each package, not just for one-time update. One of the things that are tested on those 8 monthes is whether or not you're will to /maintain/ a package. The original maintainer eventually did.
Debian debates amd64 port Posted Jul 26, 2004 9:50 UTC (Mon) by piman (subscriber, #8957) [Link] Rather than becoming a developer, you could have simply submitted a patch to the BTS, prepared an NMU, and asked another developer to sponsor it for you. That would have taken much less time (probably a month at most waiting for a sponsor; I don't know what kind of patch-writing skills you have).Given the level of trust and skill required to maintain Debian packages, 8 months seems more than reasonable. Maybe it's not enough, because my NM process took 8 months, and I've had my share of mistakes.
Debian debates amd64 port Posted Jul 27, 2004 20:18 UTC (Tue) by bronson (subscriber, #4806) [Link] Yeah, right. That would almost certainly not work. For some weird reason, NMUs are frowned upon. It's as if you're insulting the original packager, even if all you're doing is fixing year old bugs. The end result is a whole lot of discussion about who owns what and very little forward progress. Debian is in serious pain right now.I'd love to see Debian encourage NMUs, especially if a bug is older than, say, 1 month. This way, packages wouldn't fester quite so bad.
Debian debates amd64 port Posted Jul 29, 2004 21:04 UTC (Thu) by andrel (guest, #5166) [Link] The release team have been encouraging NMUs.
|
|||||||||||