Hi all, over the few weeks and months the activities that led and lead to port OpenOffice.org 2.0 to Mac OS X have reached a level of complexy that makes some organization necessary.
A few points that need clarification are: - Who is in charge for the Mac OS X port. If you take a look at the mac porting webpage you might get the impression that still Edward Peterlin and Dan Williams are in charge or worse that nobody is in charge. So for outside developers and users a headless Mac Port is close to a dead Mac Port and they switch over to NeoOffice/J, iWork or stick with MSO. - Next decision to be made is: Who does the official build for Mac OS X. Currently we have at least five people building OOo. Eric B., Pavel Janik, Maho Nakata, Florian Heckl and me. And I don't know if any of the other who tried and talked about it on IRC had any success. To make it worse it looks like all five or more builders use different sources, patches etc and so we cannot say that m9x or so works because it is possible that e.g. my and Eric B's builds work but Mahos don't or the other way round. We have to make official builds and let them pass official QA. For QA Joerg Sievers offered his help in his freetime when he is not employed at SUN. For QA we would have a person in charge. Since Maho has a sponosored G5 now best would be if he could build some languages and additional language packs. Eric B. proposed this on IRC. I don't know but afaik Maho uses the NetBSD porting mechanism. The question is if this mechanism is needed or not when an user only wants to use OOo and not build it. E.g. If you want to run a fink app you need to have fink installed. Only thing that makes me curious about Mahos build is that Terry Teague for the second time reported that he cannot open documents with Mahos builds. We have to investigate on this. Maybe I can ask Joerg to do an QA on Mahos build. - Next point would be adding a decent installer that keeps it simple for Mac OS X users. Best would be to have this installer/launching app right out of the build process. A step in the right direction was Florian Heckl's Metapackage script that bundles the 17 single packages into one metapackage. Now it would be up to us to add the app Mox created into the installation process so that in the end you have an OOo.app and a click launches X11 and OOo. In the meantime Stefan Taxhet tries to organize a Mac OS X Tinderbox. Eric B. gladly offered to host this Tinderbox. If we have this Tinderbox we can use it for official builds. Remote access for others and such stuff is to be planed when the Mac is there. If we don't get it we need to find another solution for a tinderbox and an official build machine. As you may see by now there are a lot of tasks to take over but who could do the distribution of taks if we have no one in charge? So first we need a person in charge for Mac OS X port. Eric B came to a point with this sentence: We have 3 important priorities : stabilize/add decent installer/distribute the tasks With stabelize he means OOo but why not extend it to the community itsself. Regards, Eric Hoch -- ## Ansprechpartner Anwenderunterst�tzung, users-Mailingliste, MacOSX ## de.OpenOffice.org - Office f�r MacOS X, Linux, Solaris & Windows ## Openoffice.org - ich steck mit drin! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
