<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Feb 11, 2013, at 1:34 PM, Kevin Ollivier <<a href="mailto:kevino@theolliviers.com">kevino@theolliviers.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 11, 2013, at 12:27 PM, Benjamin Poulain wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Mon, Feb 11, 2013 at 11:27 AM, Kevin Ollivier <span dir="ltr"><<a href="mailto:kevino@theolliviers.com" target="_blank">kevino@theolliviers.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>I actually have recently been working on a patch to get trunk building again, though. The path of least resistance for me would simply be to ask people to ignore the wx port in their changes, but leave it in the tree. git is much better about these things, but I still remember what a pain it was to maintain the entire port in an svn branch back in the day, and I'd rather not re-try that experiment unless I really have to. If people feel strongly that I should approach things another way, though, I'm certainly open to ideas.</div>
</div></blockquote><div><br></div><div>Asking people to ignore wx is basically the same as having the code outside the tree. Having the code outside the tree would make this change effective instead of having one more rule to the project.</div>
<div><br></div><div>Looking at the history of wx's WebKit and platform code, the vast majority of changes are from Apple/Google. I think it is unfair to have many people maintain your code while you develop the project outside of the tree.</div>
<div><br></div><div>Given the data, I am in favor of removing the wx port from <a href="http://webkit.org/">webkit.org</a> and have it be a separate tree on Gitorious or GitHub.</div><div>What are the main pain points of developing outside <a href="http://webkit.org/">webkit.org</a> for you? Is there anything that can be done in the structure to simplify such changes?</div></div></blockquote><div><br></div><div>My big concern is not losing history while moving the wx files out of the tree and into a git branch, and also at the same time not losing the ability to merge the rest of trunk safely. Though I haven't investigated the process yet, so I don't know how easy or hard it may be. </div></div></div></blockquote><br></div><div>If you create a github repository by forking from the canonical webkit github repository, you'll have history for all the wx files and a good way to merge from trunk at times that you find convenient. I think that's the motivation behind the suggestion.</div><div><br></div><div> - Maciej</div><div><br></div><br></body></html>