Re: [Fwd: [u-a-dev] What can the Mozilla Team do?]

2007-02-22 Thread Alex Latchford
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Daniel Holbach wrote:
> Hello Will,
> 
> thanks for all the enlightening words. I wasn't aware of what was going
> on in orca-firefox land.
> 
> On Di, 2007-02-20 at 10:22 -0500, Willie Walker wrote:
>> For what the Mozilla team can do?  I'd say throw more capable bodies at 
>> it.  Work with Aaron Leventhal - I'm sure he has no shortage of stuff 
>> for people to do.  The caret navigation needs work.  The AT-SPI 
>> implementation in Gecko needs completion, testing, and should attempt to 
>> behave as much like the GTK+/GAIL implementation as possible.
> 
> I think Alex was more referring to the Ubuntu Mozilla team, which
> maintains the Mozilla suite in Ubuntu and liaises with Upstream.
> 
> 
> My own opinion is that, 
>   * adding a tag is cool,
>   * subscribing the 'accessibility' team, if there's any input you
> need from us or anything that needs accessibility testing.
>   * maybe point out how to forward those kinds of bugs upstream,
>   * also point out how to get more data than "doesn't work with
> version ".
> 
> That's all I can think of for now as I don't know enough about the
> nature of Mozilla Accessibility bug reports.
> 
> Thanks a lot for all your efforts.
> 
> Have a nice day,
>  Daniel
> 
> 


Howdy guys,

Thanks for the comments, I have forwarded these comments onto the
Mozilla Team list, we are going to discuss the best way to move forward
with tagging accessibility issues on the mailing list and probably at
the next meeting.

Thanks again, Alex.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF3hGHoqGssgr3yPYRAvPYAJ4oMojVIQsSoNFnmmZSkhSfza3HjwCggm5o
mv+gSqx6KMmT9F9Zahm3aMo=
=Cuz5
-END PGP SIGNATURE-

-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: [Fwd: [u-a-dev] What can the Mozilla Team do?]

2007-02-20 Thread Daniel Holbach
Hello Will,

thanks for all the enlightening words. I wasn't aware of what was going
on in orca-firefox land.

On Di, 2007-02-20 at 10:22 -0500, Willie Walker wrote:
> For what the Mozilla team can do?  I'd say throw more capable bodies at 
> it.  Work with Aaron Leventhal - I'm sure he has no shortage of stuff 
> for people to do.  The caret navigation needs work.  The AT-SPI 
> implementation in Gecko needs completion, testing, and should attempt to 
> behave as much like the GTK+/GAIL implementation as possible.

I think Alex was more referring to the Ubuntu Mozilla team, which
maintains the Mozilla suite in Ubuntu and liaises with Upstream.


My own opinion is that, 
  * adding a tag is cool,
  * subscribing the 'accessibility' team, if there's any input you
need from us or anything that needs accessibility testing.
  * maybe point out how to forward those kinds of bugs upstream,
  * also point out how to get more data than "doesn't work with
version ".

That's all I can think of for now as I don't know enough about the
nature of Mozilla Accessibility bug reports.

Thanks a lot for all your efforts.

Have a nice day,
 Daniel



signature.asc
Description: This is a digitally signed message part
-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


Re: [Fwd: [u-a-dev] What can the Mozilla Team do?]

2007-02-20 Thread Willie Walker
Hi Alex:

I think a general assistive technology bug tag might make sense if it's 
something the Ubuntu folks would like to manage (i.e., I'm not sure we 
can expect Joe User to know to tag things appropriately).

For where to start the search, I generally feel happy if people throw 
blame at the top of the food chain first (e.g., Orca).  In some cases, 
it is indeed an Orca bug.  In a lot of cases, it is an underlying 
infrastructure or AT-SPI implementation bug. In these cases, we keep a 
bug open in the Orca bug database, but mark is as '[blocked]' and open 
an associated blocking bug in the offending component.  It takes extra 
work on our part to triage things like this, but it gives us one stop 
shopping for the list of bugs effecting our world.

