Componentization wants YOU

[Colin Blundell]

Hello Chromium engineers,

Would you like to enhance the maintainability and scalability of Chromium, gain broad exposure to the Chromium codebase, and aid the integration of the iOS port? The componentization team has the perfect opportunity for you!

The team has more work on our hands than we can handle on our lonesome at any given time. This work comes in all shapes and sizes -- anything from contributing CLs to helping burn down a bugtree to designing and executing a feature componentization -- and much of it can be done by any motivated Chromium engineer! If you're interested in getting involved, please contact me.

Best,

Colin 

[Lei Zhang]

Is there a list of things that need componentizing? Some concrete
details might help others decide whether they would like to jump
onboard or not.

> --
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev

[Colin Blundell]

Hi all,

Yes, there is (now) such a list (thanks for the excellent suggestion, Lei)!

If you're interested in one of the features marked "Available", email me and we can discuss how best to proceed.

If you're interested in one of the features marked "Started", email me and the owner of the bug and we can likely find some work for you to contribute toward the feature's componentization.

Thanks,

Colin

[Shezan Baig]

Hi Colin,

I don't see "chrome/browser/spellchecker" in that list.  Do you still plan to componentize spellchecking?

Thanks,

-shez-

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Lei Zhang]

I was just thinking of writing it as C14N yesterday.

[Colin Blundell]

Hi Shez,

No, spellchecker is not on the list at this point.

Best,

Colin

[Ryo Hashimoto]

Hi Colin,

Thanks for sharing the task list.

IIUC, basically, componentizing a directory means moving as much code as possible from chrome/browser/foo/ to component/foo/, right?

Do we have some kind of guideline which helps developers decide which code to be moved to component/?

[Colin Blundell]

Hi Ryo,

That's basically correct; rather than "as much code as possible" I would say "the code that is not specific to the Chrome embedder." What we've used as a rough guideline is: Is the code used by the iOS port? If it is, then it almost certainly should be componentized. If it's not, it still *might* make sense for it to be componentized but the priority would be much lower. If you're interested in a feature for which componentization has not yet begun, the first step would be to talk to me and we can coordinate working through the design phase of the componentization.

I've also started a hotlist for bugs that are ripe for being tackled by any interested party. I will add to this hotlist over time as bugtrees get created for individual feature componentizations.

Best,

Colin

[Colin Blundell]

Hi all,

I have brought the Browser Components design doc and cookbook up-to-date to take iOS into account (notably, mentioning layered components) and to document the componentization process that I and my team use, which is different in some ways from the one that Jói's team had employed. If you're interested in componentization, start with those and let me know where there are holes to fill!

Thanks,

Colin

[Ben Goodger (Google)]

Another concrete example that relates to a subset of src/chrome code: is this code needed by any other module outside src/chrome, e.g. src/ash? Good examples are much of the code in src/chrome/browser/chromeos which could live in src/ash, src/ui/* or src/chromeos.

-Ben