|
|
Log in / Subscribe / Register

Still shipping a broken gdm without XDMCP option?

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 8:40 UTC (Fri) by gowen (guest, #23914)
In reply to: Still shipping a broken gdm without XDMCP option? by patrick_g
Parent article: Release candidate for Ubuntu 10.04 LTS now available

It's Jef Spaleta. Facts, nuance and differences of opinion come a distant second when there's an opportunity to bash ubuntu.


to post comments

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 16:09 UTC (Fri) by paulj (subscriber, #341) [Link] (2 responses)

To Jef's credit it seemed to me he was actually explaining why this was not Canonicals' fault but upstream-induced and how Canonical even tried to stall for time in the hope upstream would address the feature regressions.

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 17:43 UTC (Fri) by dlang (guest, #313) [Link] (1 responses)

I read it as an attack on Ubuntu for not having worked on fixing the bug, first by ignoring the upstream changes (not helping fix it), and then by just switching to the upstream version without fixing the problem

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 18:04 UTC (Fri) by jspaleta (subscriber, #50639) [Link]

So the original post I was responding to wasn't an attack? By my explanation was? Did I say they made a wrong or a bad choice? They made a choice.. and those choices have consequences.

And furthermore Canonical has addressed some of the problems by quickly putting together a replacement for the gdmconfig gui for their own users. It doesn't address everything. But its probably fair to say its the best effort that can be made without actively getting involved in gdm development. Is that sort of reactive downstream effort enough to satisfy their own users?

I haven't seen Canonical bring this tool up for discussion in gnome upstream for a heads up and to see if it fits in with the gdm roadmapping. I might have missed it. As always I'd love a reference to a public discussion between Canonical and upstream developers. If there is any evidence that Canonical is making a firm engineering commitment to be an active part of the Gnome code development..I haven't seen it.

The money for a sysadmin and the upgrade of gnome bugzilla are nice to see. Better launchpad integration with Gnome is surely beneficial to Canonical so it makes some sense for them to be the driver for the bugzilla upgrade. There's a lesson there about driving your own needs into upstream projects that could be applied equally to the gdm situation. But neither of those things are going to help prevent wide and prolonged divergences between upstream's development focus and Canonical's deliverables. Prevention of that nature requires proactive engagement into the upstream process. Is it an attack on Canonical to say that?

-jef

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 16:58 UTC (Fri) by jspaleta (subscriber, #50639) [Link] (2 responses)

Point of fact... its Canonical not Ubuntu that I'm bashing. I'm pretty consistent about that.

I thought I was actually sort of defending Canonical there. It's not their fault that gdm lost features in the re-write was introduced several gnome releases ago back in 2008. How could it be? they aren't involved in gdm upstream development in any significant way, happily patching in features into their downstream version of gdm instead of helping with the re-write.

If you haven't read the gnome 2.24 release discussion about releasing gdm 2.24 from the fall of 2008...you should.

Here's the hard reality.... there's zero guarantee that the features a specific distribution feels are important will be in the next version of _any_ software. A distribution is free to hold back a version of any component if they feel it better meets there needs...that's perfectly acceptible. But that should be a big red flag moment when it happens to a core piece of technology..especially for a quickly moving corporately sponsored distribution to do a quick health check between upstream roadmapping and internal interests...especially when those features don't materialize for 3+ of your distribution releases.

It's one thing to hold back on one release because you were taken by surprise. It's something else to hold back on two releases because you don't have the in-house expertise on staff to make quality contributions to the upstream project. But 3+ releases? You can't just hunker down and hope upstream is planning on implementing the features you feel you need. At some point you have to step up and be a part of that upstream development process. Upstream maintainers said as much in this case in their own words back in 2008. History has sort of proved them right.

Shuttleworth is all about "less is more" these days in Canonical's own design work... the gdm developers were way ahead of Shuttleworth-think on that score it seems.

-jef

Still shipping a broken gdm without XDMCP option?

Posted Apr 23, 2010 22:56 UTC (Fri) by nix (subscriber, #2304) [Link] (1 responses)

Pah, they had nothing on the gnome-session developers. What do you mean you want the ability to save your session or save the state of applications that conform to the X Session Management Protocol rather than our new whizzy DBus-based protocol which even most GNOME apps don't use yet? Why would you want to do that?

Still shipping a broken gdm without XDMCP option?

Posted Apr 24, 2010 13:13 UTC (Sat) by paulj (subscriber, #341) [Link]

And it's still not working correctly either I think. It doesn't seem to save my "xterm +sb -geometry ... -e alpine" xterms. At one point it /tried/ to save session state for them, but then would crash on session start - that was fun.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds