Changeset 313


Ignore:
Timestamp:
03/04/10 14:55:19 (10 years ago)
Author:
sander
Message:

Created a second extension proposal

Location:
trunk/doc
Files:
2 added
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/officeshots-extension-proposal.tex

    r263 r313  
    2727\begin{description} 
    2828  \item[Time estimate:] 40 hours 
     29  \item[Deadline:] November 2009 
    2930\end{description} 
    3031 
    3132\section{ODF Anonymiser} 
    3233 
    33 J. David Ib\'a\~nez from iTools has created a tool to anonymise ODF documents. It replaces text, images and metadata with latout-equivalent placeholders.This tool can be used to offer the users of Officeshots the option to anonymise their documents before they are sent to the rendering clients. 
     34J. David Ib\'a\~nez from iTools has created a tool to anonymise ODF documents. It replaces text, images and metadata with layout-equivalent placeholders.This tool can be used to offer the users of Officeshots the option to anonymise their documents before they are sent to the rendering clients. 
    3435 
    3536There would be an extra option on the front page to enable the anonymiser. When an uploaded document is received it would first be piped through the anonymiser before the rendering jobs are created. The user will be able to download the anonymised version of his document along with the rendering results so he can compare eqiuvalent documents. The original document will not be stored on the server. 
     
    3940\begin{description} 
    4041  \item[Time estimate:] 20 hours 
     42  \item[Deadline:] January 2010 
    4143\end{description} 
    4244 
    43 \section{Rendering clients} 
     45\section{Batch processing} 
    4446 
    45 Officeshots is still lacking support for many office applications, most notably Microsoft Office. Backends for these cannot always be written by the developers of those applications. I propose to build these backends myself. It is currently not possible to accurately guess how much time is required to build these. Much depends on the specific API and interfaces of these applications. For closed source applications it also matters which (and how many) licences are donated to Officeshots and if we get access to developers to answer questions. 
     47There are several test suites for OpenDocument Format in existance. These test suites consist of several hundred small documents, each using a distinct feature from the ODF specification. These test suites make it possible to atomically test features from the ODF specification in various office applications. 
    4648 
    47 Instead of trying to accutately estimate how much time will be required I propose to spend a fixed amount of time on creating new backends, and implementing as many as possible in the allotted time. At the very least I intend to write backends for Microsoft Office 2000 and 2003 (which is currently untested alpha quality for MS-Word only) and Microsoft Office 2007. The implementation of these backends does depend on the availability of the new server in Norway and Windows and Office licensed for the virtual machines. These need to be supplied by The OpenDoc Society. 
     49I propose to extend Officeshots to automate the processing of these test suite. There would be a location on the central server where an archive of these test documents could be uploaded. The server then extracts them and feeds them to all the different applications that are running on factories. These jobs would run in a low priority as to avoid overloading the clients and to make sure that normal user-submitted documents complete in time. 
     50 
     51The results of the conversion would be made available in a gallery or on a special gallery-like page. Comparing the results to the original would still require manual work though. 
    4852 
    4953\begin{description} 
    50   \item[Time estimate:] 30 hours 
     54  \item[Time estimate:] 40 hours 
     55  \item[Deadline:] January 2010 
    5156\end{description} 
    5257 
     58\pagebreak 
    5359\section{Validator integration} 
    5460 
     
    5965\begin{description} 
    6066  \item[Time estimate:] 40 hours 
     67  \item[Deadline:] December 2009 
    6168\end{description} 
    6269 
     
    8592\begin{description} 
    8693  \item[Time estimate:] 60 hours 
     94  \item[Deadline:] February 2010 
    8795\end{description} 
    8896 
Note: See TracChangeset for help on using the changeset viewer.