Hi,
On 18 Oct 2007, at 18:17, Pavel Janík wrote:

I think I did my time

Thank you, Eric.

and I'm glad to announce Shaun McDonald is the new Mac OS X project Lead.

?

As I already said on releases:

1. Mac port is not a project. It is a subproject of the development project (porting).

I thought the porting project was a sub-project of the big project OpenOffice.org.


2. even if it is, the usual way is to vote on candidates, if they agree to be candidates..

I'm happy to be a candidate.


I already discussed my vision of the Mac port with Shaun, here are my ideas:

- we should go back to our project, OpenOffice.org. We are too separated now.

- we are development sub-project of porting project. We should behave as such.

- we should get marketing and other projects to do part of the work we did in the past

I trust him, and agree with his Vision of what should be the Mac OS X port.

I'd like to hear Shaun's vision first to be able to judge it. Can you send us the vision Shaun has?

Here is my vision for the future of the Mac Port of OpenOffice.org:

I'd like to see the Mac Port to no longer be just a port of OpenOffice.org, rather be integrated with the rest of OpenOffice.org, just like Windows, Linux and Solaris. If there is some major work such as platform integration on a particular component, then Mac OS X should be done too, and not just left behind. When there is platform integration work specific to a particular platform it doesn't really matter whether the other platforms have it done too. One recent example of this is the platform integration for extensions, which still hasn't been implemented for Mac OS X.

I believe that we have already reach an important step in this process some time time ago, as it is now considered that integrating a CWS that breaks the Mac platform is not allowed.

I would like to see OpenOffice.org to in the first instance become a stable Mac application, with basic integration with the platform. This is almost done now. Thereafter we should work on making OpenOffice.org more mac like in many other ways. Some of this has already started, for example extra QuickLook support in Leopard. Another example is a discussion that happened in Barcelona where Jogi came up with removing the grey no document screen, and replacing it with an improved templates dialog. Other basic things like the native print dialog are also required early on in the development.

Later we can move on to other things to implement, such as some of the new Leopard features, such as Calendar/ToDo integration (or maybe this would be better done as an extension rather than implemented in the core of OpenOffice.org).

To integrate the Mac platform within the project more, we need to move the many things that the mac port has been doing over to the other parts of the project. For example we should have a few people on the marketing project, so that the marketing project are always up to date. We should have a few people in the user experience (ux) project to help make sure that any decisions there don't conflict with the Apple HIG, or our the vision of OpenOffice.org on the Mac. We need people who know the mac platform to answer user's questions on the OpenOffice.org forum, and on the users list.

We should use the skills of everyone to the best use for the project, but instead we sometimes need to move them to other sub-projects of OpenOffice.org. Opening up communication between the sub-project is essential to prevent the left hand saying something different from the right hand.

I'm hoping that within the next 2 years there will no longer be a Mac porting project, because Mac OS X will be a major platform that OpenOffice.org on runs on.


Shaun


And be asured, that I do not want to be a candidate for the "lead" of Mac port!
--
Pavel Janík


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to