On Monday 26 November 2007 04:15:47 am G T Smith wrote: > Rajko M. wrote: > > On Saturday 24 November 2007 02:27:29 am Jan Tiggy wrote: > > ... > > > >>> Why waste time on unnecessary development (which will then > >>> have bugs), when the SuSE team *COULD* be using that same > >>> time, energy, and attention working on things that are > >>> currently broken. > >> > >> Full ACK! Let it be guys and maybe focus on bugs for a season. > > > > Hi Jan, > > > > No one wants to develop something new without good reason, specially not > > Novell that is paying for this. > > > > YaST is old tool, and it was changed from time to time to adjust layout > > and functionality to new demands. This version is few years old and it > > was example how to do it when it was created, but now there are better > > solutions and YaST has to go forward. > > Been following this discussion and some of its diversions with interest. > > Some thoughts.... > > a) I think that currently Yast as a overall design is sound and really > needs little change. Where some things are kept needs some tweaking, but > to change references like NISS to something like 'centralised user > management' is probably inappropriate and likely to create as much > confusion as it is to enlighten.
Sure. > b) A good idea would be links to a local (at least for networking, if > your networking is broken and you want more info, an externally > networked resource is not got to be entirely helpful) html version of > the documentation and where appropriate HowTos from the modules as with > swat. It is logical to have basic network off line, and basic system setup in the book. > c) Probably the thing which needs most revision is the software > management side. I seem to remember with 8.x and 9.x fairly detailed > information on a particular package was available before one installed it. > > Now we have a scenario where we get a massive and slow update of local > information resources (which makes this process rather painful), that > does not include such info. From a company (Novell) that has access to > some of the most efficient database synchronisation technologies around, > this is somewhat unbelievable, and needs fixing. So far I know they are looking to provide package information before package is installed, but that is not trivial for repositories that are not static. Simply they don't want to rush and slow down package management. > d) Though there is some doubt on the attribution of the quote below... I > think one needs to be aware that there is validity in the point > made...change for changes sake is a dangerous trap... > > [...] but it seemed that every time we were beginning to form up into > teams, we > would be reorganised. I was to learn later in life that we tend to meet > any new situation by > reorganising, and a wonderful method it can be for creating the illusion > of progress while > producing confusion, inefficiency and demoralisation." > (Caius Petronius Arbiter (Roman Administrator). c.60 A.D.) Since Roman times life is not changed that much :-) > =========================================================================== > I have always wished that my computer would be as easy to use as my > telephone. > My wish has come true. I no longer know how to use my telephone. > > Bjarne Stroustrup > =========================================================================== http://en.opensuse.org/Famous_quotes -- Regards, Rajko. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
