Re: NLD10 and GNOME
Hi to all of you, El mié, 08-02-2006 a las 18:21 +, Jamie McCracken escribió: > (btw big thank you for XGL - Im using it now and it rocks way better > than OS/X and vista) > Despite this thread being boring there is a lot of very important stuff to be learned here... but I am much more interested in other things: Jamie, what video card/drivers are you using, what are the main specs of your machine (CPU, RAM, Distro, kernel, etc.), what problems did you have when configuring XGL, Compiz, etc. What did you liked and/or disliked the most about this new technology? Is it as responsive for you as seen in those videos? What do you think that can be improved? (Having in mind that this is still a work in progress). I'm more interested in personal opinions of people who have configured and used this amazing new technology. A big thank you to all the people who made this posible!. -William __ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam �gratis! Reg�strate ya - http://correo.yahoo.com.mx/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
Hi all, My god, I am a little surprised at the discussion that has resulted from a small comparison I made on my blog. :P I want to be entirely clear in my opinion here - I was not criticising Novell for these changes, just making the comparison. In terms of the 'design behind closed doors', I think its a really tough one to quantify and draw an opinion from. Sure, in a perfect world, everything would be developed up front, in public and be subject to full public discussion and commentary. I think for day to day GNOME work and development - work that does not mean fundamental changes to the user interface philosophy and direction of GNOME, this is pragmatic and workable solution. For fundamental changes to GNOME infrastructure or interface, the problem runs a little deeper, and I can identify with the bike shed analogy. I think the problem is that to really push forward and make fundamental innovative decisions, it requires someone to step up and make a solid stand. The problem of course is that in a large distributed project such as GNOME, few people want to step up and make such a stand and risk treading on so many toes. I think this is becoming an increasing problem for GNOME. As many of you will know, I used to be heavily involved in the KDE project, and I defected over to GNOME because I thought that the GNOME community (a) had a finer understanding and appreciation of usability and (b) the community had the balls to stand up and make decisions. In recent months there seems to be some fragmentation in the community and little spats like this really don't help. As I blogged about last night (http://www.jonobacon.org/viewcomments.php?id=640), it seems there is a cyclical wave of community confidence and ability that moves between KDE and GNOME - and this is most certainly derived from the social scenario of developing software within a public community, and the competition and opinions that that infers. So in summary, I can identify with both sides - I can sympathise with developing going on behind closed doors to at least get *a* solution up and running without it turning into a talking shop, but I can also understand Jeff's concern that such things are not really under the kind of 'community' banner that we would all like it to be. Its just a same we have such 'sides'. The concern I have is that unless some of these problems are resolved, Topaz is only going to be a pipe dream - a pipe dream that no-one wants to stand up and kick off due to fear that anyone standing up and making a decision will involve a community backlash. With fundmental changes like ones discussed in Topaz, we really need a decision to be made at some point. I would be happy to stand up and propose JonoGNOME, but I suspect you would all laugh at me and poke me with a stick. :P Cheers, Jono ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
> > (A similar set of issues were expressed more eloquently in my GUADEC talk, > > if you want to watch that video.) > > do you have a link? http://stream.fluendo.com/archive/6uadec/Jeff_Waugh_-_Project_Topaz.ogg - Jeff -- FOSDEM 2006: Brussels, Belgiumhttp://www.fosdem.org/2006 "Old timers will tell you what a pain unstable was during the new testament transition." - Jon Corbet on Debian's KJV packages ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
On Thu, 2006-02-09 at 02:54 +1100, Jeff Waugh wrote: > > > > What a big jerkbird! So lazy! So community-tearing! Definitely the work of > > an evil, evil noncontributor. > > Anna, as I mentioned in another email, this frustration is about a broader > problem we have in our community than the particular acts of contributing > organisations or individuals. Definitely a large portion of the frustration > you read in my email was aimed at *myself*, as I have also contributed to > this 'sorry state' of affairs. > > It was not a good email. It was too emotive in precisely the wrong context. > > (A similar set of issues were expressed more eloquently in my GUADEC talk, > if you want to watch that video.) > do you have a link? ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
Good morning, everyone. Goodness sakes. This thread has so much anger in it! I can't help but think that there is a misunderstanding or two that needs to be cleared up. The photos that Jono found are from a website that the team I manage uses to house our daydreams, our ideas, our rants -- I have the uncomfortable feeling that some people here are confusing a set of mockups that we never intended to develop further for actual product plans. As the design lead for NLD 10, I can say for sure that we are NOT implementing almost any of the stuff shown in those mockups. Do we really need to email all the gnome lists every time someone on my team has a new daydream? Are you guys not sufficiently sick of all the "The World According to Me" emails that our mailing lists attract? This is ridiculous. El mié, 08-02-2006 a las 12:16 +1100, Jeff Waugh escribió: This is a very sorry state of affairs for GNOME. But it is not only Novell and its employees who have adopted this commons-sapping, community-tearing, morally and intellectually lazy approach to open design and development in GNOME. Uh. Ok. You know, I went to a ton of trouble to put those 200 usability videos up on the web at http://www.betterdesktop.org . After I put them up there, I reviewed the site with people at the Boston summit, to see what else they wanted me to do. They said, "Turn it into a wiki so we can comment!" - so I did. What a big jerkbird! So lazy! So community-tearing! Definitely the work of an evil, evil noncontributor. Call me pissed ('cause I am), but hearing about how destructive I am makes me feel like perhaps my attempts to involve the Gnome community in all the testing I've been doing are moot. Why bother if nothing will ever be good enough, or appreciated? Why bother if lists devolve into name calling over a few daydreamy screenshots? But ultimately, this is *killing our community*. Really? From where I sit, it looks our community is killing our community. Anna. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Hey, On Wed, 2006-02-08 at 11:52 +, Alan Cox wrote: > Nor does the committee argument stand up. It is perfectly possible to > post in advance that "we are going to do this, we've created a temporary > alternate repository for the work and if you want to join in or help > merge stuff back as it meets acceptability please sign up" Indeed that's probably one of the few problems I could possibly have - seeing this stuff through some demonstration videos of NLD [1]. We probably just need some common sense involved in making sure the appropriate people in the community get a heads up so they don't have to see it 2nd or 3rd hand. Innovation happens elsewhere, and that's really, really great to see. We can just be a lot more mature about it and the community that we're building. Glynn [1] And I'm 100% sure Sun has been in this boat too... ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
It's not about Novell (was Re: NLD10 and GNOME)
Le mercredi 08 février 2006 à 23:17 +, Jamie McCracken a écrit : > Hopefully, Novell will release the source soonish and put this issue to > rest. Please, we're mainly talking about a problem that is not about Novell. We should let Novell people know that we love them, as much as we love the Red Hat guys and all the people working on GNOME. The main problem I see is that the GNOME community could be a central point, but is not. It's caused by many lacks. But *we* can change this. If we stop blaming people for bad reasons. Thanks, Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Sriram Ramkrishna wrote: On Wed, Feb 08, 2006 at 11:17:01PM +, Jamie McCracken wrote: Hopefully, Novell will release the source soonish and put this issue to rest. What would we do with it? How many of Ximian's contributions have we merged or RedHat's? It's a huge job, and unless they sync up with the maintainer on occasion, I'm not sure how it'll end up in CVS. its a separate applet so thats okay - it wont mess up the existing code. It will need some adjustment to remove any beagle dependency (IE replace it with a plug-in interface so I can optionally use tracker or beagle with it) but otherwise its a cool applet and that makes it especially frustrating waiting for it and compwiz too... -- Mr Jamie McCracken http://www.advogato.org/person/jamiemcc/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On Wed, Feb 08, 2006 at 11:17:01PM +, Jamie McCracken wrote: > Hopefully, Novell will release the source soonish and put this issue to > rest. What would we do with it? How many of Ximian's contributions have we merged or RedHat's? It's a huge job, and unless they sync up with the maintainer on occasion, I'm not sure how it'll end up in CVS. Feelin cynical... sri ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Kalle Vahlman wrote: I mean, I'm making a theme engine (for Maemo) but haven't released anything yet. Will you behead me for being secretive when I do or just let it slide because I'm tweeny-tiny myself and not a big company? I only take exception when a large company (especially one that makes a lot of money from OSS) deliberately delays disclosure of source purely for financial reasons (IE in order to keep ahead of their competitors). Whilst any company that does that is not screwing the community (provided they eventually release the source) they are however treating the community in a negative fashion. Hopefully, Novell will release the source soonish and put this issue to rest. -- Mr Jamie McCracken http://www.advogato.org/person/jamiemcc/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
> On Wed, 2006-02-08 at 21:54 +0100, Jon K Hellan wrote: > > However, if we decide to target a niche audience, on a niche operating > > system, that's niche squared. I doubt if that's sustainable. > > Didn't say niche, I said specific. The group can still be large. There are > many, many well-defined subsets of the world's billions of people that > still contain a hell of a lot of people. Apple have done this very cleverly over the past few years with OS X. They concentrated on their core market, really worked hard to nail it, and have been scaling out to other markets as the opportunity has come up and their ability to focus on the broadening market needs balloons. - Jeff -- FISL 7.0: Porto Alegre, Brazilhttp://fisl.softwarelivre.org/7.0/www/ "Basically my philosophy on release management is that it should be like police brutality." - Maciej Stachowiak ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
On Wed, 2006-02-08 at 21:54 +0100, Jon K Hellan wrote: > However, if we decide to target a niche audience, on a niche operating > system, that's niche squared. I doubt if that's sustainable. > Didn't say niche, I said specific. The group can still be large. There are many, many well-defined subsets of the world's billions of people that still contain a hell of a lot of people. And the whole point here is to remove the nicheness of the software (whether it's an OS, I don't know), by appealing strongly to a specific group that wants to use it. Would you expect a sports car with a truck bed to appeal to more people than a regular truck or regular sports car? I would not. Not choosing an audience doesn't mean you appeal to everyone. It means you appeal to everyone in some ways *and* make everyone hate you in some ways, so nobody really likes you overall. What you want to do is be sure some group of people likes you in *almost all important respects*. The fallacy is to think that indecisiveness avoids the decision and leads to universal appeal. It does not. It leads to either a de facto decision (best case), or a totally incoherent piece of software (worst case). Sure, the trick is in picking a group that's specific enough but not too niche, and in trying to appeal to multiple "similar enough" groups, while not breaking your appeal by chasing overly-dissimilar groups. But life is full of judgment calls, no? Havoc ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
On Wed, 2006-02-08 at 11:28 -0500, Havoc Pennington wrote: > If you guys want a specific productive suggestion, I think these are two > de facto directions that could just be adopted; one is a kind of > building block platform shared among the GNOME desktop, Maemo, GPE, XFCE > even [2]; it might benefit from becoming explicitly targeted toward > multiple projects? Emphasize fd.org more. I don't know. Two is a GNOME > desktop that is still largely UNIX/shell-user/developer-oriented, > designed for the customers of today's Linux distributions. Focus on this > more and do it better. > > If the community wants to go beyond these de facto directions, I think > it's possible, but only if people have the courage to commit to their > chosen audience and recognize that it means not serving some other > audiences. In the past, we lacked that courage for whatever reason. Good thinking, as always. However, if we decide to target a niche audience, on a niche operating system, that's niche squared. I doubt if that's sustainable. Jon Kåre ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/8/06, Jamie McCracken <[EMAIL PROTECTED]> wrote: > wrt to yer blog post regarding code drops at release time, I hope you > and Novell can be persuaded to do more development in the open just for > the sake of fairness (as we currently have a level playing field with > the vast majority of Gnome software being done in the open). No one > would complain if a small company or some individuals did stuff secretly > but a big company like Novell should set a good example here. Actually it is the big companies that have very extensive and tedious legal processes in place for code, they have a lot to lose in court of law if someone working there steals code from someone else for example. Small companies probably won't have as much resources or interest for screening. A good example of this is the Maemo platform which had very slow turnup on (open source licensed) code to the svn repository just or at least mainly because of legal checks and other corporate stuff (or so I've gathered from the responses to community queries about sources). > Profit > from open source has always centered around support and services rather > than a panel applet or two so I doubt you will lose anything and its > certainly not worth the loss of good community relations. If it's just an applet or two they were making, why the fuss?-) I mean, I'm making a theme engine (for Maemo) but haven't released anything yet. Will you behead me for being secretive when I do or just let it slide because I'm tweeny-tiny myself and not a big company? Just because I want it to have more than the one widget themeing before I realease anything? -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Hi, On Wed, 2006-02-08 at 12:09 -0500, Rodney Dawes wrote: > It's not an extension to the panel menu code. It's not even a patch. > It's a completely separate applet. This is in fact, in no way different > than a theme engine in terms of integrating it upstream, into a larger > conglomerate package. Why do people keep assuming every change someone > does, is a patch? There are much better ways to do a lot of this stuff, > than patches, with the architecture we have. Well, to be fair, it's not like they can just look at the code and know this. ;) I don't think such a kneejerk reaction is so overboard judging from a single mockup and a fuzzy freeze frame in a video. Joe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Rodney Dawes wrote: On Wed, 2006-02-08 at 17:43 +0100, Kjartan Maraas wrote: In a sense, but a theme is more self-contained and wouldn't need review in full the samme way that an extension to the panel menu code would. It's not an extension to the panel menu code. It's not even a patch. It's a completely separate applet. This is in fact, in no way different than a theme engine in terms of integrating it upstream, into a larger conglomerate package. Why do people keep assuming every change someone does, is a patch? There are much better ways to do a lot of this stuff, than patches, with the architecture we have. glad to hear it - perhaps some of us were overreacting a bit :) wrt to yer blog post regarding code drops at release time, I hope you and Novell can be persuaded to do more development in the open just for the sake of fairness (as we currently have a level playing field with the vast majority of Gnome software being done in the open). No one would complain if a small company or some individuals did stuff secretly but a big company like Novell should set a good example here. Profit from open source has always centered around support and services rather than a panel applet or two so I doubt you will lose anything and its certainly not worth the loss of good community relations. (btw big thank you for XGL - Im using it now and it rocks way better than OS/X and vista) -- Mr Jamie McCracken http://www.advogato.org/person/jamiemcc/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
ons, 08,.02.2006 kl. 12.09 -0500, skrev Rodney Dawes: > On Wed, 2006-02-08 at 17:43 +0100, Kjartan Maraas wrote: > > In a sense, but a theme is more self-contained and wouldn't need review > > in full the samme way that an extension to the panel menu code would. > > It's not an extension to the panel menu code. It's not even a patch. > It's a completely separate applet. This is in fact, in no way different > than a theme engine in terms of integrating it upstream, into a larger > conglomerate package. Why do people keep assuming every change someone > does, is a patch? There are much better ways to do a lot of this stuff, > than patches, with the architecture we have. > I'm all the more pleased to hear this. Maybe if this had been communicated more clearly from the outset we would have avoided this kind of confusion :-) (or maybe I didn't do my homework before commenting). Anyway, this wasn't really the important part of my reply to Dan so don't read too much into it. > And frankly, we need to show ISVs that it can be done, so they will > start doing it too. We need their support, if we're going to succeed > at actually getting Linux and GNOME to be usable and on desktops in > the Real World (TM). > I agree fully. Cheers Kjartan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On Wed, 2006-02-08 at 17:43 +0100, Kjartan Maraas wrote: > In a sense, but a theme is more self-contained and wouldn't need review > in full the samme way that an extension to the panel menu code would. It's not an extension to the panel menu code. It's not even a patch. It's a completely separate applet. This is in fact, in no way different than a theme engine in terms of integrating it upstream, into a larger conglomerate package. Why do people keep assuming every change someone does, is a patch? There are much better ways to do a lot of this stuff, than patches, with the architecture we have. And frankly, we need to show ISVs that it can be done, so they will start doing it too. We need their support, if we're going to succeed at actually getting Linux and GNOME to be usable and on desktops in the Real World (TM). -- dobey ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
ons, 08,.02.2006 kl. 10.55 -0500, skrev Dan Winship: > Alan Cox wrote: > > So if Fedora, Ubuntu and every other Gnome using distribution also start > > doing tons of private development > > (Excluding Xgl, there was hardly "tons" of private development.) > > > then trying to jam it all in CVS > > afterwards how do you expect Gnome to develop when all these variants > > suddenely try and get merged and all overlap and clash. > > We don't. A lot of people have assumed that we're expecting to force the > new menu code into the GNOME mainline at some point, which I guess is a > reasonable assumption given what happened with Ximian Desktop, etc, but > that was never the plan here. At the moment we're not even planning to > ship it in SUSE 10.1 (which is 90% the same codebase as NLD10). The new > menu is something we did for NLD, and if the community wants it too, > then great, but we didn't do it with the expectation that they > necessarily would. It's like Industrial was. > In a sense, but a theme is more self-contained and wouldn't need review in full the samme way that an extension to the panel menu code would. > > Nor does the committee argument stand up. It is perfectly possible to > > post in advance that "we are going to do this, we've created a temporary > > alternate repository for the work and if you want to join in or help > > merge stuff back as it meets acceptability please sign up" > > Yes, I shouldn't have suggested that secrecy was a necessary part of the > mix. The secrecy doesn't necessarily help. But how does it actually > *hurt*? Yes, there are integration issues in some cases, but not in this > case. Yes, there are code review issues as you mentioned in another > message, but it's not like the GNOME community and/or Red Hat is > reviewing the work we do on YaST or iFolder or any of dozens of other > non-GNOME things, so that argument also feels weak. Novell has also been > doing tons of GNOME work in the open, so it's not like we're trying to > get a free ride off GNOME. So what exactly have we done wrong? > I don't think you've done anything wrong. Nothing that isn't weighed up by the great contribution this is to making linux on the desktop succeed. It just happens to stomp on a sore foot, so to speak. This is a community problem and it's the community that has to solve it if we want to avoid this kind of thing happening in the future. Good thing Novell is part of the community too :-) Looking forward to seeing some of this incredibly cool technology pop up on my desktop too one of these days. I think also that we sometimes put too much emphasis on never duplicating code or effort. I really think that it gives the community as a whole more experience in how to approach a certain problem and that "both sides" can learn from each other's mistakes when this happens. I'm sure there are lessons to be learned from metacity/libcm/compositor vs. Xgl/compiz that will benefit both projects long term. There are probably other examples of the same. I do mostly agree that you could have achieved the same step forward codewise without the secrecy, but it would have created a fuss and you would have lost the fun of announcing something entirely new to the world :) Cheers and thanks to everyone involved for doing all the work this must have been. Kjartan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
On Wed, 2006-02-08 at 04:49 -0200, Evandro Fernandes Giovanini wrote: > > There's also the issue of who you target with the changes. Novell might > find in a usability test that the menu they designed is a lot better for > their target audience but most people in the GNOME community would > reject it in favor of the current panel layout (I'm one for example). > Should that stop Novell from doing what's best for their customers > (people used to Windows but now using GNOME because their company went > with NLD)? Since everyone must chime in on this thread ;-) and I'm not above a potshot from the sidelines while not doing any work anymore, my comment is that deciding the above, community-wide, is a much larger issue than the one Jeff raises (or than whether we have XGL or panel changes at all). In fact this question should define a project, rather than defining a project as a particular set of tarballs and source code. Is GNOME for UNIX and shell users? Is it for Linus Torvalds? Is it for ourselves? Is it for American college students? 35-year-old corporate office workers with an IT staff? And are we willing to tell whoever it's *not* for to jump in a lake? The blog thread this weekend brought up the old "are we too dumbed down, not dumbed down enough, or just right" line of thinking which (apologies to whoever feels offended) I find to be a shamefully lazy, wholly misleading, and simply completely broken way to think about software. A close second, which is the "let's be simple and avoid confusing people" school of thought, is really just the same limited approach, rephrased to sound better. Yes I've been guilty of it myself. Doesn't make it right. The replacement for this should be: 1) who, specifically, is the software for? (ideally much more specific even than stuff like "technical vs. nontechnical users") [1] 2) why, specifically, do they want to use it? what does it help them do that they want to do? Helping them do it without being confusing is a hygiene kind of thing, like code maintainability; but doing something someone wants to do at all, and knowing the who and what, is the first-order problem. And you have to do something they want, that they can't already do, *considering the entire reality of what software (and non-software) they are already using*. There's no way anyone can rearrange the panel menus and add eye candy, in order to convert something appealing to nontechnical college kids into an enterprise/corporate thing, or convert a programmer/sysadmin/shell-user desktop into something plausible for college kids. It's not about surface cosmetics, guys. The overall direction needs to be in the roots of the project, it answers the question what should the software _do_. What should it _be_. Should it be a "desktop" at all? Going back to my blog posts last month, define the hole, not the drill. Until the project answers that, it will create building blocks that get rearranged and reshuffled into other projects, whether NLD10 or Maemo or Red Hat. The extent of the rearranging can be large or small. No shame in that, but if that's the plan (as it _definitely_ is for e.g. the Linux kernel) then suck it up and optimize the project for it. Lots of times the kernel developers' thoughts and practices very much assume this. They are writing a component for use by developers, not an end-user product. And they aren't ashamed of it and they optimize for it and they do it well. Jeff, you're right that Steve Jobs style "big press release" is incompatible with community development (though I don't think it's a moral issue perhaps, I think it's legitimate to make the tradeoff as long as one is willing to eat the consequences). But the larger problem right now is what I described above, the lack of direction; if the community had that, they would just steamroll over the cosmetics coming in from the Linux distributions. And also a lot of "stop energy" would go away, because it usually arises from lack of agreement on the big picture (which gets expressed through nitpicking about details). btw, choosing an audience and effectively making something for them *will* alienate other audiences, possibly even losing the support of the Linux distributions. That's the reality. Don't think you can move in a direction without *not* moving in a different direction. There _is_ a default audience if a project doesn't find a way to choose one deliberately, and it's what I've called "by and for developers." If there's no way to stay out of that gravity, it's better to embrace it wholeheartedly IMO than to be there de facto and keep poking developers in the eye. e.g. whether to expose paths in the UI; if most of your users are shell users, GNOME probably made the wrong call. A developer orientation could also concentrate on making the project a good building block for integrators creating custom solutions, whether NLD or Maemo, by modularizing it, making it customizable, and not flaming about the customizations. I
Re: NLD10 and GNOME
Alan Cox wrote: > So if Fedora, Ubuntu and every other Gnome using distribution also start > doing tons of private development (Excluding Xgl, there was hardly "tons" of private development.) > then trying to jam it all in CVS > afterwards how do you expect Gnome to develop when all these variants > suddenely try and get merged and all overlap and clash. We don't. A lot of people have assumed that we're expecting to force the new menu code into the GNOME mainline at some point, which I guess is a reasonable assumption given what happened with Ximian Desktop, etc, but that was never the plan here. At the moment we're not even planning to ship it in SUSE 10.1 (which is 90% the same codebase as NLD10). The new menu is something we did for NLD, and if the community wants it too, then great, but we didn't do it with the expectation that they necessarily would. It's like Industrial was. > Nor does the committee argument stand up. It is perfectly possible to > post in advance that "we are going to do this, we've created a temporary > alternate repository for the work and if you want to join in or help > merge stuff back as it meets acceptability please sign up" Yes, I shouldn't have suggested that secrecy was a necessary part of the mix. The secrecy doesn't necessarily help. But how does it actually *hurt*? Yes, there are integration issues in some cases, but not in this case. Yes, there are code review issues as you mentioned in another message, but it's not like the GNOME community and/or Red Hat is reviewing the work we do on YaST or iFolder or any of dozens of other non-GNOME things, so that argument also feels weak. Novell has also been doing tons of GNOME work in the open, so it's not like we're trying to get a free ride off GNOME. So what exactly have we done wrong? -- Dan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
> What a big jerkbird! So lazy! So community-tearing! Definitely the work of > an evil, evil noncontributor. Anna, as I mentioned in another email, this frustration is about a broader problem we have in our community than the particular acts of contributing organisations or individuals. Definitely a large portion of the frustration you read in my email was aimed at *myself*, as I have also contributed to this 'sorry state' of affairs. It was not a good email. It was too emotive in precisely the wrong context. (A similar set of issues were expressed more eloquently in my GUADEC talk, if you want to watch that video.) - Jeff -- FISL 7.0: Porto Alegre, Brazilhttp://fisl.softwarelivre.org/7.0/www/ "The cool stuff coming out of freedesktop.org doesn't just happen as the result of an accident with a particle accelerator and a goat: it only happens when people hack on it." - Daniel Stone ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
So if Fedora, Ubuntu and every other Gnome using distribution also start doing tons of private development then trying to jam it all in CVS afterwards how do you expect Gnome to develop when all these variants suddenely try and get merged and all overlap and clash. Do you want to have situations where people play games like releasing one day earlier than the other so they can check their stuff into CVS/Subversion/whatever to block the 'opposition' ? Nor does the committee argument stand up. It is perfectly possible to post in advance that "we are going to do this, we've created a temporary alternate repository for the work and if you want to join in or help merge stuff back as it meets acceptability please sign up" Alan ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Need for lead (Re: NLD10 and GNOME)
On Tue, 2006-02-07 at 19:53, Elijah Newren wrote: > So, we have two merged window manager + compositing manager codebases > now. My question is whether and how we can merge these. I think that's precisely the heart of the problem: decisions in the GNOME project are made not to hurt community developpers. Sometimes I'm sure the core isn't even looked at and is accepted as a whole. Code needs to be accepted on it merit, not only feature-wise but wrt its quality, integration with the rest of the desktop and testability (i.e. no too big changes in the code at once). Look at Xorg, they asked David to integrate Xgl piece by piece, rejecting unwanted changes. Look at the linux kernel, they often reject ideas without code, and often reject code because it's not good or because it's too big. But they never decide to merge two pieces of code just to please both developpers. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
Le mercredi 08 février 2006 à 04:49 -0200, Evandro Fernandes Giovanini a écrit : > I think the process used by Novell is very common in the GNOME community > (and Free Software in general). > > For example take metacity. Sawfish was the default window manager, so > Havoc could have started a discussion > "should-our-window-manager-be-like-this-instead". But he didn't; what he > did was write metacity following the design he had in mind in a window > manager. Metacity was included in GNOME because most people adopted it > and agreed that Havoc's design was better for the default window > manager. AFAIK, Havoc used CVS for metacity. Everybody could look at it. > The menu layout we use today is another example. If people had gone on > discussions about which is better - the foot or the "menu panel" - > perhaps things would have gone nowhere. But someone wrote the "menu > panel" and eventually it became the GNOME default. There were discussions about the new layout, but they were not on d-d-l ;-) It was also done in CVS, by one of the maintainer. > Ubuntu has also done some changes in the panel, like the 'Add to Panel' > dialog. From what I remember this was first done in Ubuntu and after a > release using that configuration discussion started on the usability > list. The Ubuntu "Add to Panel" dialog was developed with input from a gnome-panel maintainer (who wondered what result it would give). Discussion on usability list occurred because the maintainer was not sure the result was okay. (maintainer being me, in that case) > Another example is the log out dialog on the right top corner of > the screen in Dapper, which wasn't proposed for discussion on > mail.gnome.org, it was just implemented there when GNOME uses the window > selector for the top right corner. AFAIK, the log out thing in dapper is just a simple applet. The real change is in the gnome-session dialog. I'm not sure the gnome-session maintainers were aware of this change, but I believe that at least Mark wanted to move this functionality to the panel, so... [...] I'm not saying design by community works. But people working on the modules that will be changed should have the possibility to know about the change. Don't ignore them. Be nice. Another solution is to just proclaim "we don't need maintainers any more, everyone can do anything". Less work for me ;-) (but I'm not sure this is a good solution). Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Be nice to the contributors (was Re: NLD10 and GNOME)
Le mardi 07 février 2006 à 15:55 +0100, Christian Fredrik Kalager Schaller a écrit : > Hi, > While it would be good to get fixes and improvements right away I do > think its to hard to criticize anyone for holding back a bit on things > they are doing. Being able to ship something first is an important > marketing tool and this has happened before. In most cases where it has > happened the distribution makers have been good at working with the > community afterwards to get their changes merged upstream. > > Remember getting those changes merged in is in their interest too > as keeping a larger and larger diff maintained is very costly and time > consuming, so I am sure nobody wants to keep the changes any longer than > necessary. (this is no way specific to Novell or to the panel change in NLD10, which just seems to be a new menu applet) Let's put it another way: I'm a maintainer of some modules, working on my free time on GNOME. I'm trying to fix bugs, and if I find time, implement cool new features (most often small new features :/). Now, something with a lot of changes comes out. It looks really great. As a user, I'm pleased. As a contributor, I'm sad. While I'm struggling in day-to-day not-so-funny things, I'll probably have to review a big patch without having the fun of developing it. I'd have loved to give some input on the idea, and on the implementation. Maybe I would have said "no way", but "no way" means "I don't want this, but feel free to patch your version if you really want". I'm not saying it's bad to code some stuff in your corner. But please, please, please be nice to contributors: tell the people who work on some stuff what you might be doing, talk to them, ask them what they think. You don't need to mail d-d-l to get input on some change. Someone on irc wrote something like "GNOME is first a software writing project, and then love". This is so wrong. Don't ignore the community. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/7/06, Dan Winship <[EMAIL PROTECTED]> wrote: > So to sum up: design by committee is bad, endless debates that result in > code not actually being written are bad, design by very small teams is > good, software with a unified vision is good, trying out cool new UI > ideas is good, free code at least doesn't suck, and of course, for > Novell, not shipping NLD10 is bad. Totally agree, all those guys whining about developing out of alpha stage "behind closed doors" are just jealous about others doing cool stuff ;) Many projects could be more stable if only they hadn't been torn to pieces by indecision in the community. Or left rotting because talk of changes lead nowhere. Talk is cheap but if nobody codes, nothing happens. This has been discussed many times recently, but discussions that start with "hey, I wrote a patch to..." instead of with "hey, I just thought that..." will have a significantly better chance to actually have an effect. This is very visible in the usability list for example, since discussions there involve more non-coders than here for example. There's loads and loads of suggestions which might be good but nobody knows because nobody implemented it. Which is a shame. -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sorry State [Was: NLD10 and GNOME]
Em Qua, 2006-02-08 às 12:16 +1100, Jeff Waugh escreveu: > > > > Two words: "bike shed"[1]. Or actually, "stop energy"[2] works too. Your > > pick. > > This is a very sorry state of affairs for GNOME. But it is not only Novell > and its employees who have adopted this commons-sapping, community-tearing, > morally and intellectually lazy approach to open design and development in > GNOME. > > In contributing organisations, it is rationalised as a faster approach, a > way to avoid massive discussions about inanities, and top of the list in > these modern times, a way to avoid "design by committee" or "stop energy". > How on Earth *do* we manage design out in the open? It is easier to avoid > that question, in the name of getting things done. > > Outside the contributing organisations, it's appeased as something we have > to accept to get the cool stuff, and a side-effect of our ability to involve > contributing organisations, who have their own priorities. It sounds a lot > like, "don't bite the hand that feeds you", whether that hand is delivering > cool drops of code, or your pay packet. > > But ultimately, this is *killing our community*. > > And it must be fought. > > - Jeff > I think the process used by Novell is very common in the GNOME community (and Free Software in general). For example take metacity. Sawfish was the default window manager, so Havoc could have started a discussion "should-our-window-manager-be-like-this-instead". But he didn't; what he did was write metacity following the design he had in mind in a window manager. Metacity was included in GNOME because most people adopted it and agreed that Havoc's design was better for the default window manager. The menu layout we use today is another example. If people had gone on discussions about which is better - the foot or the "menu panel" - perhaps things would have gone nowhere. But someone wrote the "menu panel" and eventually it became the GNOME default. Ubuntu has also done some changes in the panel, like the 'Add to Panel' dialog. From what I remember this was first done in Ubuntu and after a release using that configuration discussion started on the usability list. Another example is the log out dialog on the right top corner of the screen in Dapper, which wasn't proposed for discussion on mail.gnome.org, it was just implemented there when GNOME uses the window selector for the top right corner. There are some people posting mockups of "GNOME 3" and to be honest I see very little discussion about them. People know (or learn) that unless they code these mockups or convince someone to do it then most likely nothing will happen. But if someone comes up with a different concept for the panel and translates that into code then the community will review and pick it up or reject it. Spending time discussing the design first would IMO be a waste of time if the person has it clear in their head what they want from this hypothetical new panel. The review process will still happen, just not before the design. The design might even have small changes after suggestions from the community, but the basic idea of the original author is what makes this good or bad design. I'm not sure I agree that "you can't do design by comittee" but I would agree that a lot of the good design decisions we see in GNOME today came from only a few coders doing their vision. I'd love to play with the code as soon as possible but maybe there are other reasons for it not being released yet. What GNOME can do is encourage the companies making changes in their development branches to at least commit the patches in a CVS branch. There's also the issue of who you target with the changes. Novell might find in a usability test that the menu they designed is a lot better for their target audience but most people in the GNOME community would reject it in favor of the current panel layout (I'm one for example). Should that stop Novell from doing what's best for their customers (people used to Windows but now using GNOME because their company went with NLD)? My 2c. Cheers, Evandro ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Sorry State [Was: NLD10 and GNOME]
> Two words: "bike shed"[1]. Or actually, "stop energy"[2] works too. Your > pick. This is a very sorry state of affairs for GNOME. But it is not only Novell and its employees who have adopted this commons-sapping, community-tearing, morally and intellectually lazy approach to open design and development in GNOME. In contributing organisations, it is rationalised as a faster approach, a way to avoid massive discussions about inanities, and top of the list in these modern times, a way to avoid "design by committee" or "stop energy". How on Earth *do* we manage design out in the open? It is easier to avoid that question, in the name of getting things done. Outside the contributing organisations, it's appeased as something we have to accept to get the cool stuff, and a side-effect of our ability to involve contributing organisations, who have their own priorities. It sounds a lot like, "don't bite the hand that feeds you", whether that hand is delivering cool drops of code, or your pay packet. But ultimately, this is *killing our community*. And it must be fought. - Jeff -- II OSWC: Malaga, Spain http://www.opensourceworldconference.com/ "You put on the pants, and the pants start telling you what to do." - Bono ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/7/06, Miguel de Icaza <[EMAIL PROTECTED]> wrote: > Hey, > > > Here's a heart felt thank you from one person for avoiding this. :) > > However, that seems to apply more to e.g. the panel changes. I'm > > curious about the joint window-manager/compositing manager ("compiz") > > you were working on as it sounds like duplication of Soeren's work and > > something that largely wouldn't be affected by the bike shed stuff, at > > least not if the work & discussion were restricted to the core gl part > > excluding plugins. > > My understanding while talking to David Reveman this past week was that > the complexity of keeping a compositing manager as a separate process > from the window manager was too high (too much bookkeeping that made it > error prone, and there were some fundamental problems that he could not > solve). > > So some time ago he abandoned his effort to patch Metacity and have a > separate composition manager, reduced the complexity and eliminated a > lot of bugs and the source of these bugs. Right, but this sounds similar to what Soeren did/is doing -- he's building a compositing manager inside metacity, and has merged many of the changes into head now (this is disabled by default, though). So, we have two merged window manager + compositing manager codebases now. My question is whether and how we can merge these. > That is what David explained to me, but I can only understand about 50% > of the technical stuff that he talks about, so keep that in mind. Yeah, I don't know the technical details of the compositing side either (I've been meaning to help out with it at some point, but there's so many other bugs to fix...). I guess we just need Soeren and David to get together and figure it out. :) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/7/06, Dan Winship <[EMAIL PROTECTED]> wrote: > Luis Villa wrote: > > On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: > >> The changes that were implemented were not as radical as the > >> mockups. Basically what Nat F. showed in Paris is what was > >> implemented. The code will be released to the community soon. > > > > To ask the obvious question, why not now, and why not discussed > > publicly earlier? I should have been not quite so hasty and added 'and if the answers are real problems (which I think they probably are) any suggestions on how to solve them?' I'm swamped at work, so I can't go into much detail ATM, but it seems like these are very real issues we need to solve... Luis > So here's my (ie, not Novell's) answer. > > Two words: "bike shed"[1]. Or actually, "stop energy"[2] works too. Your > pick. > > Although the changes aren't nearly as radical as the original mockups, > they are a big change from the current GNOME panel menu. If we had > proposed the changes on the mailing lists, it would have started a huge > discussion about what people hated about the design ("you can't make the > panel menu depend on beagle!!!") and how it should be different. And > then we could have either (a) completely ignored everyone and done it > ourselves anyway, or (b) had a long conversation about the merits of the > design and then not actually finished the code in time for NLD10. > > So we did it ourselves, and now either GNOME will like what we did, in > which case, yay, free code for GNOME, or GNOME won't like what we did, > in which case, no harm no foul for GNOME, and yay, brand differentiation > for Novell. (And anyone who yells "fork" deserves to get one stuck in them.) > > > An equivalent answer to the question is "because you can't do design by > committee". Everything good in GNOME is good because one person or a > small number of people working closely together made it good. Much of > what is bad in GNOME is bad because lots of people have contributed > without having a single vision of what the end result is supposed to be. > I mean, look at the stuff John Williams has been blogging about the last > week[3]: > > * Evolution's UI blocking on I/O SUCKS. Due to lack of design in the > early stages of development > > * Evolution's integration with gaim and tomboy RULES. Both of these > happened because specific people (ChipX86, orph) made them happen. > > * Multimedia integration SUCKS. No one has ever sat down and tried > to fix the big picture. (Although I think the gstreamer team is in > the process of doing this now?) > > * Apps not remembering their window size and position SUCKS. Again, > needs someone to take this problem and make it their own. I > remember xkahn was trying to fix this a few years ago, but never > finished. > > * Bug-buddy SUCKS. Jacob's original UI was simple and brilliant. But > as more and more people added more and more features without > looking at the big picture, it got unwieldy. (But now a small > team is putting the simplicity back in again.) > > * Deskbar applet RULES (kikidonk), dashboard RULES (Nat), and beagle > RULES (trow and joe). None of these was done *exclusively* by > those people, but each of them reflects one person's (or a few > people's) vision, as opposed to the current state of bug buddy, > which just sort of happened. > > This is just another aspect of the UI "simplicity" thing. We like UIs > that try to do the right thing (metacity, epiphany/firefox, evince) > rather than UIs that try to make every possible user happy > (enlightenment, mozilla, gpdf/acroread). If you try to design something > by committee, you either have to end up with the latter sort of messy > does-everything UI, or you ignore and hence piss off a large chunk of > the committee. > > And that's where we are with NLD. There is no way that everyone in the > GNOME community is going to like the changes we wanted to make. But we > did the user testing, and we believe in it, and we want to make the > changes anyway. So we're doing it. Maybe it will turn out good, and > maybe it will turn out bad. Either way, the GNOME community learns from > it. Think of it like this: wouldn't it have been cool if we could have > tried out spatialus on our users, found out that they hated it, and then > reverted back to browserlus, without ever having to actually piss off > our users? This is essentially what is going to happen with NLD10. If > Novell's customers like the NLD changes, then GNOME can adopt them. If > Novell's customers don't like the changes, then GNOME can stand off to > the side and say "yeah well, we never liked that UI anyway. Not at all > like how we would have done it." :-) > > But some people will still say "But couldn't you have discussed it with > the community before doing it?" No, we couldn't. If we had, it would > either not have happened, or it would have suc
Re: NLD10 and GNOME
Hey, > Here's a heart felt thank you from one person for avoiding this. :) > However, that seems to apply more to e.g. the panel changes. I'm > curious about the joint window-manager/compositing manager ("compiz") > you were working on as it sounds like duplication of Soeren's work and > something that largely wouldn't be affected by the bike shed stuff, at > least not if the work & discussion were restricted to the core gl part > excluding plugins. My understanding while talking to David Reveman this past week was that the complexity of keeping a compositing manager as a separate process from the window manager was too high (too much bookkeeping that made it error prone, and there were some fundamental problems that he could not solve). So some time ago he abandoned his effort to patch Metacity and have a separate composition manager, reduced the complexity and eliminated a lot of bugs and the source of these bugs. That is what David explained to me, but I can only understand about 50% of the technical stuff that he talks about, so keep that in mind. Miguel. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Dan, I agree on 99.9% of your mail, seriously, except one little line: > dashboard RULES (Nat) IIRC Dashboard didn't compile some time ago (was some discussion on it on dashboard-list), afaik no (stock) apps work with it,... Or have you guys been fixing that too recently? :D I can't wait to get all great stuff Novell got out there on my desktop... There should be some good way to say "Thank you". Kind regards, Ikke http://www.eikke.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/7/06, Dan Winship <[EMAIL PROTECTED]> wrote: > Luis Villa wrote: > > On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: > >> The changes that were implemented were not as radical as the > >> mockups. Basically what Nat F. showed in Paris is what was > >> implemented. The code will be released to the community soon. > > > > To ask the obvious question, why not now, and why not discussed > > publicly earlier? > > So here's my (ie, not Novell's) answer. > > Two words: "bike shed"[1]. Here's a heart felt thank you from one person for avoiding this. :) However, that seems to apply more to e.g. the panel changes. I'm curious about the joint window-manager/compositing manager ("compiz") you were working on as it sounds like duplication of Soeren's work and something that largely wouldn't be affected by the bike shed stuff, at least not if the work & discussion were restricted to the core gl part excluding plugins. I'm not trying to come across as accusing, I'm just wondering whether there was duplicated effort and if so whether there's a possibility of merging now or if we have a real fork for this particular part of the desktop. Thanks, Elijah ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Luis Villa wrote: > On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: >> The changes that were implemented were not as radical as the >> mockups. Basically what Nat F. showed in Paris is what was >> implemented. The code will be released to the community soon. > > To ask the obvious question, why not now, and why not discussed > publicly earlier? So here's my (ie, not Novell's) answer. Two words: "bike shed"[1]. Or actually, "stop energy"[2] works too. Your pick. Although the changes aren't nearly as radical as the original mockups, they are a big change from the current GNOME panel menu. If we had proposed the changes on the mailing lists, it would have started a huge discussion about what people hated about the design ("you can't make the panel menu depend on beagle!!!") and how it should be different. And then we could have either (a) completely ignored everyone and done it ourselves anyway, or (b) had a long conversation about the merits of the design and then not actually finished the code in time for NLD10. So we did it ourselves, and now either GNOME will like what we did, in which case, yay, free code for GNOME, or GNOME won't like what we did, in which case, no harm no foul for GNOME, and yay, brand differentiation for Novell. (And anyone who yells "fork" deserves to get one stuck in them.) An equivalent answer to the question is "because you can't do design by committee". Everything good in GNOME is good because one person or a small number of people working closely together made it good. Much of what is bad in GNOME is bad because lots of people have contributed without having a single vision of what the end result is supposed to be. I mean, look at the stuff John Williams has been blogging about the last week[3]: * Evolution's UI blocking on I/O SUCKS. Due to lack of design in the early stages of development * Evolution's integration with gaim and tomboy RULES. Both of these happened because specific people (ChipX86, orph) made them happen. * Multimedia integration SUCKS. No one has ever sat down and tried to fix the big picture. (Although I think the gstreamer team is in the process of doing this now?) * Apps not remembering their window size and position SUCKS. Again, needs someone to take this problem and make it their own. I remember xkahn was trying to fix this a few years ago, but never finished. * Bug-buddy SUCKS. Jacob's original UI was simple and brilliant. But as more and more people added more and more features without looking at the big picture, it got unwieldy. (But now a small team is putting the simplicity back in again.) * Deskbar applet RULES (kikidonk), dashboard RULES (Nat), and beagle RULES (trow and joe). None of these was done *exclusively* by those people, but each of them reflects one person's (or a few people's) vision, as opposed to the current state of bug buddy, which just sort of happened. This is just another aspect of the UI "simplicity" thing. We like UIs that try to do the right thing (metacity, epiphany/firefox, evince) rather than UIs that try to make every possible user happy (enlightenment, mozilla, gpdf/acroread). If you try to design something by committee, you either have to end up with the latter sort of messy does-everything UI, or you ignore and hence piss off a large chunk of the committee. And that's where we are with NLD. There is no way that everyone in the GNOME community is going to like the changes we wanted to make. But we did the user testing, and we believe in it, and we want to make the changes anyway. So we're doing it. Maybe it will turn out good, and maybe it will turn out bad. Either way, the GNOME community learns from it. Think of it like this: wouldn't it have been cool if we could have tried out spatialus on our users, found out that they hated it, and then reverted back to browserlus, without ever having to actually piss off our users? This is essentially what is going to happen with NLD10. If Novell's customers like the NLD changes, then GNOME can adopt them. If Novell's customers don't like the changes, then GNOME can stand off to the side and say "yeah well, we never liked that UI anyway. Not at all like how we would have done it." :-) But some people will still say "But couldn't you have discussed it with the community before doing it?" No, we couldn't. If we had, it would either not have happened, or it would have sucked. It's inevitable. It's not a problem with the GNOME community, it's a problem with communities in general. The wisdom of crowds[4] only works in situations where there are clear right and wrong answers. If you try to apply it to a design problem, where there are many entirely different right answers, then you end up with a wrong answer. Always[5]. So to sum up: design by committee is bad, endless debates that result in code not actually being written are bad, design by very small teams
Re: NLD10 and GNOME
Christian Fredrik Kalager Schaller wrote: Hi, While it would be good to get fixes and improvements right away I do think its to hard to criticize anyone for holding back a bit on things they are doing. Being able to ship something first is an important marketing tool and this has happened before. In most cases where it has happened the distribution makers have been good at working with the community afterwards to get their changes merged upstream. Remember getting those changes merged in is in their interest too as keeping a larger and larger diff maintained is very costly and time consuming, so I am sure nobody wants to keep the changes any longer than necessary. I agree and im not judging Novell here but merely being blunt in asking a direct question (and hopefully I will get a direct answer) My concern is that if this becomes the rule rather than the exception and if say Red Hat follows suit then it would make gnome development effectively untenable and increase the risk of forking. That said Novell is certainly due all the praise and credit they will no doubt get when things are released and no one wants to take that away from them. Perhaps we can find some middle ground here that keeps everyone happy? -- Mr Jamie McCracken http://www.advogato.org/person/jamiemcc/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Hi, While it would be good to get fixes and improvements right away I do think its to hard to criticize anyone for holding back a bit on things they are doing. Being able to ship something first is an important marketing tool and this has happened before. In most cases where it has happened the distribution makers have been good at working with the community afterwards to get their changes merged upstream. Remember getting those changes merged in is in their interest too as keeping a larger and larger diff maintained is very costly and time consuming, so I am sure nobody wants to keep the changes any longer than necessary. Sincerely, Christian On Tue, 2006-02-07 at 14:41 +, Jamie McCracken wrote: > Luis Villa wrote: > > On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: > >> On Tue, 2006-02-07 at 10:43 +, Jono Bacon wrote: > >>> Hi all, > >>> > >>> Just a quick question to anyone who may be in the know. After seeing > >>> the NLD10 videos, it seems the GNOME in there is rather similar to the > >>> mockups shown at http://www.flickr.com/photos/gamehack/sets/1506658/ > >> Indeed, these mockups were made internally at Novell by the UI team > >> (same guys that brought you betterdesktop). > >> > >>> I made a comparison in a blog post at > >>> http://www.jonobacon.org/viewcomments.php?id=637 to outline the point. > >>> > >>> Do we know if these radical changes to GNOME have been implemented, > >>> and if so, are the changes coming back to the community? > >> The changes that were implemented were not as radical as the mockups. > >> Basically what Nat F. showed in Paris is what was implemented. The code > >> will be released to the community soon. > > > > To ask the obvious question, why not now, and why not discussed > > publicly earlier? > > > > Ditto + do i take it the changes amount to a fork? (I assume as its > internal it does not have maintainer approval nor consensus?) > > To also be so blunt, is this a new strategy by Novell to keep new things > like these under wraps in order to steal a march on your competitors? > (if so I would be worried by this as it goes against the spirit of open > source where "open" is the definitive word - I would hate to see this > become common practice as if every gnome based organisation did this we > would end up in a mess as well as in the dark) > > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Luis Villa wrote: On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: On Tue, 2006-02-07 at 10:43 +, Jono Bacon wrote: Hi all, Just a quick question to anyone who may be in the know. After seeing the NLD10 videos, it seems the GNOME in there is rather similar to the mockups shown at http://www.flickr.com/photos/gamehack/sets/1506658/ Indeed, these mockups were made internally at Novell by the UI team (same guys that brought you betterdesktop). I made a comparison in a blog post at http://www.jonobacon.org/viewcomments.php?id=637 to outline the point. Do we know if these radical changes to GNOME have been implemented, and if so, are the changes coming back to the community? The changes that were implemented were not as radical as the mockups. Basically what Nat F. showed in Paris is what was implemented. The code will be released to the community soon. To ask the obvious question, why not now, and why not discussed publicly earlier? Ditto + do i take it the changes amount to a fork? (I assume as its internal it does not have maintainer approval nor consensus?) To also be so blunt, is this a new strategy by Novell to keep new things like these under wraps in order to steal a march on your competitors? (if so I would be worried by this as it goes against the spirit of open source where "open" is the definitive word - I would hate to see this become common practice as if every gnome based organisation did this we would end up in a mess as well as in the dark) -- Mr Jamie McCracken http://www.advogato.org/person/jamiemcc/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On 2/7/06, JP Rosevear <[EMAIL PROTECTED]> wrote: > On Tue, 2006-02-07 at 10:43 +, Jono Bacon wrote: > > Hi all, > > > > Just a quick question to anyone who may be in the know. After seeing > > the NLD10 videos, it seems the GNOME in there is rather similar to the > > mockups shown at http://www.flickr.com/photos/gamehack/sets/1506658/ > > Indeed, these mockups were made internally at Novell by the UI team > (same guys that brought you betterdesktop). > > > I made a comparison in a blog post at > > http://www.jonobacon.org/viewcomments.php?id=637 to outline the point. > > > > Do we know if these radical changes to GNOME have been implemented, > > and if so, are the changes coming back to the community? > > The changes that were implemented were not as radical as the mockups. > Basically what Nat F. showed in Paris is what was implemented. The code > will be released to the community soon. To ask the obvious question, why not now, and why not discussed publicly earlier? Luis ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
Hi JP, > Indeed, these mockups were made internally at Novell by the UI team > (same guys that brought you betterdesktop). Awesome. Good work. They seem to be going down rather well, from speaking to other people. > The changes that were implemented were not as radical as the mockups. > Basically what Nat F. showed in Paris is what was implemented. The code > will be released to the community soon. Thanks. :) Jono ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: NLD10 and GNOME
On Tue, 2006-02-07 at 10:43 +, Jono Bacon wrote: > Hi all, > > Just a quick question to anyone who may be in the know. After seeing > the NLD10 videos, it seems the GNOME in there is rather similar to the > mockups shown at http://www.flickr.com/photos/gamehack/sets/1506658/ Indeed, these mockups were made internally at Novell by the UI team (same guys that brought you betterdesktop). > I made a comparison in a blog post at > http://www.jonobacon.org/viewcomments.php?id=637 to outline the point. > > Do we know if these radical changes to GNOME have been implemented, > and if so, are the changes coming back to the community? The changes that were implemented were not as radical as the mockups. Basically what Nat F. showed in Paris is what was implemented. The code will be released to the community soon. -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
NLD10 and GNOME
Hi all, Just a quick question to anyone who may be in the know. After seeing the NLD10 videos, it seems the GNOME in there is rather similar to the mockups shown at http://www.flickr.com/photos/gamehack/sets/1506658/ I made a comparison in a blog post at http://www.jonobacon.org/viewcomments.php?id=637 to outline the point. Do we know if these radical changes to GNOME have been implemented, and if so, are the changes coming back to the community? Cheers, Jono ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list