Thanks @souravsingh, but I think this is a little basic for a tutorial. Maybe move into the examples?

So far, this is just a minor rewrite of the existing log demo. C.f.

existing log demo
this PR

@souravsingh I assume you are going to expand on this. OTOH there's no need to open a PR in this early stage. PRs should be opened when the feature is either complete or if you need feedback on certain aspects before completion.

@timhoffm Yes, It is a minor rewrite of the existing demo, which I intend to extend by adding tick behavior and symlog. I opened the PR early so I can get iterative feedback for the PR.

@souravsingh Thanks for the explanation. Please keep in mind that our review capacity is limited (actually it‘s one of the main limiting factors in the development).

That said, there is no general rule when to submit a first version. If it‘s too early, we‘re wasting reviewer time, if it‘s too late, the PR may go in the wrong direction and needs correction, which is extra work for the author. As a rule of thumb, a PR does not have to be polished, if you are having doubts. But in that case, it should at least demonstrate your ideas. Also, it helps a lot, if you your ideas and indicate the state of the changes.

We‘re happy to give feedback once this is more concrete.

Closing the PR since there is zero incentive for me in working on this.

@souravsingh I hope we don't have scared you off with our comments. Helping to improve the documentation is greatly apreciated.

Of course, the motivation has to come from within yourself. We can only give feedback and help along the way. I recognize that priorities and motivation can change, and that's perfectly fine. Maybe see you another time.