Re: Ubuntu development...
> > The fact that you submit bug reports and do not follow up / patch them > yourself > shows a severe disinterest in *really* helping ubuntu and (like most > new devel's in all projects) just want to focus on the hot-dog stuff. I do follow up - in fact, I've often posted additional info on my bug reports as to the origin of the issue/suggestions as to what could be done. I may not have the solution to everything, but that doesn't mean that I'm just being lazy or "just focusing on the hot-dog stuff". Maybe it means that for you, but I've submitted bugs/ideas to other projects (including *Debian*, of all distributions) and have received plenty of response. > > 2) RTFM. Please. Coming onto the mailing list and asking for manual > locations makes me want to knife myself. Yes it could be clearer, but > you are not asking for help or clarifying a point, your just being > lazy. I'm not asking for something trivial - I'm asking how to provide input/ideas regarding key components of the system. It's perfectly clear how to do MOTU/Bug Squad/etc - it's NOT clear how to go about suggesting changes to the main desktop setup. I've looked countless times on Launchpad and have remained stumped - "RTFM" really doesn't help one bit. 3) Before you start working on MAJOR new features, why not help fix > bugs and other common problems first? Wouldn't these be more benficial > and a better learning process than "Making the default system look > better"?. BTW the way it renders fonts is entirely appropriate: Most > people get used to MS's crappy way of sub-sampling fonts to make them > look sharper. In many of the cases I've discussed, I'm not necessarily talking about coding a major new project from scratch - I'm talking about integrating already existing code into the system, investigating changes in default settings, etc. Yes, I certainly would work on the smaller bugs/issues as well - and I already know where to go for that (Bug Squad, MOTU, etc etc). However, it's unclear where to go with basic desktop issues/ideas, other than to file a bug in Launchpad, provide all the info you can, and wait. Do any Ubuntu developers care to comment? I'd like to contribute, but I'm beginning to feel like I can't do so in any meaningful way outside the "universe" and Launchpad bug reports (which, even when I provide extensive info and narrow the problem to something fairly specific, don't tend to get much response). Tim -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
On Saturday 25 August 2007 12:57:21 Tim Hull wrote: > > The fact that you submit bug reports and do not follow up / patch them > > yourself > > shows a severe disinterest in *really* helping ubuntu and (like most > > new devel's in all projects) just want to focus on the hot-dog stuff. > > I do follow up - in fact, I've often posted additional info on my bug > reports as to the origin of the issue/suggestions as to what could be done. > I may not have the solution to everything, but that doesn't mean that I'm > just being lazy or "just focusing on the hot-dog stuff". Maybe it means > that for you, but I've submitted bugs/ideas to other projects (including > *Debian*, of all distributions) and have received plenty of response. > > > 2) RTFM. Please. Coming onto the mailing list and asking for manual > > locations makes me want to knife myself. Yes it could be clearer, but > > you are not asking for help or clarifying a point, your just being > > lazy. > > I'm not asking for something trivial - I'm asking how to provide > input/ideas regarding key components of the system. It's perfectly clear > how to do MOTU/Bug Squad/etc - it's NOT clear how to go about suggesting > changes to the main desktop setup. I've looked countless times on > Launchpad and have remained stumped - "RTFM" really doesn't help one bit. > > > 3) Before you start working on MAJOR new features, why not help fix > > > bugs and other common problems first? Wouldn't these be more benficial > > and a better learning process than "Making the default system look > > better"?. BTW the way it renders fonts is entirely appropriate: Most > > people get used to MS's crappy way of sub-sampling fonts to make them > > look sharper. > > In many of the cases I've discussed, I'm not necessarily talking about > coding a major new project from scratch - I'm talking about integrating > already existing code into the system, investigating changes in default > settings, etc. Yes, I certainly would work on the smaller bugs/issues as > well - and I already know where to go for that (Bug Squad, MOTU, etc etc). > However, it's unclear where to go with basic desktop issues/ideas, other > than to file a bug in Launchpad, provide all the info you can, and wait. > > > > Do any Ubuntu developers care to comment? I'd like to contribute, but I'm > beginning to feel like I can't do so in any meaningful way outside the > "universe" and Launchpad bug reports (which, even when I provide extensive > info and narrow the problem to something fairly specific, don't tend to get > much response). > > > > Tim Not a Ubuntu-Core developer or in fact someone who packages or anything but I'm suprised by the rudeness of the person who responded to Tim. WHy would he then want to still work for a community that treats him such. Im sorry you were dealt such a low blow via email Jonathan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
dcraw licence problem (causing problem for digikam/ufraw/rawstudio)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since 8.39 version of dcraw we have a problem (https://bugs.launchpad.net/ubuntu/+source/dcraw/+bug/86480) because author have changed licence. (look at http://cybercom.net/~dcoffin/dcraw/dcraw.c). Silently others programs may have by-passed this problem as digikam / ufraw / rawstudio. Can authors/maintainers tell us which version of dcraw is oncluded ? Or confirm that : ufraw 0.11 in Gutsy use 8.62 rawstudio 0.5.1+20070601 in Gutsy use 8.46 digikam 0.9.2 use libkdcraw1 0.1.1 in Gutsy which use 8.60 Debian devs are discussing also on this problem : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=431883 but i can't see any discussion with original author. Can we seriously take this problem and talk with Dave Coffin to resolve this ? I can't do that because my knowledge of licence is poor and my english poor too :p Taking care of photographers, and supporting their cameras is important for the popularity of Ubuntu. Best regards - -- Patrice Vetsel <[EMAIL PROTECTED]> Aka/Alias Kagou https://launchpad.net/people/vetsel-patrice gpg key: 0x15c094db -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG0JzxAGLykBXAlNsRAsMBAKCxDHvQfkvQ6nnpEPvW7+xpKYBnRQCgqZdz qwmqWOlkkq+YhAUBTmOGxUM= =AlFd -END PGP SIGNATURE- -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Heya! Wow, that previous response was quite harsh - that was probably why it was sent off-list. Tim Hull wrote: > I do follow up - in fact, I've often posted additional info on my bug > reports as to the origin of the issue/suggestions as to what could be done. > I may not have the solution to everything, but that doesn't mean that I'm > just being lazy or "just focusing on the hot-dog stuff". Maybe it means > that for you, but I've submitted bugs/ideas to other projects (including > *Debian*, of all distributions) and have received plenty of response. More developers tends to lead to more response. That's the way the world works, i'm afraid. If you know of people interested in doing some work with the bugs, please point them to the Bug Squad. > I'm not asking for something trivial - I'm asking how to provide input/ideas > regarding key components of the system. It's perfectly clear how to do > MOTU/Bug Squad/etc - it's NOT clear how to go about suggesting changes to > the main desktop setup. I've looked countless times on Launchpad and have > remained stumped - "RTFM" really doesn't help one bit. I'm still unsure which key components you want to change, or how you want to change them. You may want to clarify, because that will effect the answer you get. > In many of the cases I've discussed, I'm not necessarily talking about > coding a major new project from scratch - I'm talking about integrating > already existing code into the system, investigating changes in default > settings, etc. Yes, I certainly would work on the smaller bugs/issues as > well - and I already know where to go for that (Bug Squad, MOTU, etc etc). > However, it's unclear where to go with basic desktop issues/ideas, other > than to file a bug in Launchpad, provide all the info you can, and wait. Tim can work on whatever he likes - that's one of the advantages of free software. Of course, hopefully he'll fix any bugs in code that he writes, or any bugs that he sees along the way. > Do any Ubuntu developers care to comment? I'd like to contribute, but I'm > beginning to feel like I can't do so in any meaningful way outside the > "universe" and Launchpad bug reports (which, even when I provide extensive > info and narrow the problem to something fairly specific, don't tend to get > much response). A lot of conversation between developers (which is, what I suspect, that you're looking for at the moment) is done on IRC. You'd probably have to speak to the individual developers relating to what you want to work on. The lack of response to your emails is likely because they're still quite broad (in the area of what you want to do), and the developers tend to be busy people, so don't reply to everything. Hobbsee -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG0O0C7/o1b30rzoURAqpMAJ9kNbOHJg19qRQnx92M5GzJ7mjZ2QCffbTh 5Vg4m2LqSoDYGBkSmc/fAj0= =btwR -END PGP SIGNATURE- -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Default option for volume hotkeys (speakers/headphones)
Hi all, I am using Gutsy Tribe 5 and maintain one of the LaptopTesting pages. As such, I plugged in my headphones and tested the volume hotkeys. Nothing happens. The bug report is here: https://bugs.launchpad.net/bugs/63544 and is marked as invalid. The reason that it is marked invalid is that there is no consensus on how it should be fixed. The default at the moment, as I understand things, is that the volume hotkeys control the "Master" setting. This controls the speakers but not the headphones (despite the name). As I see it, there are at least three options: 1) Change the hotkeys to control both "Master" and "Headphones". This can manually be achieved by going into the preferences and Ctrl-clicking. 2) Change the hotkeys to control "PCM" (I understand that this would mean that the volume of sound from some applications would not be able to be altered) 3) Cleverly determine whether headphones are plugged in. If they are, make the hotkeys control "Headphones" and if they are not, control "Master". We are all aiming for an intuitive, user-friendly distribution. It is my personal opinion that, when somebody has headphones in and presses the volume hotkeys, they would expect the sound that they are hearing to change volume. One can always change the default in the preferences, but the default should make sense. What are the opinions of others on this? I would have thought that 1 was a better solution than we currently have, although it may not be the best. Regards, Aaron -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
On 8/25/07, Sarah Hobbs <[EMAIL PROTECTED]> wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Heya! > > Wow, that previous response was quite harsh - that was probably why it > was sent off-list. Just realized that. I'm still unsure which key components you want to change, or how you > want to change them. You may want to clarify, because that will effect > the answer you get. A few examples: (Please don't flame. I know some of these may sound stupid to seasoned developers, but they are just my ideas.) 1. The desktop task (meaning the default Ubuntu one, not Kubuntu or Xubuntu) doesn't contain adequate iPod support for syncing/transferring songs/etc. Rhythmbox has *some* support, but it is so bad it is almost worse than nothing (it transfers at ~USB 1.1 speeds, won't delete tracks, and has no sync). What I suggest here is either 1) including Banshee alongside/in place of Rhythmbox or 2) including GTKpod. 2. The current default fonts look dreadfully ugly. For one thing, they are MASSIVE (on Gutsy at least), and they use a type of hinting which makes them look quite ugly when compared to OS X. What I suggest here is to 1) revert the auto-DPI-detect/change to 11-pt font in Gutsy - things look much better in Feisty with the settngs where they were 2) investigate changing the default hinting to either autohinter or no hinting - this, while a little blurry, seems to look eons better than the "native" hinter. 3. Currently, each Ubuntu release is based on a new version of the core libraries and toolchain, synced from Debian testing/unstable. While this may mean that each version has the absolute latest and greatest, it also makes them more prone to stability issues and breaks the ABI every 6 months, which ends up requiring users to update more often because they want to run program X and the version they need is compiled against the new version Y of glibc. Why not base Ubuntu on Debian stable+backports (for latest GNOME, KDE, kernel, Firefox, OO.o, etc) instead? > > A lot of conversation between developers (which is, what I suspect, that > you're looking for at the moment) is done on IRC. You'd probably have > to speak to the individual developers relating to what you want to work > on. The lack of response to your emails is likely because they're still > quite broad (in the area of what you want to do), and the developers > tend to be busy people, so don't reply to everything. OK. I've actually seen you on IRC a few times. I figured that this may be the case, though I was looking for something along the lines of debian-devel (yes, ubuntu-devel exists, but it is mainly for semiprivate developer contact). Anyway, it's nice to see a developer respond. I'm still unsure about Ubuntu, but for other reasons besides that one e-mail. My main concern at the moment is that the Technical Board seems to decide much of what happens regarding the base Ubuntu distribution internally without much external discussion. Or at least that's what I've gathered from the web site, after looking deeper into all of this. I'm a big supporter of openness and transparency (just ask my student government), and this doesn't instill confidence in me. Tim -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
On Sun, 2007-08-26 at 00:26 -0400, Tim Hull wrote: > 2. The current default fonts look dreadfully ugly. For one thing, they > are MASSIVE (on Gutsy at least), and they use a type of hinting which > makes them look quite ugly when compared to OS X. What I suggest here > is to 1) revert the auto-DPI-detect/change to 11-pt font in Gutsy - > things look much better in Feisty with the settngs where they were 2) > investigate changing the default hinting to either autohinter or no > hinting - this, while a little blurry, seems to look eons better than > the "native" hinter. > On this point I'm wondering if this may be caused by CompositeByDefault, since running XGL on my laptop (non-free ATI drivers, no aiglx for me :( ) causes the font rendering to change and ends up with much larger fonts than regular Xorg. This happens regardless of whether a compositing window manager is being run or not. Perhaps an accelerated X server is the reason Gutsy fonts look bigger and uglier for you than Feisty? (I haven't changed the font preferences from the Ubuntu defaults) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
On 8/26/07, Chris Warburton <[EMAIL PROTECTED]> wrote: > > > On Sun, 2007-08-26 at 00:26 -0400, Tim Hull wrote: > > > 2. The current default fonts look dreadfully ugly. For one thing, they > > are MASSIVE (on Gutsy at least), and they use a type of hinting which > > makes them look quite ugly when compared to OS X. What I suggest here > > is to 1) revert the auto-DPI-detect/change to 11-pt font in Gutsy - > > things look much better in Feisty with the settngs where they were 2) > > investigate changing the default hinting to either autohinter or no > > hinting - this, while a little blurry, seems to look eons better than > > the "native" hinter. > > > On this point I'm wondering if this may be caused by CompositeByDefault, > since running XGL on my laptop (non-free ATI drivers, no aiglx for > me :( ) causes the font rendering to change and ends up with much larger > fonts than regular Xorg. This happens regardless of whether a > compositing window manager is being run or not. Perhaps an accelerated X > server is the reason Gutsy fonts look bigger and uglier for you than > Feisty? (I haven't changed the font preferences from the Ubuntu > defaults) > That is because Ubuntu still doesn't make any radical changes into their choice of font rendering. It's still using "Native" hinting, versus "Autohinter" rendering (which is default in Fedora). I think here's what we need to do, we need to have "*orders signed in triplicate, sent in, sent back, queried, lost, found, subjected to public enquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters." *for the Ubuntu guys to change it. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubuntu development...
On Sun, 2007-08-26 at 05:41 +0100, Chris Warburton wrote: > On Sun, 2007-08-26 at 00:26 -0400, Tim Hull wrote: > > > 2. The current default fonts look dreadfully ugly. For one thing, they > > are MASSIVE (on Gutsy at least), and they use a type of hinting which > > makes them look quite ugly when compared to OS X. What I suggest here > > is to 1) revert the auto-DPI-detect/change to 11-pt font in Gutsy - > > things look much better in Feisty with the settngs where they were 2) > > investigate changing the default hinting to either autohinter or no > > hinting - this, while a little blurry, seems to look eons better than > > the "native" hinter. > > > On this point I'm wondering if this may be caused by CompositeByDefault, > since running XGL on my laptop (non-free ATI drivers, no aiglx for > me :( ) causes the font rendering to change and ends up with much larger > fonts than regular Xorg. This happens regardless of whether a > compositing window manager is being run or not. Perhaps an accelerated X > server is the reason Gutsy fonts look bigger and uglier for you than > Feisty? (I haven't changed the font preferences from the Ubuntu > defaults) > This is possibly an artifact of incorrect DPI reporting by Xgl, if indeed it's only apparent under Xgl. I've got a new xgl package in the works, waiting for review [1]. Once that's hit, I'd be very interested in hearing whether you still see this behaviour - it should be easy to fix if it's still apparent. [1] https://bugs.launchpad.net/ubuntu/+source/xserver-xgl/+bug/126255 signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