For the specific case of Firefox...well...Firefox's AT-SPI 
implementation is being completely written.  Most of my engineering time 
is spent chasing down bugs in the Firefox/Gecko AT-SPI implementation 
and engaging the Firefox team in AT-SPI specification interpretation 
dialogs.  Afterwards, I try to make it work with Orca.  This is just 
where we are with Firefox right now because it's all on the bleeding 
edge.  Both teams (Orca and Firefox) are friendly with each other and we 
are both committed to making this work.

For what the Mozilla team can do?  I'd say throw more capable bodies at 
it.  Work with Aaron Leventhal - I'm sure he has no shortage of stuff 
for people to do.  The caret navigation needs work.  The AT-SPI 
implementation in Gecko needs completion, testing, and should attempt to 
behave as much like the GTK+/GAIL implementation as possible.

Thanks!

Will
(Orca Project Lead)

Alex Latchford wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Maybe this will get a better response here?
> 
> Thanks, Alex
> 
> -  Original Message 
> Subject: [u-a-dev] What can the Mozilla Team do?
> Date: Sun, 18 Feb 2007 09:57:16 +
> From: Alex Latchford <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> 
> Howdy guys & gals,
> 
> After popping down to the meeting a few weeks back Henrik Omma made us
> aware, by attending our meeting, of the problems you are facing with
> Accessibility in Firefox & Thunderbird, we really want to help you with
> this however we are unsure of exactly what you need helping with.
> 
> We have started to set up a new bug tag [1], which lists all bugs we
> think are somehow related to the assistive applications included in
> Ubuntu, I was wondering if we could get some clarification on what you
> want us to do with these reports as they *seem* to be relating to Orca
> rather than Firefox specifically.
> 
> We have also started up a stub wiki page outlining the procedures for
> dealing with Accessibility based issues at [2], if I could ask a short
> blurb about what is currently being done and what would help you guys
> out the most, that would be great!
> 
> I think that's about it for now, I personally have joined both
> Accessibility lists and will try to help out as much as possible from
> now on. If you have any problems relating to Mozilla then please feel
> free to contact me and I will try to do my best with the request. :)
> 
> Thanks, Alex.
> 
> [1] https://launchpad.net/ubuntu/+bugs?field.tag=accessibility
> [2] https://wiki.ubuntu.com/MozillaTeam/Accessibility
> 
> - --
> Ubuntu-accessibility-devel mailing list
> [EMAIL PROTECTED]
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility-devel
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFF2wKToqGssgr3yPYRAst4AJ4lX6318eClQsSYcH3+pX6guJKgbACgrPUX
> mZa8qhpMGE7XM1QBXC0RGYc=
> =1c5o
> -END PGP SIGNATURE-
> 


-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility


[Fwd: [u-a-dev] What can the Mozilla Team do?]

2007-02-20 Thread Alex Latchford
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Maybe this will get a better response here?

Thanks, Alex

-  Original Message 
Subject: [u-a-dev] What can the Mozilla Team do?
Date: Sun, 18 Feb 2007 09:57:16 +
From: Alex Latchford <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

Howdy guys & gals,

After popping down to the meeting a few weeks back Henrik Omma made us
aware, by attending our meeting, of the problems you are facing with
Accessibility in Firefox & Thunderbird, we really want to help you with
this however we are unsure of exactly what you need helping with.

We have started to set up a new bug tag [1], which lists all bugs we
think are somehow related to the assistive applications included in
Ubuntu, I was wondering if we could get some clarification on what you
want us to do with these reports as they *seem* to be relating to Orca
rather than Firefox specifically.

We have also started up a stub wiki page outlining the procedures for
dealing with Accessibility based issues at [2], if I could ask a short
blurb about what is currently being done and what would help you guys
out the most, that would be great!

I think that's about it for now, I personally have joined both
Accessibility lists and will try to help out as much as possible from
now on. If you have any problems relating to Mozilla then please feel
free to contact me and I will try to do my best with the request. :)

Thanks, Alex.

[1] https://launchpad.net/ubuntu/+bugs?field.tag=accessibility
[2] https://wiki.ubuntu.com/MozillaTeam/Accessibility

- --
Ubuntu-accessibility-devel mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility-devel

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF2wKToqGssgr3yPYRAst4AJ4lX6318eClQsSYcH3+pX6guJKgbACgrPUX
mZa8qhpMGE7XM1QBXC0RGYc=
=1c5o
-END PGP SIGNATURE-

-- 
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility