Quoting Andrew McGlashan ([email protected]): > Okay, I was wrong then. However, Chromium is still, in some respects > "Google property". Not sure which one gets updates first or how well > they bounce those updates back and forth.
The code checkins occur at the Chromium repo, which is a rolling codebase with (usually) multiple daily snapshots. Occasionally, Google decides to take a snapshot of the code, add in proprietary extras, and release that as the next version of Google Chrome. Yes, certainly Chromium is in some respects 'Google property', in that although anyone has the right to fork, only very rarely does anyone presume to do so, on account of maintenance being a gigantic job. (One example is the ungoogled-chromium browser. There are also a number of non-Google proprietary browsers based on Chromium.) I am unclear on whether Google accepts code contributions from non-employees into its repo for Chromium. -- Cheers, "I suppose the process of acceptance will pass through the usual Rick Moen four stages: (i) This is worthless nonsense; (ii) This is an rick@linux interesting, but perverse, point of view; (iii) This is true, mafia.com but quite unimportant; (iv) I always said so." -- JBS Haldane _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
