Re: [PROPOSAL] ODF Toolkit for Incubation
+1 :) On 20.07.2011 22:29, Rob Weir wrote: Apologies to those who have received multiple copies of this message. I've cc'ed members of the Apache POI project, the Apache OpenOffice podling and the ODF Toolkit Union, due to the prior interest they've expressed in this. I invite them to join the discussion on general@incubator.apache.org. If they want to subscribe to this list they can do so by sending an email to general-subscr...@incubator.apache.org. = The ODF Toolkit = == Abstract == The ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents. Unlike other approaches which rely on runtime manipulation of heavy-weight editors via an automation interface, the ODF Toolkit is lightweight and ideal for server use. The ODF Toolkit is currently hosted by the ODF Toolkit Union and is licensed under the Apache 2.0 license. == Proposal == To move the following components from the ODF Toolkit Union to a single ODF Toolkit project at Apache: Simple Java API for ODF: http://simple.odftoolkit.org/ ODFDOM: http://odftoolkit.org/projects/odfdom/pages/Home ODF Conformance Tools: http://odftoolkit.org/projects/conformancetools/pages/Home (We'd be open as well to a catchier name. We've been calling it The ODF Toolkit, prefaced always with The. Or individually by component name. But The Apache ODF Toolkit or Apache ODF Toolkit are ponderous.) In addition to migrating the code, we would migrate the website, tutorials, samples, Bugzilla data, and (if feasible) the mailing list archives. We would also seek to transfer the odftoolkit.org domain name to Apache. While under incubation we will merge these projects into a single SDK with three layers: # Package layer, representing the ZIP + Manifest container file of an ODF document. This structure is shared by other document formats, such as EPUB # DOM Layer, a schema-generated layer that maps 1:1 with the ODF schema. This uses Apache Velocity as the templating engine. # Convenience layer: an intuitive, high level API for use by app developers who are not familiar with ODF XML, but who have basic knowledge at the level of a word processor user. == Background == The ODF Toolkit Union was jointly announced by Sun and IBM at the OpenOffice.org Conference in Beijing, November 2008. The idea was to create a portfolio of tools aimed at accelerating the growth of document-centric solutions. The Open Document Format specification is large and complex. Most developers simply do not have the time and energy to master the 1,000-page specification By providing programming libraries, with high level APIs, the ODF Toolkit offers an means to reduce the difficulty level, and encourage development of innovative document solutions. == Rationale == During the recent OpenOffice incubation proposal discussions, the mention of possible moving the ODF Toolkit to Apache was met with enthusiasm. Apache is emerging as the leading open source community for document related projects. The ODF Toolkit would have a good deal of synergy with other Apache projects, including the ODF Toolkit's dependency on Apache XML tools like Xerces, to possible multi-format applications with POI libraries to pipelining ODF with SVG and PDF rendering with Batik, FOP or PDFBox. Getting these various document processing libraries in one place, under a compatible permissive license would be of great value and service to users-developers interested in combining these tools for their specific project requirements. Last, but not least, there is obvious synergy with Apache OpenOffice, as a prominent office suite supporting the ODF format. The ODF Toolkit is already licensed under Apache License, Version 2.0, enabling a smooth transition. = Current Status = == Meritocracy == We understand the intention and value of meritocracy at Apache. The initial committers are familiar with open source development. A diverse developer community is regarded as necessary for a healthy, stable, long term ODF Toolkit project. == Community == The ODF Toolkit is developed by a small set of core developers, though the community extends to include a broad set of application developers who use the code and contribute bug reports, patches and feature requests. Although there are some open source projects that use these components directly, such Apache Directory Studio and GNU Octave, to support ODF import/export, it is more typical for these kinds of libraries to be used by application developers in small, ad-hoc document automation and data wrangling applications. == Core Developers == The coders on the existing ODF Toolkit will comprise the initial committers on the Apache project. These committers have varying degrees of experience with Apache-style open source development, ranging from none to being committers on other Apache projects.. == Alignment == Along with the technical synergies described earlier, Apache
Re: [PROPOSAL] ODF Toolkit for Incubation
+1 :) On 20.07.2011 22:29, Rob Weir wrote: Apologies to those who have received multiple copies of this message. I've cc'ed members of the Apache POI project, the Apache OpenOffice podling and the ODF Toolkit Union, due to the prior interest they've expressed in this. I invite them to join the discussion on general@incubator.apache.org. If they want to subscribe to this list they can do so by sending an email to general-subscr...@incubator.apache.org. = The ODF Toolkit = == Abstract == The ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents. Unlike other approaches which rely on runtime manipulation of heavy-weight editors via an automation interface, the ODF Toolkit is lightweight and ideal for server use. The ODF Toolkit is currently hosted by the ODF Toolkit Union and is licensed under the Apache 2.0 license. == Proposal == To move the following components from the ODF Toolkit Union to a single ODF Toolkit project at Apache: Simple Java API for ODF: http://simple.odftoolkit.org/ ODFDOM: http://odftoolkit.org/projects/odfdom/pages/Home ODF Conformance Tools: http://odftoolkit.org/projects/conformancetools/pages/Home (We'd be open as well to a catchier name. We've been calling it The ODF Toolkit, prefaced always with The. Or individually by component name. But The Apache ODF Toolkit or Apache ODF Toolkit are ponderous.) In addition to migrating the code, we would migrate the website, tutorials, samples, Bugzilla data, and (if feasible) the mailing list archives. We would also seek to transfer the odftoolkit.org domain name to Apache. While under incubation we will merge these projects into a single SDK with three layers: # Package layer, representing the ZIP + Manifest container file of an ODF document. This structure is shared by other document formats, such as EPUB # DOM Layer, a schema-generated layer that maps 1:1 with the ODF schema. This uses Apache Velocity as the templating engine. # Convenience layer: an intuitive, high level API for use by app developers who are not familiar with ODF XML, but who have basic knowledge at the level of a word processor user. == Background == The ODF Toolkit Union was jointly announced by Sun and IBM at the OpenOffice.org Conference in Beijing, November 2008. The idea was to create a portfolio of tools aimed at accelerating the growth of document-centric solutions. The Open Document Format specification is large and complex. Most developers simply do not have the time and energy to master the 1,000-page specification By providing programming libraries, with high level APIs, the ODF Toolkit offers an means to reduce the difficulty level, and encourage development of innovative document solutions. == Rationale == During the recent OpenOffice incubation proposal discussions, the mention of possible moving the ODF Toolkit to Apache was met with enthusiasm. Apache is emerging as the leading open source community for document related projects. The ODF Toolkit would have a good deal of synergy with other Apache projects, including the ODF Toolkit's dependency on Apache XML tools like Xerces, to possible multi-format applications with POI libraries to pipelining ODF with SVG and PDF rendering with Batik, FOP or PDFBox. Getting these various document processing libraries in one place, under a compatible permissive license would be of great value and service to users-developers interested in combining these tools for their specific project requirements. Last, but not least, there is obvious synergy with Apache OpenOffice, as a prominent office suite supporting the ODF format. The ODF Toolkit is already licensed under Apache License, Version 2.0, enabling a smooth transition. = Current Status = == Meritocracy == We understand the intention and value of meritocracy at Apache. The initial committers are familiar with open source development. A diverse developer community is regarded as necessary for a healthy, stable, long term ODF Toolkit project. == Community == The ODF Toolkit is developed by a small set of core developers, though the community extends to include a broad set of application developers who use the code and contribute bug reports, patches and feature requests. Although there are some open source projects that use these components directly, such Apache Directory Studio and GNU Octave, to support ODF import/export, it is more typical for these kinds of libraries to be used by application developers in small, ad-hoc document automation and data wrangling applications. == Core Developers == The coders on the existing ODF Toolkit will comprise the initial committers on the Apache project. These committers have varying degrees of experience with Apache-style open source development, ranging from none to being committers on other Apache projects.. == Alignment == Along with the technical synergies described earlier, Apache
Re: [VOTE] Accept OpenOffice.org for incubation
Please ignore my vote below (duplicate). I first used the wrong email address, which is not subscribed, then used the correct one, and didn't expect that someone would moderate the list and let the first one through... Malte. On 11.06.2011 17:59, Malte Timmermann wrote: +1 (non-binding) Malte. On 10.06.2011 19:05, Sam Ruby wrote: [X] +1 Accept OpenOffice.org for incubation - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request to join as initial committer
On 11.06.2011 18:43, Steve Lee wrote: Very cool. While IBM contributed its accessibility code to Oracle last year, Oracle was unable to fully integrate. We should finish that work if the proposal passes to podling. It looks like this will be an effort you would want to consider working on. This is the code that implements the IA2 APIs that IBM donated to Linux Foundation in December 2008.[1] I'm *very* keen to see this happen. Actually the status with IA2 in OOo is quite good - but not in public CWSes yet - I am quite sure it will find it's way to Apache OOo. Malte. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request to join as initial committer
Hi Joani, nice to see you joining this project! :) Malte. On 10.06.2011 23:28, Joanmarie Diggs wrote: Hi! Sorry for this just-under-the-wire request, but I would love to be added to the list of initial committers if it is not too late. Most of my strengths are around accessibility: Volunteer Job: * Orca project lead (1+ years) and developer (5+ years) * GNOME Accessibility Project assistant to the lead (1+ year) Day Job: * Assistive Technology Specialist, Carroll Center for the Blind (15 years) Thank you in advance for your consideration! Take care. Joanmarie Diggs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
+1 (non-binding) Malte. On 10.06.2011 19:05, Sam Ruby wrote: [X] +1 Accept OpenOffice.org for incubation - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Hi Peter, On 11.06.2011 19:49, Peter Korn wrote: I doubt I'll contribute much direct code to the effort, but I look forward to helping with design decisions that affect accessibility. Would be nice to continue working with you on accessibility :) Malte. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request to join as initial committer
On 11.06.2011 18:43, Steve Lee wrote: Very cool. While IBM contributed its accessibility code to Oracle last year, Oracle was unable to fully integrate. We should finish that work if the proposal passes to podling. It looks like this will be an effort you would want to consider working on. This is the code that implements the IA2 APIs that IBM donated to Linux Foundation in December 2008.[1] I'm *very* keen to see this happen. Actually the status with IA2 in OOo is quite good - but not in public CWSes yet - I am quite sure it will find it's way to Apache OOo. Malte. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request to join as initial committer
Hi Joani, nice to see you joining this project! :) Malte. On 10.06.2011 23:28, Joanmarie Diggs wrote: Hi! Sorry for this just-under-the-wire request, but I would love to be added to the list of initial committers if it is not too late. Most of my strengths are around accessibility: Volunteer Job: * Orca project lead (1+ years) and developer (5+ years) * GNOME Accessibility Project assistant to the lead (1+ year) Day Job: * Assistive Technology Specialist, Carroll Center for the Blind (15 years) Thank you in advance for your consideration! Take care. Joanmarie Diggs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
+1 (non-binding) Malte. On 10.06.2011 19:05, Sam Ruby wrote: [X] +1 Accept OpenOffice.org for incubation - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request: Can proposed committers introduce themselves?
Hi, my name is Malte Timmermann, and I work on the code base of OpenOffice.org since 1991 - almost from the beginning. It started with StarDivision, later acquired by Sun, later acquired by Oracle. While still being an Oracle employee, my engagement here will be on an individual base. Among the many things that I have implemented for OOo are the first version of the multi-platform Help System and compiler (and designing the XML version later), the Basic IDE, different widgets and remote support for VCL, the UNO AWT Toolkit and Uno Controls with MVC separation for using them in multi-view documents, and parts of the XML digital signatures. My biggest contribution probably was the EditEngine, which is used for text IO in Calc, Impress and the Drawing objects. When starting this, I was told to create some lightweight editor for Impress - and it ended up with a huge beast capable of many text processing features, including all the stuff you need for vertical and right-to-left writing, rotated text and text flow in a polygon. Later I became responsible for the project to make OpenOffice.org accessible, which was really challenging because of OOo's own GUI toolkit and because of all existing Accessibility APIs not being complete enough for exposing complex document content. So I spent a lot of time in designing the Uno Accessibility API (which later was used by IBM as the starting point for IAccessible2), and with having many discussions with people from JAA, ATK and with different AT projects and vendors. I still work in the area of Accessibility, be it for the OpenOffice.org application, or for ODF. I am a member of the OASIS ODF TC and it's Accessibility SC. When in 2006 the first security issues with OOo have been reported, I got the job to take care for StarOffice and OOo security and the handling of security issues. I have initiated the OOo Security Team, where people could report vulnerabilities to, and where people from different Linux distros are members so that we could together work on fixing the issues and coordinating release dates. Unfortunately, even working as a technical architect for StarOffice/OOo since 2003, I was only able to influence newly developed stuff, but not to make bigger changes to the existing code base - mainly because of resource and time restrictions. There are many things that should be changed. One of the things I have in mind would make it much easier for other projects or products to make use of the different OOo editors inside other applications or GUI technologies. Since this should be very interesting for commercial products like Lotus Symphony or RedOffice, maybe we can find time and resources for this now (once we have solved the more important issues to get Apache OOo running at all). But it will be a quite big task... It's now time for the next decade of OOo. After a decade of closed source StarOffice, and a decade of copyleft OpenOffice.org, it's now time for many decades of Apache OpenOffice(.org), where many individuals and companies can cooperate together, all having the same rights to make use of the code in other open source projects as well as in closed source products. And you can bet - after working on this thing almost half of my life now, I want to see Apache OpenOffice(.org) becoming a big success! Malte. PS: I just managed to catch up all the emails on this list, and summed it up in my blog at http://blogs.oracle.com/malte/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
