Date: prev next · Thread: first prev next last


Hi :)
+1

I like the sound of ... 
"It is sometimes good to meet as a team with 3rd party software 
providers to see what kind of progress or what type of cooperative 
development could take place."

Could TDF buy dev time from RedHat or SUSE or Canonical or another supporter of TDF or at least 
someone that  does understand OpenSource and is able to work alongside volunteers and inspire them 
and perhaps build-up a team.  


So, what i would like to see is a person working at a slightly higher level than a dev but 
focussing on developing a team to work on accessibility issues.  Perhaps only part-time but with a 
job title such as 

"Community Development Officer" (for Accessibility) or
"Development Co-ordinator" or
"Development Lead" 

Waiting for a volunteer to happen to take interest has got nowhere is 2 years although a few people 
have put in a lot of hard-work and done some great things (most recently Stuart but there have been 
others).  

Regards from
Tom :)  





________________________________
From: Marc Paré <marc@marcpare.com>
To: LibO Mailing List Accessibility <accessibility@global.libreoffice.org>; Florian Effenberger 
<floeff@documentfoundation.org> 
Sent: Tuesday, 20 November 2012, 15:48
Subject: [libreoffice-accessibility] Re: Funding Wishlist

This may be more a question to Florian as well as the accessibility team.

As LibreOffice Accessibility is a barrier to the acceptance of LibreOffice in many 
governmental/educational/institutional systems worldwide, would it reasonable if there was a 
funding request for dev outsourcing for a particular area of accessibility where code development 
is lagging?

To the accessibility team, if there was funding available for such a thing, what would your items 
be and in order of preference. I know in my local school boards Dragon Speaking is a requirement, 
that is, unless there is an equivalent replacement.

What items would you suggest?

===============

Another funding wishlist item could be that the TDF/LibreOffice help fund an Accessibility 
conference where some of the leading members of the accessibility team along with other interested 
partners could meet to try to solve bottlenecks in development for LibreOffice.

It is sometimes good to meet as a team with 3rd party software providers to see what kind of 
progress or what type of cooperative development could take place.

===============

Would there be any other items that you could think of to put on your wishlist?

Cheers,

Marc


-- Marc Paré
Marc@MarcPare.com
http://www.parEntreprise.com
parEntreprise.com Supports OpenDocument Formats (ODF)
parEntreprise.com Supports http://www.LibreOffice.org

-- Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted




-- 
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.