On 6/26/13 2:53 PM, Rob Weir wrote: > On Wed, Jun 26, 2013 at 8:44 AM, Jürgen Schmidt <jogischm...@gmail.com> wrote: >> Hi, >> >> today I have received a zip file with patches related to the OSBA >> sponsored OOXML improvement project [1]. >> >> Regina came up some time ago and after some private email exchange with >> a list of git commit id's from one of the contractors. But I assume >> nobody was able to take a closer look on this or was able to extract the >> related patches and necessary information at this time. >> >> The patches are for the use-cases 1-4 and use-case 5 will follow. I have >> also asked for a detailed use-case description and test documents. As >> soon as I can provide more info I will share it here on the list. >> >> The OSBA contracted two companies to work on the defined use-cases and >> paid for the implementation. The project scope was from the beginning to >> make these improvements available in LibreOffice and in OpenOffice. >> >> Unfortunately for us the work was done on the LO code base and it means >> that we have to merge the changes in our code base if possible at all. >> >> Currently we are in the AOO 4.0 release phase and I believe we all have >> other things to do. But in the scope of AOO 4.1 it would make sense to >> take a closer look on this improvements. Maybe together with a general >> goal to improve the OOXML support in AOO and to provide an export as >> well. I am at this point of course not interested in a political >> discussion about document standards ;-) Our goal should be to satisfy >> our users and to provide the best free office suite to fulfill their >> requirements. and OOXML is (if we like it or not) an ISO standard as well. >> >> Anyway I would like to make the patches (that are all under ALv2) >> available for all who are interested to help with the review and >> integration. The patches will be soon available on the OSBA webpage as >> well. >> >> Any suggestion where I should store the patches in the meantime to make >> them available? >> > > This is good news. I'm not sure all of the code will be interesting > for us, but we can "cherry pick" the good parts. > > Where to put it? > > 1) Attach to BZ issues if they are small
for now I prefer an issue and the new issue can be seen as meta issue https://issues.apache.org/ooo/show_bug.cgi?id=122598 Juergen > > or > > 2) Create a top level /osba-patches directory in SVN and put them > there, with a readme that explains what they are and that they have > not been released by us yet. (Look at /symphony for example of this) > > > At the point we're interested in actually merging this, then we > probably want to do that in a branch. But that is post 4.0. > > Regards, > > -Rob > > > > >> >> [1] http://www.osb-alliance.de/working-groups/wg-office-interoperability/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
