My apologys for my recent developer panic attack
Sorry all for the way I must have come off in my prior message. But like I just stated in the previous message, I just don't want to see the time Bill took to get things that now work better than in the present day Ubuntu in my personal opinion such as Pulse audio, to suddenly go backwards and stop working due to so many developpers working on the project. How will the development team be kept together with so many people doing daily builds? As Canonical won't be building the disks, is Bill supposed to build them all then? especially if daily builds are beginning to show up? Luke, perhaps you could help to clarify. I'm more than a bit confused-I suppose. Thanks! -- Regards, --Keith Skype: skypedude1234 MSN Messenger: keithin...@hotmail.com Yahoo/AIM/Twitter: keithint1234 Facebook: http://facebook.com/keith.hinton1 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: does maverick contain a working at-spi2 infrastrcture?
On Thu, Jun 10, 2010 at 03:45:01PM EST, Halim Sahin wrote: > Hi Luke, > > Just wondering about this decision: > maverick will ship gnome 3.0 right? > gnome 3 doesn't ship bonobo and other stuff so I am interested to know > how you can reintegrate bonobo there. Ubuntu Maverick will not be shipping everything from GNOME 3, we will still have pieces that require bonobo, particularly gnome panel. Since the GNOME/GTK/bonobo framework is used by several different Ubuntu variants, things have to be managed conservatively, so things don't break too badly for everyone at once. There is also code maturity from upstrea to consider. As for at-spi2 packages, I should have them ready to go in a PPA later today for maverick and lucid. Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Vinux to be used as Ubuntu Accessibility testing platform.
Hi all I may have told a few people here and there over the past few weeks, but I have decided to use Vinux as a test platform for accessibility related features. The plan is to test such features, make sure they are well implemented, and then as time and code/setup maturity permits, they will be merged into the main Ubuntu distribution proper. This work will start by moving Vinux disk building over to a the same framework used to build official Ubuntu CDs. Canonical won't be building the disks, but I know how to set up the framework. This will allow for much easier development of Vinux, and allow for much more rapid development, as there will be the opportunity for daily builds, basing different builds on different Ubuntu releases, etc. Regards Luke -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
