Re: Gnome/Guadec and Government market
Hi Sanne: Javier's e-mail is the only contact I have. :-( He may be in the process of moving, but I'm not sure. I'm CC'ing Peter Korn, however. He may have some contacts that you can use. Will On Mar 30, 2010, at 10:11 AM, Sanne te Meerman wrote: Hi Willie, Besides a practical comment from Andre Klapper, you were the only one who responded to my request for a talk about accessibility. I've tried to contact Javier Martinez, but so far I have not received a reply. Could you connect us? I'm still very much interested. Thanks, Sanne Sanne te Meerman schreef: Wow, that's really great... the fact that a local organisation gets involved with software development from the bottom up is fantastic, but this is also great for marketing Open Source, a showcase for the added value of open source development. And for Gnome and Guadec this could also be very valuable. Thank you. Javier, if you're reading this, I'd love to hear more. Sanne Willie Walker schreef: Hi: The ONCE organization in Spain does a fair amount with GNOME and GNOME accessibility. I'm CC'ing Javier Martinez on this e-mail -- he's my primary contact with ONCE. Will Sanne te Meerman wrote: I've made this a new thread. (this time really, sorry Andre) Thanks Dave, If these companies could connect with the public sector during or before Guadec, the involvement of public sector and the mentioned companies will be more attractive for both. Do you have names/ emails of i.e. persons responsible for marketing open source related products at these companies? Or maybe someone from Novell/RH/Mandriva is listening? That would be a good start. Their participation in shaping a meeting of some sort would give me something to 'brag about' at public sector. I've had some contacts in spain in the past, I'll look through my emails for that. Again, if someone from Extremadura is involved with Gnome, let me know. thank you, Sanne Hi, Stormy Peters wrote: I don't think there is anyone currently targeting governments but I think we need to do this. Anybody willing to help Sanne? I believe that Novell, Red Hat and Mandriva all target public sector markets in Europe. Perhaps Extremadura and Andalucia would be good contacts for Sanne also, as government sector users of GNOME. Chers, Dave. Stormy Peters schreef: I don't think there is anyone currently targeting governments but I think we need to do this. Anybody willing to help Sanne? Stormy On Thu, Dec 17, 2009 at 8:16 AM, Sanne te Meerman sa...@opensourceadvies.nl mailto:sa...@opensourceadvies.nl wrote: Hi, Repeated request: is there some information I'm unaware of about Gnome and targeting the government market? Or anyone who is experienced in this subject? thank you, Sanne te Meerman Guadec organisation Sanne te Meerman schreef: I've just subscibed to this mailinglist, so to avoid being off-topic, I've made a subthread. I was immediately triggered by this subject and conversation. I am trying to involve Dutch national governemnt with Guadec (I'm part of the dutch team of organisers). Focus on accessibility and usability can draw attention for several reasons, in my opinion: -attention on policy issues instead of technique is important. Accessibility and usability are issues that ring with policymakers (more than technique) -Government is more inclined to have attention to these subjects than i.e. companies because of political attention and pressure to these issues. -the bottom-up development of open source might be the best way to connect with the personal itches of disabled people. The industry involved therefore might have an advantage to more traditional ICT companies in this niche market. It might be good to have some sessions about usability and accesebility during Guadec. I will propose that. Any other suggestions? Maybe there is some documentation about Gnome and targeting the government market, that someone can point me to. That would be helpful. thank you, Sanne te Meerman Brian Cameron schreef: Willie/Dave: It might also be nice to highlight the humanitarian aspects of accessibility a bit more. For example, I think it would be nice to highlight something about the GNOME accessibility community. Perhaps something about the fact that a number of people with disabilities participate in development and in user forums. I think the promise of joining a community of people working to address accessibility usability issues is attractive to highlight
Re: Communicating to users what GNOME 3.0 is
Hi All: The accessibility changes are big - and as it's a core component of GNOME (accessible to all) there's probably a lot more we could be doing around it. (I'm not an expert on accessibility in any way, shape or form). I use the phrase the perfect storm when it comes to the a11y work for GNOME 3: bonobo deprecation, WebKit, and GNOME Shell are all difficult challenges when it comes to accessibility. However, to put a positive spin on it... 1) The move away from Bonobo/CORBA to D-Bus lays the foundation for GNOME accessibility to be available on more devices. It also provides a common infrastructure that can be used by KDE -- if things go well, people will be able to access KDE GUI's using GNOME assistive technologies. This will give them access they've never had before. 2) We're hoping to improve the out of the box experience for setting up Universal Access preferences - http://live.gnome.org/Accessibility/NewPreferencesGUI. This will make the GNOME desktop more approachable to a larger number of people. 3) The work with http://live.gnome.org/Caribou will provide tighter mouse-only integration with the desktop, helping people with disabilities as well as touch-screen users. 4) The better integration with GDM will provide an easier way to set up accessible login. Will -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Gnome/Guadec and Government market
): In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 5:27 PM, Dave Neary wrote: Hi, Shorter would be better, I think. How about this (pure edit, no additions): In GNOME, making sure that people with disabilities can use our software is a core value. From infrastructure allowing our built-in screen reader or specialised hardware to interact with applications to utilities to make it easier for people with motor problems to interact with a computer, accessibility in GNOME is built-in, not bolted on. As a result GNOME not only has compelling accessibility today, it also provides a rich foundation for the future. How does that read? Covers all the bases, I think - a11y is a core value, what does accessibility mean, and how do we make things easier for people with disabilities. Maybe needs a quick fact check on the second sentence (it is at-spi that lets Orca do its thang, isn't it?) Cheers, Dave. Willie Walker wrote: Here's a bunch of run-ons... :-) In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the accessibility infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days of GNOME. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Today, users have built-in keyboard navigation, highly customizable fonts/colors/icons, keyboard enhancements such as StickyKeys, the MouseTweaks tool that provides mouse clicking features by dwelling, the GOK on screen keyboard that can be driven via dwell clicking and switches, the Dasher predictive text entry tool, and the Orca screen reader and magnifier. Developers also have the glade-3 tool that helps encourage accessible user interface design and the accerciser tool that helps developers analyze how their application is exposed to the built-in accessibility infrastructure. For tomorrow, the GNOME project is busily working on enhancing the on screen keyboard and magnifier, developing ways to use web cameras to move the mouse based upon head/body position, and making the solution much more friendly to resource constrained devices such as netbooks and the OLPC. Will On Dec 8, 2009, at 1:08 PM, Stormy Peters wrote: Looks good. Can we add a sentence or two about what accessibility
Re: Braille printing for conferences
Thanks Dave! Something about the specialised hardware to interact with applications portion seems odd to me. In GNOME, we have a core value that people with disabilities have free compelling access to the graphical desktop and web. GNOME accomplishes this with full keyboard access, theming, and an industry leading accessibility infrastructure that is used by built-in assistive technologies including a screen reader, magnifier, and on screen keyboard. With a model of built in versus bolted on, GNOME not only has free compelling accessibility today, but it also provides a rich and stable base for future accessibility work. or... (I just took my first stab at this and added by people with disabilities to the first sentence): In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 5:27 PM, Dave Neary wrote: Hi, Shorter would be better, I think. How about this (pure edit, no additions): In GNOME, making sure that people with disabilities can use our software is a core value. From infrastructure allowing our built-in screen reader or specialised hardware to interact with applications to utilities to make it easier for people with motor problems to interact with a computer, accessibility in GNOME is built-in, not bolted on. As a result GNOME not only has compelling accessibility today, it also provides a rich foundation for the future. How does that read? Covers all the bases, I think - a11y is a core value, what does accessibility mean, and how do we make things easier for people with disabilities. Maybe needs a quick fact check on the second sentence (it is at-spi that lets Orca do its thang, isn't it?) Cheers, Dave. Willie Walker wrote: Here's a bunch of run-ons... :-) In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the accessibility infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days of GNOME. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Today, users have built-in keyboard navigation, highly customizable fonts/colors/icons, keyboard enhancements such as StickyKeys, the MouseTweaks tool that provides mouse clicking features by dwelling, the GOK on screen keyboard that can be driven via dwell clicking and switches, the Dasher predictive text entry tool, and the Orca screen reader and magnifier. Developers also have the glade-3 tool that helps encourage accessible user interface design and the accerciser tool that helps developers analyze how their application is exposed to the built-in accessibility infrastructure. For tomorrow, the GNOME project is busily working on enhancing the on screen keyboard and magnifier, developing ways to use web cameras to move the mouse based upon head/body position, and making the solution much more friendly to resource constrained devices such as netbooks and the OLPC. Will On Dec 8, 2009, at 1:08 PM, Stormy Peters wrote: Looks good. Can we add a sentence or two about what accessibility is or give some examples of the technology? Stormy On Tue, Dec 8, 2009 at 11:07 AM, Willie Walker william.wal...@sun.com wrote: Here's a quick snippet I might propose: In GNOME, accessibility is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 12:58 PM, Stormy Peters wrote: Paul Cutler and Denise Walters were working on that part so hopefully one of them will chime in. It'd probably be good to ask the a11y team for a short summary to put there though. Stormy On Mon, Dec 7, 2009 at 8:34 PM, Ben Konrath b...@bagu.org wrote: On Tue, Dec 1, 2009 at 4:03 PM, Stormy Peters sto...@gnome.org wrote: snip Accessibility: [photgraph of user
Re: Braille printing for conferences
In GNOME, we have a core value that people with disabilities have free compelling access to the graphical desktop and web. GNOME accomplishes this with full keyboard access, theming, and an industry leading accessibility infrastructure that is used by built-in assistive technologies including a screen reader, magnifier, and on screen keyboard. With a model of built in versus bolted on, and with all development being done using direct continuous collaboration with people with disabilities, GNOME not only has free compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Or... In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, and with all development being done using direct continuous collaboration with people with disabilities, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will Brian Cameron wrote: Willie/Dave: It might also be nice to highlight the humanitarian aspects of accessibility a bit more. For example, I think it would be nice to highlight something about the GNOME accessibility community. Perhaps something about the fact that a number of people with disabilities participate in development and in user forums. I think the promise of joining a community of people working to address accessibility usability issues is attractive to highlight. If that wouldn't make it too long, and you agree. Brian Thanks Dave! Something about the specialised hardware to interact with applications portion seems odd to me. In GNOME, we have a core value that people with disabilities have free compelling access to the graphical desktop and web. GNOME accomplishes this with full keyboard access, theming, and an industry leading accessibility infrastructure that is used by built-in assistive technologies including a screen reader, magnifier, and on screen keyboard. With a model of built in versus bolted on, GNOME not only has free compelling accessibility today, but it also provides a rich and stable base for future accessibility work. or... (I just took my first stab at this and added by people with disabilities to the first sentence): In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 5:27 PM, Dave Neary wrote: Hi, Shorter would be better, I think. How about this (pure edit, no additions): In GNOME, making sure that people with disabilities can use our software is a core value. From infrastructure allowing our built-in screen reader or specialised hardware to interact with applications to utilities to make it easier for people with motor problems to interact with a computer, accessibility in GNOME is built-in, not bolted on. As a result GNOME not only has compelling accessibility today, it also provides a rich foundation for the future. How does that read? Covers all the bases, I think - a11y is a core value, what does accessibility mean, and how do we make things easier for people with disabilities. Maybe needs a quick fact check on the second sentence (it is at-spi that lets Orca do its thang, isn't it?) Cheers, Dave. Willie Walker wrote: Here's a bunch of run-ons... :-) In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the accessibility infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days of GNOME. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Today, users have built-in keyboard navigation, highly customizable fonts/colors/icons, keyboard enhancements such as StickyKeys, the MouseTweaks tool that provides mouse clicking features by dwelling, the GOK on screen keyboard that can be driven via dwell clicking and switches, the Dasher
Re: Braille printing for conferences
Here's a quick snippet I might propose: In GNOME, accessibility is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 12:58 PM, Stormy Peters wrote: Paul Cutler and Denise Walters were working on that part so hopefully one of them will chime in. It'd probably be good to ask the a11y team for a short summary to put there though. Stormy On Mon, Dec 7, 2009 at 8:34 PM, Ben Konrath b...@bagu.org wrote: On Tue, Dec 1, 2009 at 4:03 PM, Stormy Peters sto...@gnome.org wrote: snip Accessibility: [photgraph of user interacting with A11Y tools] Is there a reason why there is no text for this section? Did you guys not have time to write something up during the meeting or was it lost in a cut 'n paste? :-) I'm really just wondering what's up just so I know if this is something the a11y team needs to write up if we go ahead with the Braille handouts. Cheers, Ben -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Braille printing for conferences
Here's a bunch of run-ons... :-) In GNOME, accessibility by people with disabilities is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the accessibility infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days of GNOME. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Today, users have built-in keyboard navigation, highly customizable fonts/colors/icons, keyboard enhancements such as StickyKeys, the MouseTweaks tool that provides mouse clicking features by dwelling, the GOK on screen keyboard that can be driven via dwell clicking and switches, the Dasher predictive text entry tool, and the Orca screen reader and magnifier. Developers also have the glade-3 tool that helps encourage accessible user interface design and the accerciser tool that helps developers analyze how their application is exposed to the built-in accessibility infrastructure. For tomorrow, the GNOME project is busily working on enhancing the on screen keyboard and magnifier, developing ways to use web cameras to move the mouse based upon head/body position, and making the solution much more friendly to resource constrained devices such as netbooks and the OLPC. Will On Dec 8, 2009, at 1:08 PM, Stormy Peters wrote: Looks good. Can we add a sentence or two about what accessibility is or give some examples of the technology? Stormy On Tue, Dec 8, 2009 at 11:07 AM, Willie Walker william.wal...@sun.com wrote: Here's a quick snippet I might propose: In GNOME, accessibility is a core value that touches all aspects of the system. With a model of built in versus bolted on, the GNOME Accessibility project has helped lead the industry in accessible design. From the infrastructure, to the graphical toolkit, to the applications, to the assistive technologies, accessibility has been a central consideration from the very early days. As a result, GNOME not only has compelling accessibility today, but it also provides a rich and stable base for future accessibility work. Will On Dec 8, 2009, at 12:58 PM, Stormy Peters wrote: Paul Cutler and Denise Walters were working on that part so hopefully one of them will chime in. It'd probably be good to ask the a11y team for a short summary to put there though. Stormy On Mon, Dec 7, 2009 at 8:34 PM, Ben Konrath b...@bagu.org wrote: On Tue, Dec 1, 2009 at 4:03 PM, Stormy Peters sto...@gnome.org wrote: snip Accessibility: [photgraph of user interacting with A11Y tools] Is there a reason why there is no text for this section? Did you guys not have time to write something up during the meeting or was it lost in a cut 'n paste? :-) I'm really just wondering what's up just so I know if this is something the a11y team needs to write up if we go ahead with the Braille handouts. Cheers, Ben marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Speaking at RPI in New York
Hi All: My parents live in upstate New York and I'm probably headed down to visit them over Thanksgiving. One of the routes I drive down to my parent's house takes me through Troy, so it might be a welcome driving break to stop by and give a talk, assuming I can talk my wife and son into hanging out somewhere for an hour and a half or so. I'd also like to try to hook up with Ephraim Glinert (Professor Emeritus of Computer Science at RPI) if possible -- he was involved in some of the Java Accessibility API work we did back in the late 90's. So, if RPI is not going to be shut down the week of Thanksgiving, I might be available to speak Mon-Wed. Will PS - I'm also trying to hook up with the National Technology Institute for the Deaf at RIT in Rochester that week. If both RPI and RIT are available, it might get a little tight, but still fun. Tim Horton wrote: On Nov 2, 2009, at 04:22, Stormy Peters wrote: Anybody in the New York area interested in speaking at RPI? If anyone *is* interested in coming/talking and needs a place to stay, racarr and I have a couch you can happily crash on (we go to RPI, and live a few minutes off campus). We'd also *love* to have someone come visit and give a talk :-) --Tim Stormy -- Forwarded message -- From: *Luis Ibanez* luis.iba...@kitware.com mailto:luis.iba...@kitware.com Date: Sat, Oct 31, 2009 at 12:42 PM Subject: Re: [TOS] FSOSS session notes To: Stormy Peters stormy.pet...@gmail.com mailto:stormy.pet...@gmail.com Cc: Mel Chua m...@redhat.com mailto:m...@redhat.com, TOS t...@teachingopensource.org mailto:t...@teachingopensource.org, Will Schroeder will.schroe...@kitware.com mailto:will.schroe...@kitware.com, Badri Roysam roy...@ecse.rpi.edu mailto:roy...@ecse.rpi.edu, Mukkai Krishnamoorthy moor...@cs.rpi.edu mailto:moor...@cs.rpi.edu Stormy, This is a great idea, and it is very much needed. We are currently running our Open Source Software Practices course http://public.kitware.com/OpenSourceSoftwarePractice/index.php/Main_Page at RPI (http://www.rpi.edu http://www.rpi.edu/) and will appreciate to have a visiting speaker from the GNOME project. Should we simply ask our name/course to the page: http://live.gnome.org/GnomeEvents/Speakers (?) Here are several typical needs that an Open Source Course have from Open Source Projects: a) Case studies: for example, we cover a couple of sessions on Governance and community management. We talk about the projects that we manage (www.itk.org http://www.itk.org/, www.vtk.org http://www.vtk.org/, www.paraview.org http://www.paraview.org/), but it is very useful to have other cases. We have used tele-participation in the past (if that helps) via Skype. b) Class projects: students must work on a FOSS as part of their grade. They tend to have difficulties identifying a community that they can join, and managing to find something interesting that can be executed in about 12 weeks (with about 2~4 hours of work a week). Do you have a list of low hanging fruit in your bug tracker and or feature request list, that students could work on as part of their class project. c) Talks to the larger community: (not just the class). This works better with a FOSS project representative visiting the school for on day. It will be great is someone from GNOME was available in the period from now to Dec 10. We will be happy to provide more details if you are interested. Thanks Luis --- 2009/10/31 Stormy Peters stormy.pet...@gmail.com mailto:stormy.pet...@gmail.com: Did you talk about how to get more developers to visit schools? We've talked about this at GNOME. We'd like to have a list of potential speakers (listed by topic and location) and a list of schools that would like speakers. http://live.gnome.org/GnomeEvents/Speakers http://live.gnome.org/GnomeUni Is there a way we could work with this group to understand the need better and make this happen? Stormy -- marketing-list mailing list marketing-list@gnome.org mailto:marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: marketing hackfest?
I think this is a good idea. I would definitely like to attend this if it were at GNOME Boston and on Sunday or Monday. Thanks! Will Stormy Peters wrote: A couple of questions for the whole group: * Do you think a marketing hackfest is a good idea? * Would you be interested in attending? (If it was at a good time and place for you.) * Would you attend one around the Boston Summit? Thanks, Stormy On Thu, Sep 17, 2009 at 12:05 PM, Paul Cutler pcut...@gnome.org mailto:pcut...@gnome.org wrote: I think this is an excellent idea. Hackfests are especially helpful, not only for the energy they create, but the opportunity to plan your writing in a group environment. This was one of the big takeaways we learned at the Documentation hackfest earlier this year, and there was a presentation on it. Having the ability to sit down, brainstorm, plan and write a first draft for all the different projects we have in the pipeline would be an excellent use of time. Paul On Thu, Sep 17, 2009 at 12:25 PM, Lefty (石鏡 ) le...@shugendo.org mailto:le...@shugendo.org wrote: It’s looking like I’m going to be in Tokyo around that time, unfortunately. On 9/17/09 9:16 AM, Stormy Peters sto...@gnome.org http://sto...@gnome.org wrote: There might be an opportunity to have a marketing hackfest around the Boston Summit time frame. If so, who would be interested in coming? Would you be able to make it to the Boston Summit? I think it would be an excellent opportunity to kick off a lot of the projects we've been talking about from a press kit, to information for people going to events, to a CRM system, to the case studies, ... (I personally can not make it to the Boston Summit but I could come out the day/week after.) Stormy -- marketing-list mailing list marketing-list@gnome.org mailto:marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Open Video Guidelines (WAS: Re: [Foundations] Open Video Conference, NYU, June 19-20)
Hi All: On the accessibility front, it would be highly desirable to choose an encoding format that allows for closed captioning. My accessible video knowledge is pretty limited, though, to even be able to make a suggestion for what to use. Will Paul Cutler wrote: I know this is slightly off topic, but I used the latest version of Pitivi at Writing Open Source to transcode the keynotes from my camcorder to ogg, and came away pretty impressed with PiTiVi since I last used it a year ago. (Speaking of dogfood and all). Paul On Mon, Jun 22, 2009 at 5:39 PM, Sriram Ramkrishna s...@ramkrishna.me wrote: Jay, How did it go? I talked with J5 (John Palmieri) and he said he was going to represent GNOME there. I am of course very interested in setting up something in this regard. John had a pretty nice post on this and I'm eager to set up something where we can dogfood our video apps and be able to have a common site for tutorials and what not. sri On Mon, May 18, 2009 at 4:15 PM, Stormy Peters stormy.pet...@gmail.com mailto:stormy.pet...@gmail.com wrote: Anybody have any feedback for Jay on whether or not the following tutorials will be useful to us? (I assume the tutorials will be viewable remotely.) On Sat, May 16, 2009 at 8:29 PM, Jay dedman jay.ded...@gmail.com mailto:jay.ded...@gmail.com wrote: Hey Stormy-- Just following up to see if you had any further ideas on tutorials for the Open Video Conference. We're discussing them now amongst ourselves. * How to compress using Ogg/Theora so it looks really good (H264 is the standard comparison) * How to embed the Ogg/Theora on a blog using the video tag * How to customize the player used in the new Firefox * What can we do with the canvas tag??? Not sure if any of this is of interest to you. Jay On Tue, May 12, 2009 at 6:54 PM, Jay dedman jay.ded...@gmail.com mailto:jay.ded...@gmail.com wrote: Nice to meet you! I'm cc'ing the GNOME marketing list as that's where we've been discussing a video project. If we had an online guide to publishing practices for open video (including soliciting and sharing them), I'm sure many projects would find it useful. In addition if we had a common place to share them we could build up a good archive ... Hey Stormy-- (I'm cc'ing our partner, Michael Verdi, on this email.) As Dean said, we plan to organize a table at the Open Video Conference where video creators can get together to learn to use all this new HTML5 + Ogg/Theora on their sites. We're going to get down and dirty. Our goal is to make some video tutorials for the conference in response to some of the most commonly asked questions: How to compress using Ogg/Theora so it looks really good (H264 is the standard comparison) How to embed the Ogg/Theora on a blog using the video tag How to customize the player used in the new Firefox What can we do with the canvas tag??? We'll be publishing these videos to our work-in-progress site, Freevlog.org. There's also Makeinternet.tv where we could crosspost. Let us know what you guys had in mind. As video creators, we're currently trying to figure all that's possible with HTML5 and the new Firefox. Jay -- http://ryanishungry.com http://jaydedman.com http://twitter.com/jaydedman 917 371 6790 -- http://ryanishungry.com http://jaydedman.com http://twitter.com/jaydedman 917 371 6790 -- marketing-list mailing list marketing-list@gnome.org mailto:marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org mailto:marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list -- marketing-list mailing list marketing-list@gnome.org
Re: [g-a-devel] GNOME Accessibility presentation - contribution to stock GNOME presentations
Hey All: I updated the videos a little and move them here, including some Flash versions: http://master.gnome.org/~wwalker/demos/ I'll try get to Orca and Dasher soon. As soon as I can get GOK working on my desktop, I'll do something for it as well. Will PS - My setup is here: http://master.gnome.org/~wwalker/demos/setup.txt On Wed, 2008-10-01 at 10:03 -0400, David Bolter wrote: +1 for GOK ;) Will, Peter Korn has put on decent live demos in the past with GOK... showing desktop integration... might be worth pinging him for ideas. Please make sure you show off single switch scanning... and UI Grab... word completion... we can talk offline. cheers, davidb Dave Neary wrote: Hi Willie, Willie Walker wrote: http://master.gnome.org/~wwalker/dwell-click.avi http://master.gnome.org/~wwalker/theming.avi http://master.gnome.org/~wwalker/keyboard-enhancements.avi http://master.gnome.org/~wwalker/enable-a11y.avi Cool stuff! You used recordmydesktop, you say? One piece of feedback: I've found in my demos that setting high contrast large print inverse makes the desktop hard to put back the way it was, and some windows behave badly with the theme (some dialogs grows off the edge of the screen and I can't get at the buttons to dismiss the dialog). Have you found the same thing? I'm *really* looking forward to seeing a gok demo :) I'm kind of proud of the creative use of the cheese application in the keyboard-enhancements video. ;-) Very nice indeed :) Pity about some of the video artifacts, but definitely did the job. These were just quick unscripted demos that I rattled off kind of fast, so there's definitely room for improvement. I wish, for example, I knew how to edit/splice things so I didn't have to do them in one take. I guess Diva or Pitivi are the ones you need for a job like that? Although I haven't figured out how to split segments into different bits with that... Let me know what you think. If you like them, I can do more for GOK, Dasher, and Orca. GOK! GOK! I'd love to see one for Orca too, but I suspect it'd be a half an hour long (or would be 3 or 4 different segments - one for the magnifier, one for the screen reader, one for ...) Cheers, Dave. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: [g-a-devel] GNOME Accessibility presentation - contribution to stock GNOME presentations
Hey All: Here's some quick examples of what I was thinking about for demos of the accessibility support for GNOME. The target audience currently is unfortunately only for sighted people who can hear (sorry - it's my first real experiment with recordmydesktop), and these are geared more towards the short elevator pitch demo that you'd give at a talk rather than intending to be a complete tutorial. http://master.gnome.org/~wwalker/dwell-click.avi http://master.gnome.org/~wwalker/theming.avi http://master.gnome.org/~wwalker/keyboard-enhancements.avi http://master.gnome.org/~wwalker/enable-a11y.avi I'm kind of proud of the creative use of the cheese application in the keyboard-enhancements video. ;-) These were just quick unscripted demos that I rattled off kind of fast, so there's definitely room for improvement. I wish, for example, I knew how to edit/splice things so I didn't have to do them in one take. Let me know what you think. If you like them, I can do more for GOK, Dasher, and Orca. I can also redo these make them a little more professional if people think these are useful. Remember, these are just for giving you an idea of what's available and not meant to be instructional videos. Will On Thu, 2008-09-11 at 18:18 +0200, Dave Neary wrote: Hi there, Willie Walker wrote: I think the idea of stock presentations and demos (something you proposed earlier this year) is an awesome idea. Yup! Me too. I need to ramp back up on this stuff soon as well since I will be doing a few presentations in the coming months. I'm more than willing to put my stuff under some sort of public repository somewhere. I'd prefer something that makes it really really easy for me to upload docs and also really easy obtain them. Me too. Right now we were using the wiki, but for presentations screencasts, that just seems wrong. That slide sharing site and YouTube or Google Video seem like better fits. What do you think about making some sort of gnome-marketing module in GNOME svn where we could be somewhat free about uploading and grabbing things? I wouldn't mind myself - I suspect that a significant minority of participants in the marketing list probably don't have svn commit access, though. PS - We also have some money left over in the GNOME Outreach Program: Accessibility budget. I was thinking about trying to create a task for someone to create a bunch of short screencast videos of the assistive technologies in action (i.e., here's theming, here's stickykeys, here's bouncekeys, here's GOK in dwell mode, here's Dasher, here's MouseTweaks, here's Orca, etc.). What do you think about that? I think this is a wonderful idea! And an excellent way to get some non-technical contributions. Cheers, Dave. -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: [g-a-devel] GNOME Accessibility presentation - contribution to stock GNOME presentations
Hi Dave: I think the idea of stock presentations and demos (something you proposed earlier this year) is an awesome idea. I need to ramp back up on this stuff soon as well since I will be doing a few presentations in the coming months. I'm more than willing to put my stuff under some sort of public repository somewhere. I'd prefer something that makes it really really easy for me to upload docs and also really easy obtain them. What do you think about making some sort of gnome-marketing module in GNOME svn where we could be somewhat free about uploading and grabbing things? Will PS - We also have some money left over in the GNOME Outreach Program: Accessibility budget. I was thinking about trying to create a task for someone to create a bunch of short screencast videos of the assistive technologies in action (i.e., here's theming, here's stickykeys, here's bouncekeys, here's GOK in dwell mode, here's Dasher, here's MouseTweaks, here's Orca, etc.). What do you think about that? Dave Neary wrote: Hi all, Way back in July, I gave a presentation (once in English, once in French) of GNOME accessibility technologies - I thought it might be a useful stock presentation for that for others. Some things definitely need improvement - simple inaccuracies like talking about gnopernicus, outdated screenshots of GNOME 2.4, the photo of my brother the family (perhaps too personal for a stock presentation), and the presentation needs a narrative - I've attached my notes from the presentation below to give you an idea, it's a good 45 minutes to 1 hour long presentation. I also have a French translation. The core goal of the presentation is to show that accessibility is important because of the people we help. It's important not because having a certain level of conformance with standards opens the door to government contracts, or as a selling point for the software, but because it helps users developers, sometimes (like through Strongwind, Dogtail and LDTP) in unexpected ways. The presentation is too big to send to the list, so I've put it on a website - you can get it at: http://dneary.free.fr/Presentations/Digital ramps and handrails.pdf (versions in .ppt and .odp will also be there, but perhaps with missing bitmaps, etc). The general thrust of the presentation is: * We use computers with standard input output devices - a mouse, a keyboard, a screen. * But that doesn't cover all use-cases. Blind people can't see screens. People with degenerative motor illness can't use mice or keyboards. Old people with normal illnesses like arthritis and vision impairments can't easily use all this stuff either. And kids (and parents holding babies ;) also have trouble with these devices which require sophisticated hand-eye co-ordination * There are other hardware inputs outputs that can help: * Joysticks instead of mice * Drawing tablets * Braille keyboards * Audio input output (speech synthesis, audio signals, speech recognition for commands) * A whole range of things like accelerometers, championned by the iPhone and the Wii, and in general the whole range of video game controls which make you think differently abut interracting with a computer * More specialised: eye trackers that can use eye movement and blink patterns to command * And finally, software to make things easlier * Here's where GNOME fits in * Project founded on the principle of universal access - making computer technology available to anyone, not just geeks, regardless of culture, technical or physical ability - in 3 main ways: consistent, usable, learnable user interfaces; internationalised and localised applications (chance to explain the difference between internationalised (take out all local assumptions) and localised (add back in all the local constraints for many cultures)); work on accessibility (a nod to Sun Microsystems and IBM, who have been long-time champions of this). The rest of the presentation is a demo of various accessibility features in GNOME. I discovered several quirks bugs while doing the demos :-} The demos split into 2/3 parts: 1. General GNOME features which are useful to people with handicaps 2. Accessibility features available to all GNOME applications, regardless of the desktop configuration 3. Features that depend on AT-SPI being activated, and which can be considered advanced accessibility tools * Keyboard shortcuts: the entire GNOME desktop is available through use of only the keyboard. Remove mouse, start demo: Basics: 1. Switch applications (Alt-Tab) 2. Choose panel (Ctrl-Alt-Tab) - open a new application through panel (BUG #542325: When you open a menu while navigating with the keyboard, you cannot again navigate with the keyboard until you click somewhere with the mouse) 3. Alt-key to navigate menus of an application 4. Tab, Shift-Tab to navigate through interface elements in an application (including web application) (would be nice to show navigation to
