Jump to content

Reiver_Fluffi

Members
  • Posts

    2209
  • Joined

  • Last visited

Posts posted by Reiver_Fluffi

  1. The best burning app for Gnome is (by far) Brasero - maybe its not close yet to K3B or (the commercial) Nerolinux 3, but its a pretty decent application.

     

    Thanks for that tip, never knew that existed until now, the interface looks good. I just need something to burn now. ;)

     

    Most Gnome themes are nicer than KDE themes (in my opinion), and are easy to install.

     

    I agree, but like you say that is a matter of taste.

     

    If this is still the case on Fedora, I'd say, stick with GNOME there.

     

    I haven't had any problems so far, although I don't use KDE much.

  2. You can register for being an early seeder of Mandriva Linux 2008.
    #

     

    As per usual you will get numerous people signing up for it, get the release early and then forget the rest of you, as you try to leech onto the few honest early seeders doing as they promised. Great idea (yes I did just give praise in Mandriva's general direction, but please don't tell the world ;)), but abused by far too many people, which is quite sad!

  3. Please don't use these, they're rude and an absolute pain.

     

    If people need to know you're on holiday, then you can notify them beforehand. For those who don't need to know, they can wait until you return.

     

    James

     

    I disagree, it is a good practice for people that are in business to use an auto responder. In many cases it is not reasonable for them to furnish all of their (numerous?) customers, suppliers, and other affected stakeholders with this information beforehand. There's nothing rude about clearly stating to the sender why you will not be attending to their email in good time, it is very good communication, it would be very rude not to, ignorant, maybe.

  4. I'm with this guy in this one:

     

    Do it the Linux way.

     

    I do not understand why vendors are so focused on distributions (and Linux business models). Provide high quality drivers (or enable a community to provide them). Linux support for your hardware emerges automatically. Watch closely what is happening an be ready to make your (service?) business as soon as the time is right.

     

    Little costs, little risk, win-win for all.

     

    Regards

    Thomas

     

    P.S. Don’t limit your market for Linux to a fraction of the Linux market by selecting a “Linux vendor” or two.

  5. However, using a texteditor to create html or xml requires advanced syntax knowledge, which is not everyone's cup of tea...

     

    In addition, drawing a table with a GUI is a lot quicker than hand coding it. Personally I like to use WYSIWYG to lay out the basics, then tweak and validate the code after.

  6. SAN FRANCISCO—Windows Vista has probably created the single biggest opportunity for the Linux desktop to take market share, Cole Crawford, an IT strategist at Dell, said in an address titled, "The Linux Desktop—Fact, FUD or Fantasy?" at the annual LinuxWorld Conference & Expo here.

     

    For example, a number of companies have moved back to Windows XP after deploying Vista, Crawford said, before quoting Scott Granneman, an author, entrepreneur and adjunct professor at Washington University in St. Louis, as saying, "To mess up a Linux box, you need to work at it; to mess up your Windows box, you just have to work on it."

     

    [more...]

  7. There's a large difference between asking questions and criticizing without evidence. You didn't ask what happened before you started throwing criticism around, and that's not well justified, in terms of management ;)

     

    It was an opinion based on what facts that have been presented and my understanding of the relevant business process. For any manager incomplete information is a fact of life, people make criticisms with incomplete information all the time, I wouldn't be the first, nor the last. There's my justification.

     

    BTW, who was I meant to ask, Mandriva? Don't think so, they don't have a habit of communicating effectively (AdamW aside) with their stakeholders unless it is in their interest to do so (i.e. Euro's), otherwise they are not interested, that is well evident if you look at their forum (with the odd whine here for good measure).

     

    Anyway good discussion :thumbs:

  8. Personally, I don't think having a bad beta ISO is an issue that will hurt their business, especially if the problem is recognized and resolved in a timely manner - and, so far, we have no evidence to the contrary - yet you continue to criticize - again, it seems like you've just been looking for an excuse to do so.

     

    Did you note the word "potentially"?

     

    As far as I can tell, if they ever make any mistakes at all, you'd get on them for it (justified or not) - you don't happen to be a manager at your day job, do you?

     

    If mistakes are made, questions have to be answered, in terms of management that action s well justified.

  9. But, now you are wrong!

     

    Feel free to disagree with me, but please do not tell me that my opinion is wrong, that is not for you to decide.

     

    If you increase the community involvement, you 'will' ease the burden of the current (paid) staff, opensource == community.

     

    Not at all, the reengineering exercise merged responsibilities and created greater burdens on individual staff, only so much of that can be delegated to the community for various reasons, plus with the additional burden of managing the increased community involvement. It's not a simple matter of equating the decrease in staff with the increase in community involvement as you bluntly put it.

  10. Putting out beta ISO's is part of a community process; getting the community involved is the whole point of doing it (as well as cooker). The business process you are looking for (apparently) would be their retail CD and DVD boxes, which this wasn't a part of, so you seem to be criticizing them for involving the community?

     

    If you are attempting to argue that Mandriva should not involve the community in their beta process, and should close it up since they sell their end product, or something to that end, that is a whole different discussion and one we certainly shouldn't burden this thread with. If that's not what you're saying, then I seem to be lost as to what your argument is. Oh well, moving on...

     

    Business processes go far beyond retail boxes. The point is that if they chose to involve the community, they need to manage it, otherwise community mistakes like this could potentially be embarrassing for the business. Mandriva's recent business process reengineering will bring up more instances like this as they increased the burden on current staff and introduced heavier involvement from the community, both very risky.

     

    I will be watching with the :popcorn: I just stole from spinynorman :D

  11. Just tried the OpenSuSE live CD on VMWare. It's still horribly buggy, but at least one can clearly see now the shape of things to come...

     

    I tried the CD, I agree that it is very buggy, didn't see much in the way of significant UI improvements other than the deskbar applet, which was broken for me.

  12. :lol2::lol2::lol2:

     

    I knew you were going to say that. Do you really think it's worth the pain of setting up a password, giving that password out to all the possible people who would want to mirror (and, thereby requiring anyone who wants to mirror to request the password),

     

    Have you totally ignored my comment above, i'm looking at things in terms of business processes, not a community project, maybe my flaw is comparing Mandriva to "real" businesses, fair enough.

×
×
  • Create New...