Consider adding something about logging in the Developer Guide, possibly in this ticket or create another ticket.

On a closer look, the Developer Guide seems a more appropriate place than the log Doxygen to add the logging guidelines, as these guidelines are for science pipeline developers to use logging, not about the full features/documentations/implementations of the log pacakge.
Also, log has been used by qserv but how they use it is beyond the scope of RFC-203.
For example, logging usage in Python is differernt for science pipeline and qserv.

Jonathan Sick may you please review this addition to the Developer Guide, as well as the removal of the limbo warning in the log Doxygen for before RFC-203 got approved?

Originally I wanted to add the example code (tracing.py) to the log package in its examples/ folder, and include the example in the Developer Guide. Is there cross-package referencing I should use?

I'm not sure about the policy regarding editting the Developer Guide; should Kian-Tat Lim also be included as a reviewer?

Most of the Developer Guide can be edited like any other documentation: 1) freely, 2) with review if thought appropriate, and 3) with an RFC if anything is likely to be controversial. Certain marked parts of the Developer Guide (generally ones that say "SHALL" or "MUST") 4) must be explicitly approved by me first. This ticket appears to fall into the first category.

Thanks Hsin-Fang Chiang, I’ll do a review over lunch. Looks great on first glance.

A couple notes:

• I think that eventually a lot of the practical Stack-centric developer documentation from the Developer Guide will end up in the Pipelines documentation. I have no problem at all including this in the Developer Guide now for usability, but once https://pipelines.lsst.io is fully realized, we’ll do some refactoring of content like this.

• Yeah, there isn’t a way to do literalincludes across Git repos (or against any URL) yet. I’ll probably have to build this, thanks for the reminder.

Looks great and is well written. PR contains a few suggested improvements before merging.

Jonathan Sick thank you very much for your detailed review and thoughtful feedbacks! Suggestions are incorporated and it's now merged.