Re: Enable accessibility team to automatically receive bugmail on a11y bug reports
On 08/10/2012 07:15 PM, Andre Klapper wrote: On Tue, 2012-07-31 at 12:28 +0200, Piñeiro wrote: Sorry Andre, I misunderstood you when we were talking about this at the GUADEC. I also misunderstood you (and maybe didn't make it clear). Sorry. And following the list of sorries, sorry for my late reply. Other idea: Bugzilla components can have an [optional] Default CC beside having the Default Assignee and Default QA Contact. In case we push for an Accessibility component in each product (Ekiga and Empathy already have that), a specific address that a11y can follow could be added to the Default CC list for each a11y component (like accessibility-t...@gnome.bugs). Would that address your needs? Yes, I think that this would address our needs. Being CCed to the accessibility bugs while the default assignee remains one of the module developers makes sense to me. Still I haven't seen any feedback from module maintainers in this thread, and whether an Accessibility component in Bugzilla would be accepted. Feedback welcome. Well, probably it is because it was a vague idea of some interesting modules, probably we could list them explicitly and see if someone catches the ping. Being minimalistic we can start with: * clutter (it already has cally, so we can use it or just rename it) * gtk+ (it already has gail, so we can use it or just rename it) * gnome-shell * gnome-control-center * gdm * empathy * gedit * nautilus * evince And several doubts with respect to evolution (my vote right now is no) BR -- Alejandro Piñeiro Iglesias ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Enable accessibility team to automatically receive bugmail on a11y bug reports
On Aug 16, 2012 1:41 PM, Piñeiro apinhe...@igalia.com wrote: On 08/10/2012 07:15 PM, Andre Klapper wrote: Still I haven't seen any feedback from module maintainers in this thread, and whether an Accessibility component in Bugzilla would be accepted. Feedback welcome. Being minimalistic we can start with: [...] * gnome-shell Certainly no objections from my side. Regards, Florian ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Enable accessibility team to automatically receive bugmail on a11y bug reports
Excerpts from Piñeiro's message of jue ago 16 13:31:19 +0200 2012: On 08/10/2012 07:15 PM, Andre Klapper wrote: On Tue, 2012-07-31 at 12:28 +0200, Piñeiro wrote: Sorry Andre, I misunderstood you when we were talking about this at the GUADEC. I also misunderstood you (and maybe didn't make it clear). Sorry. And following the list of sorries, sorry for my late reply. Other idea: Bugzilla components can have an [optional] Default CC beside having the Default Assignee and Default QA Contact. In case we push for an Accessibility component in each product (Ekiga and Empathy already have that), a specific address that a11y can follow could be added to the Default CC list for each a11y component (like accessibility-t...@gnome.bugs). Would that address your needs? Yes, I think that this would address our needs. Being CCed to the accessibility bugs while the default assignee remains one of the module developers makes sense to me. Still I haven't seen any feedback from module maintainers in this thread, and whether an Accessibility component in Bugzilla would be accepted. Feedback welcome. Well, probably it is because it was a vague idea of some interesting modules, probably we could list them explicitly and see if someone catches the ping. Being minimalistic we can start with: * clutter (it already has cally, so we can use it or just rename it) * gtk+ (it already has gail, so we can use it or just rename it) * gnome-shell * gnome-control-center * gdm * empathy * gedit * nautilus * evince I have no objections to create an Accessibility component in bz for Evince. And several doubts with respect to evolution (my vote right now is no) BR -- Carlos Garcia Campos PGP key: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x523E6462 ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Enable accessibility team to automatically receive bugmail on a11y bug reports
On Thu, Aug 16, 2012 at 1:31 PM, Piñeiro apinhe...@igalia.com wrote: Well, probably it is because it was a vague idea of some interesting modules, probably we could list them explicitly and see if someone catches the ping. Being minimalistic we can start with: * clutter (it already has cally, so we can use it or just rename it) * gtk+ (it already has gail, so we can use it or just rename it) * gnome-shell * gnome-control-center * gdm * empathy * gedit * nautilus * evince I am not opposed to add this to the Nautilus BZ - even though the ideal solution would require being able to subscribe email addresses to keywords/tags like Andre previously suggested. Is there any hope to get such a thing as a Bugzilla feature eventually? Cosimo ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: avoid to select between different proxies
Le vendredi 10 août 2012 à 19:46 +0200, Blackhold a écrit : Hi, I'm using gnome2 and tested gnome3, but I miss a very important thing. in gnome 2 you could have a list of proxies, but in gnome 3 you can That is unclear to me how you could have that in gnome2. Gnome 3 should behave the same as Gnome 2 in term of proxy logic. There might be a bug in the new proxy code now in glib-networking library. Would be nice to provide with full scenario. only select 1. This is useful if you are working between different proxies, in the new way I have to have a text document saved anywhere with the common proxies I use. For more complex proxy settings, I usually recommend using an JavaScript PAC file**. In your gnome setting, choose automatic, set an URI like file:///home/me/my.pac . With a PAC file you can do a lot more, like choosing proxies base on domain, or current subnet, etc. ** See http://en.wikipedia.org/wiki/Proxy_auto-config. cheers, Nicolas ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: avoid to select between different proxies
2012/8/16 Nicolas Dufresne nicolas.dufre...@collabora.co.uk: Le vendredi 10 août 2012 à 19:46 +0200, Blackhold a écrit : Hi, I'm using gnome2 and tested gnome3, but I miss a very important thing. in gnome 2 you could have a list of proxies, but in gnome 3 you can't That is unclear to me how you could have that in gnome2. Gnome 3 should behave the same as Gnome 2 in term of proxy logic. There might be a bug in the new proxy code now in glib-networking library. Would be nice to provide with full scenario. gnome3: http://img249.imageshack.us/img249/3213/captura1f.png gnome2: http://img4.imageshack.us/img4/6002/captura2zg.png in gnome2 I have a list of proxys I usually use. The project I'm on, is guifi.net, we have proxys all over the territory for users could access for free to these internet connections, in my case I've got proxys of different places configured. I think that most users that uses regularly proxies usually use various proxies. Proxy.pac solution is not ok, we could not have announcing proxies all over the network, usually dummy routers could not configure proxy in dns, and in most cases proxy.pac don't works automatically. only select 1. This is useful if you are working between different proxies, in the new way I have to have a text document saved anywhere with the common proxies I use. For more complex proxy settings, I usually recommend using an JavaScript PAC file**. In your gnome setting, choose automatic, set an URI like file:///home/me/my.pac . With a PAC file you can do a lot more, like choosing proxies base on domain, or current subnet, etc. ** See http://en.wikipedia.org/wiki/Proxy_auto-config. cheers, Nicolas ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: avoid to select between different proxies
2012/8/17 Blackhold blackholdmai...@gmail.com: 2012/8/16 Nicolas Dufresne nicolas.dufre...@collabora.co.uk: Le vendredi 10 août 2012 à 19:46 +0200, Blackhold a écrit : Hi, I'm using gnome2 and tested gnome3, but I miss a very important thing. in gnome 2 you could have a list of proxies, but in gnome 3 you can't That is unclear to me how you could have that in gnome2. Gnome 3 should behave the same as Gnome 2 in term of proxy logic. There might be a bug in the new proxy code now in glib-networking library. Would be nice to provide with full scenario. gnome3: http://img249.imageshack.us/img249/3213/captura1f.png gnome2: http://img4.imageshack.us/img4/6002/captura2zg.png in gnome2 I have a list of proxys I usually use. The project I'm on, is guifi.net, we have proxys all over the territory for users could access for free to these internet connections, in my case I've got proxys of different places configured. I think that most users that uses regularly proxies usually use various proxies. Proxy.pac solution is not ok, we could not have announcing proxies all over the network, usually dummy routers could not configure proxy in dns, and in most cases proxy.pac don't works automatically. sorry, in DHCP. only select 1. This is useful if you are working between different proxies, in the new way I have to have a text document saved anywhere with the common proxies I use. For more complex proxy settings, I usually recommend using an JavaScript PAC file**. In your gnome setting, choose automatic, set an URI like file:///home/me/my.pac . With a PAC file you can do a lot more, like choosing proxies base on domain, or current subnet, etc. ** See http://en.wikipedia.org/wiki/Proxy_auto-config. cheers, Nicolas ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Enable accessibility team to automatically receive bugmail on a11y bug reports
Em Mon, 2012-07-30 às 15:19 +0200, Andre Klapper escreveu: Currently accessibility (a11y) bug reports in random modules/products can only be found by querying for the accessibility keyword. Bugzilla does not allow binding an email address to a certain keyword to automaticall create bugmail whenever a specific keyword is added. Having accessibility enabled by default since GNOME 3.5, the GNOME a11y team expressed interest in better notification of a11y bug reports. My proposal is similar to how most user documentation bug reports are handled currently (though this is not totally consistent yet either) and affects many projects using Bugzilla (hence CC'ing d-d-l). snip explanations Turns out that the design team has the same problem, mostly for a number of core components (shell, gtk+, control-center...), using the ui-review keyword. Using a specific product would be really inconvenient for developers, and context destroying in most cases. How about having a script that would query bugs: - with the a11y keyword - that don't have the magic a11y maint alias on CC: and adds the maintainer alias for all those That would avoid the churn and data loss from moving the bug to another component, and allow more flexibility. Adding an accessibility component to gnome-control-center would just create more confusion (we already have universal access), and wouldn't allow us to carry on categorising bugs per panel. It's a no-no from me. Cheers ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
