Blink Doc-a-thon Details

29 views

Skip to first unread message

Yuta Kitamura

unread,

Jul 5, 2017, 4:06:17 AM7/5/17

to blink-dev, ato...@chromium.org, Michael Paddon

Hi all!

As I announced, Blink Doc-a-thon will be held from next week!

I've drafted a short document describing rules & regurations:

https://docs.google.com/document/d/1FbEPu1AR6bDYwjNSR4M6XDEEDLllM2cv7c6o2L_IVOg/edit?usp=sharing

If you have any questions or suggestions, please let me know!

PS. The placeholder bug number XXXXXX will be replaced with the real number before the event starts.

Thanks,

Yuta

Kentaro Hara

unread,

Jul 5, 2017, 4:15:49 AM7/5/17

to Yuta Kitamura, blink-dev, ato...@chromium.org, Michael Paddon

Thanks Yuta-san for driving this!

I just want to emphasize that we're aiming at:

- adding README.md to all directories. If you have documents outside the code base, it's fine to just add the links to those documents to README.md. What matters is that people can fine necessary resources just by looking at README.md.

- adding class-level comments to all classes. At least newly added classes should have class-level comments.

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFJcur9xXPH1eRd%2ByckRN74AiW%2BoukbOvMRas46P4NoCmKcGag%40mail.gmail.com.