One usually adapts to unforseen problems, not ones that are known going into the project.
Your suggestion is akin to buying a car that you know has bad tires, a bad alternator, a rusted body, and sundry other things wrong with it for full price, and just planning on fixing when it actually breaks. It costs a lot more that way. On 11/13/05, Stuart Herbert <[EMAIL PROTECTED]> wrote: > On Sat, 2005-11-12 at 10:26 -0500, Chris Gianelloni wrote: > > If users are interested in non-critical information, there's already a > > mechanism in place for them to get such things. They can join the > > mailing lists. Do we not already have a gentoo-events list? We also > > have a gentoo-releng list, or gentoo-announce. > > At this point, I think you're suggesting that we different news carried > by different mediums. If so, I think that's very different from the > proposal I'm putting forward. > > > > I'm not hoping for a 100% perfect technical solution straight away. > > > > I am. Anything less at this point is a half-assed design. The *design* > > should be 100% from the start. While implementation can occur in > > stages, you should not design as you go. > > I think that's a worthy goal, but looking around, it looks to me that > software design just doesn't work like that in real life. Designs have > to adapt and change as time passes, not just implementations. > > Best regards, > Stu > -- > Stuart Herbert [EMAIL PROTECTED] > Gentoo Developer http://www.gentoo.org/ > http://stu.gnqs.org/diary/ > > GnuGP key id# F9AFC57C available from http://pgp.mit.edu > Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C > -- > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQBDd79pDC+AuvmvxXwRAqJRAKCiGr6Vu9rarsmfhDJrB0R5Fl0nIwCfUrfK > lkPLVrFD0WhteHk/mcOKFtU= > =PjJ8 > -----END PGP SIGNATURE----- > > > -- gentoo-dev@gentoo.org mailing list
