On Thu, Nov 3, 2011 at 7:32 PM, Ryan Leavengood <leaveng...@gmail.com>wrote:
> The primary problem with our port right now is some of the developers > made the choice (which I objected to) to make our own Subversion repo > containing the WebKit code to make it easier (in their eyes) to > develop the port. > > Where can we go from here? What does the WebKit project need to see > from the Haiku maintainers to have us be a supported port again? It seems like either you should be a private fork/port, or a public upstreamed one, but not both. If you want to live in the upstream tree, I think most of your development work should land quickly in public. If you want to work in a separate repository without landing changes back upstream quickly*, I think it's better to stay private until the point at which that changes. *At most I don't think your private repo should be more than a couple weeks off the public repo. Based on our experience with the Chromium port I think it would be far easier on your group to be public and do development directly in the public tree. PK
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
