This document is largely outdated as most, if not all, of the ideas represented here have been accomplished by the project as a whole. The ideas reflect some of the steps we've since taken to make the WebKit Open Source Project more supportive of the multiple organizations and ports that are now contributing.
This page describes some of the ideas we (as in the Qt WebKit team) have for the WebKit project as a whole.
We would like the WebKit community to be a strong and positive group of people that works together towards the common project goals. We believe that all of the ideas we list underneath will help further these goals.
Commit and review rights
- What is the algorithm to obtain commit and review rights? The community should have a say in this.
- The same policy should apply for every possible contributor.
- There should be platform maintainers who have the right to decide on commit and review rights for the platform specific parts of the code.
- Platform maintainers need to have decision rights about the platform specific code (e.g. which kind of patches go in, which don't)
Project planning should become more transparent. The mailing list should be used for larger discussions or decisions that affect all platforms, to give all involved parties a chance to comment.
- Platforms need to have an idea of when to expect the next stable WebKit version.
- We believe there are should be common releases for WebKit
- A release can simply consist of a branch
- The core engine should be in a stable state for a release branch
- Releases should have a well defined WebKit version number
- Releases should be time based
- Release schedules and a (loosely defined) roadmap should be discussed and agreed upon inside the community.
The WebKit project page should reflect contributing organizations in an equal fashion.
- The webkit.org/blog should aggregate the blogs of all contributors (Surfin' Safari and blogs of external contributors)
- The main webpage and the navigation bar should be platform agnostic
- Safari specific things should go in a subpage (with a prominent link form the main page)
- A free use WebKit logo would be great to have