On Tue, 2014-01-07 at 10:02 -0800, Ketrenos, James P wrote: > For the TL;DR: I am for having a single team/owner responsible for > Chromium/Blink in Crosswalk. I'm not sold on the notion of having the > original owner of a feature have to continually re-visit "completed" > work in order to keep that feature in a newer version of Crosswalk.
Thanks for the feedback, James. > However, this proposal diverges from the BKM illustrated by most open > source projects. From the community vantage point (3rd parties, other > business groups, etc.) landing something in upstream (to them) means > landing it in Crosswalk. In the Linux kernel world (and other open > source projects) once a feature has landed in upstream, rebasing is > done by the upstream community. In our approach, we are saying landing > it in Crosswalk means you are going to own that feature forever, and > if you don't, it may be deleted. It's a fair point, but Alexis mentioned already some examples in upstream projects near to us in which code that is not being maintained is removed. It's also important to note that is not 100% of contributions that need changes to Chromium/Blink. The proposal already made the case for the shift of responsibility based on - the fact we consider being able to update early and often a major feature of Crosswalk -- and by not keeping up we somehow "regress"; - and our current experience with large patches that are good candidates for upstreaming but end up not being upstreamed because there's no motivation to (or time!), and end up impacting the updates. I'd add that shifting the responsibility the way we did make the task less daunting for the person that will be taking care of the trees. Of course, if she/he/they decide that it's better to adopt some or all the topic branches, I'm fine with that. A proposal to move forward: could we take this as a starting point and let the person/people responsible for the tree refine the rules of who should maintain things? Cheers, Caio _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
