On 16 August 2014 18:38, Dennis E. Hamilton <dennis.hamil...@acm.org> wrote:
> I don't have any skin in this game. > > Yet I am baffled about where this work is going on and what Apache Project > it relates to. Is there an incubator proposal for Apache DocFormats on its > way? > Yes there is a proposal on its way, look at general-incubator approx. the last 3 days. Right now it is not decided who should sponsor this project. > > In particular, I would expect that some thought would be given to the ODF > Toolkit and that incubator project, < > http://incubator.apache.org/odftoolkit/>. > > Also, Apache POI would seem to have some relevance, especially the > OpenXML4J component, <http://poi.apache.org/>. > The intention is clearly to at least have a close cooperation with these projects. But docFormats aims at a bit more (like e.g. being openoffice on tablets). I am right now working on student proposal, to get a compliance sheet made for products that offer OXML and/or odf. MAybe that would be something you would want to help out with. > These are all Java based, as is Armin's current project in the AOO > repository. I haven't listed open-source projects outside the embrace of > ASF. > > A single <orcnote> remark is in-line below (although this notation may > derail defective HTML presentation of plaintext containing angle brackets). > > Re-subscribing to general-incubator now ... > > Oh, and congratulations on joining the IPMC, Jan. > thanks a lot. rgds jan i > > -- Dennis E. Hamilton > dennis.hamil...@acm.org +1-206-779-9430 > https://keybase.io/orcmid PGP F96E 89FF D456 628A > X.509 certs used and requested for signed e-mail > > > > -----Original Message----- > From: jan i [mailto:j...@apache.org] > Sent: Saturday, August 16, 2014 01:10 > To: dev > Subject: Re: DocFormats - Open source OOXML implementation > > On 16 August 2014 03:50, Peter Kelly <kelly...@gmail.com> wrote: > > [ ... ] > > Now, onto the fix: > > > > The library needs to have some way of checking that the HTML file being > > used as part of an update operation has a mapping (id attributes) that > > match the docx file being updated (in the case of creating a new file, > this > > is just an empty docx file). In the even that this is not the case, it > > could still do the update, but would act as if the entire document had > been > > replaced with a completely new one. > > > > The solution I'll likely implement (and this should really be my first > > task, given the potential for problems like the above is this): > > > In my humble opinion you should not use time on this right now. > > If you fix a bug we have a 1-1 relation (1 man used, 1 bug fixed) > If you start getting the documentation right we have a 1-n relations (1 man > used, n men help fix bugs). > > Please have in mind, we build a community in order to move away from "I > have to do it, because I am the only one who know how" and you are the most > important enabler of that......we need your knowledge in a file, so that > others can work. > > [ ... ] > > When the project (hopefully) enters incubator, we will automatically have > access to a bug tracking system (jira), and with that hopefully only being > some month away I would not recommend setting up one now. > > <orcnote> > On Github, there is already an issues structure, > <https://github.com/uxproductivity/DocFormats/issues>. > I think this should be continued in use until a different > setup arrives "any day soon". Note that some Github projects > create a single subrepository that is just for its issues > function. E.g., https://github.com/keybase/keybase-issues > </orcnote> > > > [ ... ] > > >
