Hi :) The problem is that a major re-write is needed. If we point at little specific things that need changing then the list is long. A re-write would probably take a lot less work. Another problem with focussing on 1 or 2 specific issues is that the work has already been done in the IBM code so it's a bit dis-heartening and how carefully do people have to work at solving the same problems in a different way to avoid licensing issues but still using the Java programming language that the rest of the project is moving away from. A third issue is even if the work does get done for 1 or 2 little things then that still leaves the whole thing in much the same mess that it's already in.
Regards from Tom :) >________________________________ > From: Marc Paré <[email protected]> >To: [email protected] >Sent: Thursday, 22 November 2012, 15:09 >Subject: [libreoffice-accessibility] Re: Funding Wishlist > >Le 2012-11-22 06:30, Tom Davies a écrit : >> 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 :) >> > >Doesn't hurt to ask. IMO, if there were a particular function that you wanted >to hire a coder in order to complete, this would probably be accepted quicker >rather than just getting someone to work on the accessibility issues in >general, But, it would not hurt to submit 2 items such at these. > >IMO, I would try to raise the accessibility profile with more specific >accessibility meetings and encourage 3rd party participation. For example, >Dragon Speaking devs may be interested in helping out making their suite >compatible to LibreOffice if some of our devs were to help out. > >But whatever the accessibility team decides to submit. Remember Florian's >suggestion that the requests "should be reasonable." > >BTW ... the following teams are now actively working on wishlist items: >website-infrastructure; developers; marketing; > >Cheers, > >Marc > > >-- Marc Paré >[email protected] >http://www.parEntreprise.com >parEntreprise.com Supports OpenDocument Formats (ODF) >parEntreprise.com Supports http://www.LibreOffice.org > > >-- Unsubscribe instructions: E-mail to >[email protected] >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 [email protected] 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
