Re: Team TODO pages
On Nov 29, 2007, at 10:05 AM, Daniel Holbach wrote: ... A page worth looking at is http://wiki.ubuntu.com/DesktopTeam/TODO - it includes https://wiki.ubuntu.com/DesktopTeam/WeeklyTODO which has a neat table overview over what's going on. The color code is derived from the release schedule page ... With editmoin it's very easy to add new tasks to the bottom by having a small script like this one: [EMAIL PROTECTED]:~$ cat bin/desktopteam-add echo ||rowbgcolor=\#FFEBBB\ $1 || || || | EDITOR=cat editmoin https://wiki.ubuntu.com/DesktopTeam/WeeklyTODO [EMAIL PROTECTED]:~$ The MOTU TODO pages use a different concept derived from the Hug Day Bug Lists, if you look at https://wiki.ubuntu.com/MOTU/TODO/Weekly/Bitesize?action=raw you'll notice that the tool hugdaylist (in the ubuntu-dev-tools package) was used to set it up. ... This seems to me like you've done a lot of careful work to implement a listing that Launchpad really should be able to do itself. :-) What would you need in Launchpad to make this wiki listing unnecessary? Mass tagging http://launchpad.net/bugs/76083 would let you add a thisweek or similar tag to multiple bugs at once. What else would you need? For example, how do you currently tell which Ubuntu bugs are Desktop Team bugs and which aren't? And do you record that a task is blocked anywhere other than in those wiki listings? Cheers -- Matthew Paul Thomas http://mpt.net.nz/ PGP.sig 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
Re: Failure starting X on hp 6715s laptop, ati x1250 graphics card, with alpha2
Pär Lidén par.liden at gmail.com writes: /etc/gdm/failsafeXserver: line 47: [: too many arguments Warning: Could not retrieve EDID because get-edid is not installed (1) open_sock(): Permission denied : error: this program dows not know how to configure the 10 shared/default-x-server doesn't exist X server Warning: Could not generate /etc/X11/xorg.conf.failsafe This is https://bugs.launchpad.net/bugs/174434 -- 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: Strawman: Change the Ubuntu Release Cycle
Pär Lidén wrote: Well, maybe there should be two different versions of the LTS release: One for the home-users where the applications are upgraded And another for corporate use, where they are not. /Pär As its been said many times before on this subject, having backports enabled accomplishes the same thing for users. If the backports team had more help, I'm sure this would be less of an issue. -Cory \m/ -- 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: VOIP: ekiga, wengophone, twinkle (was What is 'administrivia')
On Jan 2, 2008 6:23 AM, Fergal Daly [EMAIL PROTECTED] wrote: If your setup is relatively straight-forward or you are able to open ports on your firewall then you don't have be SIP expert to get it working - I know nothing about SIP I got it to work by following the docs, I'm going to go ahead and lose all my geek points now. I don't know how to open ports on my router. I certainly don't expect that any normal user does. -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com -my blog of Ubuntu stuff apt-get moo -- 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: VOIP: ekiga, wengophone, twinkle (was What is 'administrivia')
On 02/01/2008, Mackenzie Morgan [EMAIL PROTECTED] wrote: On Jan 2, 2008 6:23 AM, Fergal Daly [EMAIL PROTECTED] wrote: If your setup is relatively straight-forward or you are able to open ports on your firewall then you don't have be SIP expert to get it working - I know nothing about SIP I got it to work by following the docs, I'm going to go ahead and lose all my geek points now. I don't know how to open ports on my router. I certainly don't expect that any normal user does. Then I'm not sure how you got any of the other SIP clients to work. As I understand it, unless the machine yon which you are running the SIP client has a publicly accessible IP address, you will not be able to use SIP unless you have a way to twiddle your router. The problem is that the voice data travels in UDP packets directly between you and the other person on the call. If you don't have a public IP address - say you are using NAT with a wireless router then the packets will arrive at your router and it will not know what to do with them - they could be for any of the machines on your wireless network. If you open the port (or rather forward the port) on the router, you are telling your router, if any packets arrive on port number XYZ, send them to my computer. This will allow SIP to work for you and is independent of what SIP client you use. If one of you has a public IP address and the other a NATted one then if the NATted one startes sending the packets first, their router will see there is a conversation going on and allow the packets to flow. If both of you have NATted IP addresses then neither of you can start the conversation. With certain routers, there are tricks you can do to get around this but many many routers have no work around. Skype gets around this by sending your conversation through a 3rd computer out on the internet which has a publicly accessible IP address. All packets between the 2 chat clients go via this computer. So actually there are 2 UDP packet flows, which this 3rd computer joins together. You can also get around this if your router can run a SIP proxy. I'm curious if you got some other SIP client to work without problems. I had the same set of problems with twinkle as with ekiga, F -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com -my blog of Ubuntu stuff apt-get moo -- 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: VOIP: ekiga, wengophone, twinkle (was What is 'administrivia')
On 02/01/2008, Emmet Hikory [EMAIL PROTECTED] wrote: On Jan 3, 2008 2:02 AM, Fergal Daly wrote: Then I'm not sure how you got any of the other SIP clients to work. As I understand it, unless the machine yon which you are running the SIP client has a publicly accessible IP address, you will not be able to use SIP unless you have a way to twiddle your router. The other common option is to use STUN (1) supported by many consumer routers and VoIP clients. 1: http://en.wikipedia.org/wiki/Simple_traversal_of_UDP_over_NATs I have never had any luck with STUN and I've been using linksys and netgear routers which are pretty common but maybe I'm not doing it right, F -- Emmet HIKORY -- 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 -- 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: VOIP: ekiga, wengophone, twinkle (was What is 'administrivia')
On Wed, 2008-01-02 at 17:39 +1300, Jonathan Musther wrote: I've just been trying it for IM, you're right, it doesn't stand up - but it is better than Ekiga for VOIP stuf, or seems to be based on my early impressions. I also agree with your assessment of pidgin. I use Ekiga all the time with a few friends and it works great. -- 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: VOIP: ekiga, wengophone, twinkle (was What is 'administrivia')
Most Clients for X program just us UPnP these days, so most people are understandably spoiled by it. On Jan 2, 2008 12:02 PM, Fergal Daly [EMAIL PROTECTED] wrote: On 02/01/2008, Mackenzie Morgan [EMAIL PROTECTED] wrote: On Jan 2, 2008 6:23 AM, Fergal Daly [EMAIL PROTECTED] wrote: If your setup is relatively straight-forward or you are able to open ports on your firewall then you don't have be SIP expert to get it working - I know nothing about SIP I got it to work by following the docs, I'm going to go ahead and lose all my geek points now. I don't know how to open ports on my router. I certainly don't expect that any normal user does. Then I'm not sure how you got any of the other SIP clients to work. As I understand it, unless the machine yon which you are running the SIP client has a publicly accessible IP address, you will not be able to use SIP unless you have a way to twiddle your router. The problem is that the voice data travels in UDP packets directly between you and the other person on the call. If you don't have a public IP address - say you are using NAT with a wireless router then the packets will arrive at your router and it will not know what to do with them - they could be for any of the machines on your wireless network. If you open the port (or rather forward the port) on the router, you are telling your router, if any packets arrive on port number XYZ, send them to my computer. This will allow SIP to work for you and is independent of what SIP client you use. If one of you has a public IP address and the other a NATted one then if the NATted one startes sending the packets first, their router will see there is a conversation going on and allow the packets to flow. If both of you have NATted IP addresses then neither of you can start the conversation. With certain routers, there are tricks you can do to get around this but many many routers have no work around. Skype gets around this by sending your conversation through a 3rd computer out on the internet which has a publicly accessible IP address. All packets between the 2 chat clients go via this computer. So actually there are 2 UDP packet flows, which this 3rd computer joins together. You can also get around this if your router can run a SIP proxy. I'm curious if you got some other SIP client to work without problems. I had the same set of problems with twinkle as with ekiga, F -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com -my blog of Ubuntu stuff apt-get moo -- 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 -- Cheers, Bryan -- 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: LVM on hardy's live installer?
Op dinsdag 01-01-2008 om 12:28 uur [tijdzone -0500], schreef Mackenzie Morgan: On Jan 1, 2008 7:14 AM, Lex Hider [EMAIL PROTECTED] wrote: Is there any plans to enable LVM for the live cd installers for hardy? The Alternate CD has, as far as I'm aware, always had it, but I don't think the Live CD ever did. I think it was in the live-CD during development for some time, but never in a final release. -- Jan Claeys -- 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: Strawman: Change the Ubuntu Release Cycle
Op dinsdag 01-01-2008 om 14:07 uur [tijdzone -0500], schreef Mackenzie Morgan: Couldn't there be a LUM (linux-updated-modules) compiled for LTS to add support for newer hardware? It's called 'linux-backports-modules' and is available since gutsy. -- Jan Claeys -- 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: Strawman: Change the Ubuntu Release Cycle
oh cool. I didn't see that on the Gutsy release notes. Well, that doesn't help Dapper users, but for Hardy it should be very useful. On Jan 2, 2008 7:20 PM, Jan Claeys [EMAIL PROTECTED] wrote: Op dinsdag 01-01-2008 om 14:07 uur [tijdzone -0500], schreef Mackenzie Morgan: Couldn't there be a LUM (linux-updated-modules) compiled for LTS to add support for newer hardware? It's called 'linux-backports-modules' and is available since gutsy. -- Jan Claeys -- 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 -- Mackenzie Morgan Linux User #432169 ACM Member #3445683 http://ubuntulinuxtipstricks.blogspot.com -my blog of Ubuntu stuff apt-get moo -- 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: Strawman: Change the Ubuntu Release Cycle
On Wed, 2 Jan 2008 17:21:14 +0200 Pär Lidén [EMAIL PROTECTED] wrote: Well, maybe there should be two different versions of the LTS release: One for the home-users where the applications are upgraded And another for corporate use, where they are not. I've been following this thread and am curious how backports doesn't support this already? What could be changed to better solve this problem? Scott K -- 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: LVM on hardy's live installer?
On 03/01/08 12:29, Lex Hider wrote: Jan Claeys wrote: Op dinsdag 01-01-2008 om 12:28 uur [tijdzone -0500], schreef Mackenzie Morgan: On Jan 1, 2008 7:14 AM, Lex Hider [EMAIL PROTECTED] wrote: Is there any plans to enable LVM for the live cd installers for hardy? The Alternate CD has, as far as I'm aware, always had it, but I don't think the Live CD ever did. I think it was in the live-CD during development for some time, but never in a final release. I'm not that interested in whether or not previous releases had it. My main concern is: if it fairly simple to add LVM support to the live CD, can we implement it for the Hardy release? When I talk of LVM support, I don't mean by default, I mean having the option to mount my LVM partitions, or create new ones, through the custom partition dialogs. Lex. Rather than add these packages to the Live CD, I would suspect that a simple set of instructions would do the trick, as AFAIK apt-get install (et al.) is available to you on a Live CD, giving you the functionality you require. Of course I might be completely wrong :) -- Onno Benschop Connected via Optus B3 at S31°54'06 - E115°50'39 (Yokine, WA) -- ()/)/)()..ASCII for Onno.. |?..EBCDIC for Onno.. --- -. -. --- ..Morse for Onno.. ITmaze - ABN: 56 178 057 063 - ph: 04 1219 - [EMAIL PROTECTED] -- 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
