Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B40E76085 for ; Thu, 21 Jul 2011 14:34:35 +0000 (UTC) Received: (qmail 97353 invoked by uid 500); 21 Jul 2011 14:34:35 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 97297 invoked by uid 500); 21 Jul 2011 14:34:35 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 97289 invoked by uid 99); 21 Jul 2011 14:34:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 14:34:34 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jul 2011 14:34:27 +0000 Received: by iyj12 with SMTP id 12so950769iyj.6 for ; Thu, 21 Jul 2011 07:34:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=Go/Gx/EQmYbzWjXqDXpkuAvsu5HcbufOdbslKlsFZHo=; b=WlEeeukcQHqvfibx3yvYkWtTWvzHjj4zwPxpU2rY4KmC4CItpU+DweTB8QulWpt0vI 3B80zyNfIxZ8zrqAhzs4YQ6vPXQCTEYugkikYA7LNmB10eLFjnnSY98X+iZ/FRxtudPV rPr9iWCA09+7aLyLtgRnRRuvFPCEkWjqNdczc= Received: by 10.231.125.212 with SMTP id z20mr243099ibr.154.1311258845112; Thu, 21 Jul 2011 07:34:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.42.180.4 with HTTP; Thu, 21 Jul 2011 07:33:45 -0700 (PDT) In-Reply-To: References: From: Christian Grobmeier Date: Thu, 21 Jul 2011 16:33:45 +0200 Message-ID: Subject: Re: [PROPOSAL] ODF Toolkit for Incubation To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org cool proposal, +1 On Wed, Jul 20, 2011 at 10:29 PM, 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. =C2=A0I invite them to join the discussion on > general@incubator.apache.org. =C2=A0If they want to subscribe to this lis= t > they can do so by sending an email to > general-subscribe@incubator.apache.org. > > =3D The ODF Toolkit =3D > > =3D=3D Abstract =3D=3D > > The ODF Toolkit is a set of Java modules that allow programmatic > creation, scanning and manipulation of OpenDocument Format (ISO/IEC > 26300 =3D=3D ODF) documents. Unlike other approaches which rely on runtim= e > 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. > > =3D=3D Proposal =3D=3D > > 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. =C2=A0We've been calling it "Th= e > ODF Toolkit", prefaced always with "The". =C2=A0Or individually by > component name. =C2=A0But "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. =C2=A0We 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. =C2=A0This structure is shared by other document formats, > such as EPUB > # DOM Layer, a schema-generated layer that maps 1:1 with the ODF > schema. =C2=A0This 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. > > =3D=3D Background =3D=3D > 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 =C2=A0By 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. > > =3D=3D Rationale =3D=3D > > 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. =C2=A0The 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 =C2=A0PDFBox. =C2=A0Getting these various document processi= ng > 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, =C2=A0there is obvious synergy with Apache OpenOffic= e, > 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. > > =3D Current Status =3D > =3D=3D Meritocracy =3D=3D > We understand the intention and value of meritocracy at Apache. =C2=A0The > initial committers are familiar with open source development. =C2=A0A > diverse developer community is regarded as necessary for a healthy, > stable, long term ODF Toolkit project. > > =3D=3D Community =3D=3D > > 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, =C2=A0to support O= DF > 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. > > > =3D=3D Core Developers =3D=3D > The coders on the existing ODF Toolkit will comprise the initial > committers on the Apache project. =C2=A0These committers have varying > degrees of experience with Apache-style open source development, > ranging from none to being committers on other Apache projects.. > > =3D=3D Alignment =3D=3D > Along with the technical synergies described earlier, Apache aligns > well due to its license and emphasis on meritocracy. > > =3D Known Risks =3D > =3D=3D Orphaned products =3D=3D > > The risk, as in most projects, is to grow the project and maintain > diversity. =C2=A0This is a priority that is keenly desired by the > community. > > =3D=3D Inexperience with Open Source =3D=3D > The initial developers include experienced open source developers, > including committers from other Apache projects. Although the majority > of proposed committers do not have Apache experience, they do have > open source experience. > > =3D=3D Homogeneous Developers =3D=3D > The ODF Toolkit Union was created by IBM and Sun (later Oracle) who > provided the majority of its engineering resources as well as its > direction. Moving this project to Apache enables a new start. =C2=A0We > intend to engage in strong recruitment efforts in order to further > strengthen and diversify the community. > > > =3D=3D Reliance on Salaried Developers =3D=3D > When we look at sponsored developers, with the ability to work on this > project full time, IBM currently has more committers. =C2=A0We believe th= at > this situation will change, as the project grows in incubation. > > =3D=3D Relationships with Other Apache Products =3D=3D > Several potential areas for collaboration with other Apache projects > have been suggested, including: > > [[http://poi.apache.org|Apache POI]] which is similar library, focused > on Microsoft Office format documents > > [[http://tika.apache.org/|Apache Tika]] is a generic toolkit for > extracting text and metadata from various file formats. > > [[http://pdfbox.apache.org/|Apache PDFBox]] is a Java library for > working with PDF documents. If not direct code sharing over the Java / > C++ divide, then at least sharing of PDF know-how and perhaps things > like test cases between these projects would be great. > > We are interested in further exploring these options. > > =3D=3DA Excessive Fascination with the Apache Brand=3D=3D > > Our primary interest is in the processes, systems, and framework > Apache has put in place around open source software development more > than any fascination with the brand. > > =3D=3DDocumentation=3D=3D > > There is documentation for the Simple Java API for ODF project, > including a Cookbook, and JavaDoc: > > http://simple.odftoolkit.org/cookbook/ > > http://simple.odftoolkit.org/javadoc/index.html > > For the ODFDOM, there is a good overview documenting the project here: > http://odftoolkit.org/projects/odfdom/pages/ProjectOverview > > A 3rd party introductory tutorial here: > http://www.langintro.com/odfdom_tutorials/ > > =3D=3DInitial Source=3D=3D > > Will come from the ODF Toolkit Union, the latest stable source, plus > any work in-progress > > =3D=3DExternal Dependencies=3D=3D > > We do not believe that we have any external dependencies other than > Apache Xerces, Xalan, Velocity (a build-time dependency), Java 6 and > the ODF schemas (also a build-time dependency) > > =3D=3DCryptography=3D=3D > > We are currently working on adding support for digital signatures and > encryption of documents. The project will complete any needed export > control paperwork related to these features. > > =3D=3DRequired Resources=3D=3D > > The following mailing lists: > > =C2=A0* `odf-dev@incubator.apache.org` - for developer discussions > > =C2=A0* `odf-user@incubator.apache.org` - for user discussions > > =C2=A0* `odf-commits@incubator.apache.org` - for Subversion commit messag= es > > =C2=A0* `odf-issues@incubator.apache.org` - for JIRA change notifications > > =C2=A0* `odf-notifications@incubator.apache.org` - for continuous > build/test notifications > > =3D=3D=3DOther resources=3D=3D=3D > > A source code repository, preferable git > > An issue tracker > > A wiki > > A website > > =3D=3DInitial Committers=3D=3D > > =C2=A0Rob Weir > =C2=A0Biao Han > =C2=A0Svante Schubert > =C2=A0Ying Chun Guo > > =3D=3DSponsors=3D=3D > > =3D=3D=3DChampion=3D=3D=3D > Sam Ruby > > =3D=3D=3DNominated Mentors=3D=3D=3D > Nick Burch > Yegor Kozlov > > =3D=3D=3DSponsoring Entity=3D=3D=3D > > The Apache Incubator > --=20 http://www.grobmeier.de