I'll add that now that <a href="https://github.com/WebKit/webkit" target="_blank">https://github.com/WebKit/webkit</a> uses the same hashing as <a href="http://git.webkit.org" target="_blank">git.webkit.org</a>, it'll be trivial for folks wanting to have their own ports to fork on github and maintain svn history.<div>
<br></div><div>Maybe we should even encourage that for new ports: initially forking WebKit on github to create their port and then wait until it gets enough tractions to land it on trunk.</div><div><br></div><div>Meanwhile, are there anything we can do as the WebKit community to help maintaing a one-man port like Wx in the future? e.g. rebumping build systems, etc...</div>
<div><br></div><div>- R. Niwa</div><div><br></div><div><div class="gmail_quote">On Mon, Feb 11, 2013 at 1:51 PM, Ryosuke Niwa <span dir="ltr"><<a href="mailto:rniwa@webkit.org" target="_blank">rniwa@webkit.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>On Mon, Feb 11, 2013 at 1:34 PM, Kevin Ollivier <span dir="ltr"><<a href="mailto:kevino@theolliviers.com" target="_blank">kevino@theolliviers.com</a>></span> wrote:<br></div></div>
<div class="gmail_quote"><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><br><div><div><div><div>On Feb 11, 2013, at 12:27 PM, Benjamin Poulain wrote:</div><br><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/" target="_blank">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/" target="_blank">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></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><div><br></div></div></div><div>I kindly ask you to let us remove it from trunk in that case.</div><div><br></div><div>Given that we have 400+ contributors, having a port that's only maintained by a single person on trunk imposes a significant maintenance burden on others even if you said that people can break Wx port because not everyone reads this thread and wouldn't necessarily know your intent.</div>
<div><br></div><div>- R. Niwa</div><div><br></div></div>
</blockquote></div><br>
</div>