Tentative CSUN hackfest schedule?
Hi all. I'm trying to work out my flights for the a11y hackfest at CSUN. I suspect a schedule, tentative or otherwise, would not be quite hackfestish. :-) Therefore, is there a feel for what is likely to take place on the 21st and/or 27th? Thanks in advance! Take care. --joanie ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Tentative CSUN hackfest schedule?
The CSUN conference is officially between the 22nd and 27th, so why don't we align it with those dates? That comes out to 5 nights I believe. I counted the spaces between my fingers a few times now. Cheers, Eitan. On Mon, 2010-02-01 at 10:44 -0500, Joanmarie Diggs wrote: Hi all. I'm trying to work out my flights for the a11y hackfest at CSUN. I suspect a schedule, tentative or otherwise, would not be quite hackfestish. :-) Therefore, is there a feel for what is likely to take place on the 21st and/or 27th? Thanks in advance! Take care. --joanie ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Tentative CSUN hackfest schedule?
Thanks Eitan. Given that I'm looking at 9 to 14 hours travel time depending on layovers and the like, I'm planning on arriving on the 21st. Any ideas/plans about the 27th? --joanie On Mon, 2010-02-01 at 16:21 +, Eitan Isaacson wrote: The CSUN conference is officially between the 22nd and 27th, so why don't we align it with those dates? That comes out to 5 nights I believe. I counted the spaces between my fingers a few times now. Cheers, Eitan. On Mon, 2010-02-01 at 10:44 -0500, Joanmarie Diggs wrote: Hi all. I'm trying to work out my flights for the a11y hackfest at CSUN. I suspect a schedule, tentative or otherwise, would not be quite hackfestish. :-) Therefore, is there a feel for what is likely to take place on the 21st and/or 27th? Thanks in advance! Take care. --joanie ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: Tentative CSUN hackfest schedule?
Joanie, all, While conference events start on March 21st with evening pre-conference registration, the exhibit floor is open Wednesday the 24th through Saturday the 27th and general (non-pre-conference) sessions are also from the 24th to the 27th. See http://www.csunconference.org/index.cfm?EID=8218p=149page=TextECTID=490#schedule I suggest we either have hackfest activities during the period of 24-27, or perhaps the day before (the 23rd) if we don't want to oppose activities that may draw folks we otherwise want to have at the hackfest. Note too the keynote address welcome reception is the evening of the 23rd; we shouldn't do anything opposite that time slot. Regards, Peter Korn Accessibility Architect Principal Engineer, Sun Microsystems, Inc. Thanks Eitan. Given that I'm looking at 9 to 14 hours travel time depending on layovers and the like, I'm planning on arriving on the 21st. Any ideas/plans about the 27th? --joanie On Mon, 2010-02-01 at 16:21 +, Eitan Isaacson wrote: The CSUN conference is officially between the 22nd and 27th, so why don't we align it with those dates? That comes out to 5 nights I believe. I counted the spaces between my fingers a few times now. Cheers, Eitan. On Mon, 2010-02-01 at 10:44 -0500, Joanmarie Diggs wrote: Hi all. I'm trying to work out my flights for the a11y hackfest at CSUN. I suspect a schedule, tentative or otherwise, would not be quite hackfestish. :-) Therefore, is there a feel for what is likely to take place on the 21st and/or 27th? Thanks in advance! Take care. --joanie ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
GNOME 2.30: go stable or go cutting edge?
Hi All: GNOME 2.30 is coming out on the Ides of March (March 15). I have one main question for you: do you want it to be stable or do you want it to have more cutting edge stuff? This question is predicated on the assumption that GNOME 2.30 is the last of the GNOME 2 releases and GNOME 3 is coming out this fall. It also assumes that we will resolve the harder problems we currently have with AT-SPI/D-Bus very soon. Here's the background -- GNOME Accessibility has been facing a perfect storm for the GNOME 2.30 cycle. The three major fronts of this storm are: Bonobo/CORBA elimination, WebKit accessibility, and GNOME Shell accessibility. You can read a lengthy summary of the current state of the work at http://live.gnome.org/Accessibility/GNOME3. Here's some pros/cons. Note that the quantity of pros/cons doesn't necessarily mean anything. They are just talking points, and actually quite simple at that. PROS/CONS for going with the cutting edge: == PRO: GNOME accessibility may be more widely available on smaller/mobile devices -- those devices are happy to have D-Bus but do not want CORBA. PRO: The cutting edge stuff will likely get more testing coverage for GNOME 3.0, helping improve the GNOME 3.0 accessibility experience. PRO: We will be able to eliminate a huge portion of deprecated stuff in GNOME. CON: GNOME 2.30 accessibility could very well be unstable or slow for day-to-day use for doing your job or functioning in life. Staying on GNOME 2.28.x would be recommended for people who need more stability. CON: GOK will not work. OnBoard and an early form of Caribou would be the on screen keyboard solutions. PROS/CONS for staying stable: = PRO: Users should still be able to use GNOME 2.30 with the same stability and reliability they get with GNOME 2.28.x. PRO: GOK will work. CON: The testing of cutting edge stuff may not be as broad, so GNOME 3.0 may go out without as much testing as it needs. CON: GNOME will need to continue to carry Bonobo/CORBA around. CON: GNOME accessibility will remain unavailable on smaller/mobile devices that do not ship Bonobo/CORBA. My first concern is the end user. As a result, I tend to be more conservative and lean towards stability. That is, making sure GNOME provides a compelling accessible desktop for reliable and usable day-to-day activity goes a long way to addressing the needs of the user. With this, we're likely to say GNOME 3.0 will be more wrinkled in terms of accessibility and we could look to GNOME 3.2 and 3.4 to iron things out. However, given where we are with proximity to GNOME 3, I'm also tempted by the notion of getting the new stuff out there sooner. This would potentially forsake the accessibility of the last (or one of the last) releases of the GNOME 2 series while helping set us up for an earlier accessibility success for GNOME 3. Please, speak up with your thoughts. The collective opinion of our group matters and it will help shape what recommendations we will make to the release team for GNOME 2.30. Will ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: GNOME 2.30: go stable or go cutting edge?
On Mon, Feb 01, 2010 at 11:54:19AM PST, Willie Walker wrote: Hi All: GNOME 2.30 is coming out on the Ides of March (March 15). I have one main question for you: do you want it to be stable or do you want it to have more cutting edge stuff? This question is predicated on the assumption that GNOME 2.30 is the last of the GNOME 2 releases and GNOME 3 is coming out this fall. It also assumes that we will resolve the harder problems we currently have with AT-SPI/D-Bus very soon. Ubuntu Lucid ships with GNOME 2.30, we are keeping CORBA around, since we still use evolution 2.28 for one. So from an LTS distro and a11y maintainer POV, I would prefer GNOME 2.30 remains accessibility enabled and aims for stability. The First one or two releases of Ubuntu after this LTS will likely have crack of the day content, which will be a good testing ground for GNOME3/accessibility bug squashing. Luke ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: GNOME 2.30: go stable or go cutting edge?
at-spi2 has been put into OpenSolaris' development releases. But I can't put it into stable release without http://defect.opensolaris.org/bz/show_bug.cgi?id=13438 fixed. I believe this is a at-spi and at-spi2 co-exist bug. And we still have not run a full test for CORBA based accessibility under GNOME2.29, not sure if there will be any new bugs. So I'd prefer we go stable for GNOME 2.30. And we still have development releases for users and developers to test D-Bus stuff. Li On Mon, 2010-02-01 at 14:54 -0500, Willie Walker wrote: Hi All: GNOME 2.30 is coming out on the Ides of March (March 15). I have one main question for you: do you want it to be stable or do you want it to have more cutting edge stuff? This question is predicated on the assumption that GNOME 2.30 is the last of the GNOME 2 releases and GNOME 3 is coming out this fall. It also assumes that we will resolve the harder problems we currently have with AT-SPI/D-Bus very soon. Here's the background -- GNOME Accessibility has been facing a perfect storm for the GNOME 2.30 cycle. The three major fronts of this storm are: Bonobo/CORBA elimination, WebKit accessibility, and GNOME Shell accessibility. You can read a lengthy summary of the current state of the work at http://live.gnome.org/Accessibility/GNOME3. Here's some pros/cons. Note that the quantity of pros/cons doesn't necessarily mean anything. They are just talking points, and actually quite simple at that. PROS/CONS for going with the cutting edge: == PRO: GNOME accessibility may be more widely available on smaller/mobile devices -- those devices are happy to have D-Bus but do not want CORBA. PRO: The cutting edge stuff will likely get more testing coverage for GNOME 3.0, helping improve the GNOME 3.0 accessibility experience. PRO: We will be able to eliminate a huge portion of deprecated stuff in GNOME. CON: GNOME 2.30 accessibility could very well be unstable or slow for day-to-day use for doing your job or functioning in life. Staying on GNOME 2.28.x would be recommended for people who need more stability. CON: GOK will not work. OnBoard and an early form of Caribou would be the on screen keyboard solutions. PROS/CONS for staying stable: = PRO: Users should still be able to use GNOME 2.30 with the same stability and reliability they get with GNOME 2.28.x. PRO: GOK will work. CON: The testing of cutting edge stuff may not be as broad, so GNOME 3.0 may go out without as much testing as it needs. CON: GNOME will need to continue to carry Bonobo/CORBA around. CON: GNOME accessibility will remain unavailable on smaller/mobile devices that do not ship Bonobo/CORBA. My first concern is the end user. As a result, I tend to be more conservative and lean towards stability. That is, making sure GNOME provides a compelling accessible desktop for reliable and usable day-to-day activity goes a long way to addressing the needs of the user. With this, we're likely to say GNOME 3.0 will be more wrinkled in terms of accessibility and we could look to GNOME 3.2 and 3.4 to iron things out. However, given where we are with proximity to GNOME 3, I'm also tempted by the notion of getting the new stuff out there sooner. This would potentially forsake the accessibility of the last (or one of the last) releases of the GNOME 2 series while helping set us up for an earlier accessibility success for GNOME 3. Please, speak up with your thoughts. The collective opinion of our group matters and it will help shape what recommendations we will make to the release team for GNOME 2.30. Will ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
Re: GNOME 2.30: go stable or go cutting edge?
I'm afraid the performance of Firefox is very bad with AT-SPI2. We need to fix it before end-user gets it. Firefox tries to send children-changed event for every child add/remove, AT-SPI2 tries to update the whole children set when it gets a children-changed event. I'm wondering if there're enough testing for Firefox + AT-SPI2. Ginn ___ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
