Add different kinds of custom built-in trees to the library

I think that implementing DebugTree as a built-in custom tree inside the library, is a great way to show the users how to properly and efficiently extend and use Tree class.

While searching the web for a custom tree, for example, which log his messages into a local file, it seems that there are different implementations which obviously have different implications, because there is no one centralized reliable resource for the specific example custom tree.

IMO, it will be very productive for the users if trees/ directory will be added at java/timber/log directory root path and opportunity will be given to contributes to share their general-purpose reliable custom trees with the rest of users, in trees/ directory.

[JakeWharton]

Do you have specific ones that you’d be interested in having out-of-the-box? I’m more interested in specific, widely applicable use cases.

I’m definitely not interested in accepting and maintaining a large portion of trees. It’s not scalable for me, everyone thinks their special case is a general case and wants it in the main repo, and the APIs to configure the behavior of these will become a tragedy of the commons.

I can create a wiki page where people can link to their third-party tree with a one-liner description. How’s that?

[tasomaniac]

What about having them in the sample app? That way, people will probably copy paste and easily modify to their needs in the project. Could be better than shipping it with the lib.