Announcement

Collapse
No announcement yet.

Gnome kills KDE

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #76
    Originally posted by Honton View Post
    You are third person claiming that a large horde of ghost hackers live in the feature branches but never leaves a finger print in the master branches. I took a resonable sample from the feature branches and had a look if those names also got picked up by Ohloh.
    I did so as well and looked for my GSoC student according to ohloh.net his last commit was 6 months ago. Then I looked for a GSOC student working in the Plasma team - last commit one year ago according to Ohloh. I looked for a commit by a new contributor to KWin who provided his first patch on July, 29th - not listed on ohloh. Should I go on? I think my sample set was better, granted I knew which names I should use for the sample set. It doesn't make much sense to pick the fulltime developers who have commits all over the place.

    Comment


    • #77
      Originally posted by Honton View Post
      a few GSOC students? Ha the same thing goes on in GIMP. Have a look.
      Just did. KDE: 50 projects, GIMP: 4. Want to try again? Looking forward to the next argument. Hope it's as easy to debunk (KDE has been the organization with most slots for years).

      Originally posted by Honton View Post
      Besides even if all GSOC students did this it would not be enough to cover the amount of ghost hackers needed to claim that KDE is not dying.
      Hmm, I think I did not do that. I gave you an example for GSOC projects and non-GSOC projects. It was to show you that ohloh doesn't track the current development and thus is just wrong. Concerning your "dying" argument - KDE is strong enough to have most GSOC slots this year. This means 50 hackers and about the same number of mentors (it's not a 1:1 mapping, some mentors have two projects, some students two mentors). As long as that's the case I don't worry about that you think KDE is dying.

      Originally posted by Honton View Post
      Names please, not a few stalled GSOC projects!!!
      I think I gave you names. I didn't want to write the names and the links, because there is no reason to expose them in the public like that. But I gave you enough information to figure out the names. Of course these are not stalled projects given that GSOC is still going on.

      Originally posted by Honton View Post
      KDE hides the Qt agreement on JPGs
      oh that gets even funnier. Ever seen a contract which is not JPG or scanned PDF? That's quite common at least here in Germany and that kind of matters given that KDE e.V. is based in Germany.

      Comment


      • #78
        Omg, this thread makes me want to sell all my linux based equipment.
        You should be proud, MS never managed that.

        Comment


        • #79
          Originally posted by pmorph View Post
          Omg, this thread makes me want to sell all my linux based equipment.
          You should be proud, MS never managed that.
          Oh no! Honton kills Linux! This is proof!

          Comment


          • #80
            Originally posted by Honton View Post
            So you take KDE's inability to merge GSOC project as a sign of succes? Very funny. I just gave you an example of GIMP's branches which shows Gnome also have some feature branches waiting to be merged. But nobody at Gnome would use that as an excuse to explain the loss of more than 100 contributor. It is only you and a few other who are this desperate
            Oh I never said that. You are strongly interpreting my writing. I was only writing about the ongoing GSOC projects. Obviously those are not merged and that was not the point I wanted to make. I wanted to show that the stats at ohloh are missing data. That's all.


            Originally posted by Honton View Post
            So to sum it up. No names just a few cherrypicked references to a few branches. No explanation where the hundreds of ghost KDE hackers are hiding.
            my point was in showing that the stats are not reliable. If you draw conclusions from known incomplete data, fine with me. Just accept that others don't draw data from incomplete data. To me the question btw. would not be: "why is the number of contributors declining", to me it would be "why was the number of contributors so high after the 4.0 release?". Your graph is cherrypicked from 2010, from 2007 onwards it would be way more interesting.


            Originally posted by Honton View Post
            Haha, so you are saying this stops KDE from providing a clear text version and a FAQ?
            No, you are once more interpreting things into my writing (I would appreciate if you don't do that). Apparently nobody thought it necessary, maybe you want to do it, if you find it necessary?

            Originally posted by Honton View Post
            You said yourself you had an lawyer explain things for you.
            What? I have never written that! Please go back and check what I wrote.
            Originally posted by Honton View Post
            KDE has FAILED to communicate about this. Most people are confused and believe Qt is fully covered, which is not true.
            If you say so, but Honton is not "most people". I had never seen somebody being confused about it.
            Originally posted by Honton View Post
            This is sooo dishonest and KDE does nothing to make it better. And YOU are totally absent when people make misjudgements which makes KDE look more powerful. That is very wrong. And the links you provided earlier shows how dishonest everyone at KDE is about this. My posting got discussed because I tell what the agreement says. But no one at KDE reacts when confused people says Qt is fully covered.
            I'm sorry that you are confused. I think the problem here is that you did not be around when Qt Free Edition still existed. For most people knowing the history it's quite clear. There is no evil behind not updating the text when Qt became GPL for Windows and Mac. Probably nobody thought about that. There are other sloppy elements like a link to qt.nokia.com which is wrong nowadays. Your update to the text would certainly be appreciated.

            But let's also face that right now the difference hardly matters. Except for the platform plugins the code is the same. So all that might be lost are the plugins for the proprietary platforms. Would be sad, but we all hope that the foundation will never have to execute the rights, don't we? I personally would not care if those plugins got lost as my software is X11/Wayland only and that's the only part to which I have ever contributed in Qt (c.f. to my saying that I don't have a problem with the CLA as my contributions are protected).

            Comment


            • #81
              Lol at all those 1337 huxxors who think just because they are using a linux distro know about programming and software engineering... OMG the ignorance...

              Those 2 projects aren't comparable for many reasons. All those metrics mentioned are only relevant to those projects. Code structure is different, libraries are different, everything is different between KDE and Gnome, there is absolutely no comparison. This is just a lame attempt at trolling.

              The only real way to judge those projects is by looking at the end result.

              Based on this, both DE suck at the moment. Gnome attempts a race to remove as many features as possible as fast as possible, while KDE so-called "long term support version" (4.11), still has crippling bugs and can't stay sane for 10 minutes without X crashing(at least on my machines)...

              So instead of trolling like a fool, try contributing to the project of your choice because both frankly suck and have serious problems, and need help. If you can't do that because you are just a kid with no skill, STFU and don't waste other people's time...

              Comment


              • #82
                Originally posted by TemplarGR View Post
                can't stay sane for 10 minutes without X crashing(at least on my machines).
                completely off-topic: you want to track that down. It's mostly a sign of something rather broken in the setup. A client software like anything from KDE should not be able to crash the privileged X server (that's rather obvious). It's also not really common, we hardly get bug reports for X crashes (I just searched and the last reported X crash was in March caused by fglrx). And if we get, we don't "fix" them as it needs a fix in another place, we could only work-around it, which would keep the possibility of a crash possible.

                Comment


                • #83
                  To add onto what Martin is saying, Calligra development is heavily branch based with the intent of having a stable master and from what I've read of various mailing lists the same is true for most KDE projects except for Kontact. But Calligra has got it's various GSoC projects going on right now but it's also porting over to Qt5 as an example of a big purely branch based development going on right now (of course the problem with porting to Qt5 right now is that KF5 isn't released yet which led to rather significant debate over how to handle it) and is something that will likely just live in a branch for the foreseeable future.

                  Comment


                  • #84
                    It's so funny we have all these dumbasses waisting their time in here because there's no other place to spend it in their actual lives.

                    I hope _you_ are dying.

                    Comment


                    • #85
                      Originally posted by mgraesslin View Post
                      completely off-topic: you want to track that down. It's mostly a sign of something rather broken in the setup.
                      "Broken" is a natural state of linux, therefore one shouldnt waste his time tracking products natural state.

                      Comment


                      • #86
                        Originally posted by ArchLinux View Post
                        It's so funny we have all these dumbasses waisting their time in here because there's no other place to spend it in their actual lives.
                        Those who live in glass houses shouldn't throw stones...

                        Originally posted by startzz
                        "Broken" is a natural state of linux, therefore one shouldnt waste his time tracking products natural state.
                        Works For Me (c)

                        Comment


                        • #87
                          Gnome is dead, it is actually born dead!
                          just look at biography of its creator and you'll figure out that gnome is Microsoft try to bug us all!!!

                          PS. And on my Debian(testing) KDE works all day long without any crashes!

                          Comment


                          • #88
                            Originally posted by edmon View Post
                            Gnome is dead, it is actually born dead!
                            just look at biography of its creator and you'll figure out that gnome is Microsoft try to bug us all!!!

                            PS. And on my Debian(testing) KDE works all day long without any crashes!
                            Miguel hasn't even been involved with gnome in a very long time, stop spreading FUD.

                            There's way too much moronic FUD on these forums from both sides.

                            Comment


                            • #89
                              Originally posted by bwat47 View Post
                              Miguel hasn't even been involved with gnome in a very long time, stop spreading FUD.

                              There's way too much moronic FUD on these forums from both sides.
                              I don't like this situation either, but look at gnome it is a such a big proof!

                              Comment


                              • #90
                                Originally posted by mgraesslin View Post
                                completely off-topic: you want to track that down. It's mostly a sign of something rather broken in the setup. A client software like anything from KDE should not be able to crash the privileged X server (that's rather obvious). It's also not really common, we hardly get bug reports for X crashes (I just searched and the last reported X crash was in March caused by fglrx). And if we get, we don't "fix" them as it needs a fix in another place, we could only work-around it, which would keep the possibility of a crash possible.
                                It usually means that the graphics hardware is defective/overheating. I imagine that the issue would go away if all of the graphical effects were disabled.

                                Comment

                                Working...
                                X