Add [Treeware] badge

[owenvoke]

This is related to #4728, it adds a badge for the Treeware project.

The badge this adds contains tests, and displays the trees that have been planted by a package (based on a referer hash).

[shields-ci]

	Messages
📖	✨ Thanks for your contribution to Shields, @owenvoke!

Generated by 🚫 dangerJS against d02c3a9

[chris48s]

Thanks for working on this. I've left a couple of comments inline

[PyvesB]

Thank you for your contribution @owenvoke ! I've added a few suggestions and questions in addition to @chris48s 's review. 😉

[PyvesB]

We also have a fundingcategory, Not sure which one is more appropriate, what do you think?

[owenvoke]

I wasn't sure about this, I guess funding is probably more appropriate. 👍

@jamesmills, I was just interested what you'd suggest for this?

[Gummibeer]

I think that funding would be okay, but I want to throw in license as well. Because it's part of the license and not an optional funding.
The point is that every user is required to be trees if he uses the Treeware licensed software in production.

[jamesmills]

We actually leave it to the package maintainer to decide how to work the Treeware "condition of use". We currently have two in the wild.

This package is free and open-source, under the MIT license. Use it however you want. This package is Treeware. If you use it in production, then we ask that you buy the world a tree to thank us for our work.

You're free to use this package, but if it makes it to your production environment you are required to buy the world a tree.

In the first example, it's attached to the licence. However, the maintainer can decide how to word it.

I think it's a licence and would be happiest with this option.

[owenvoke]

I've applied the requested review comments, and commented where necessary. 👍

[chris48s]

I think this is good to go. The fact that we're not sure which category to put it in is probably an indication that "other" is OK
Thanks for your work on this

[PyvesB]

Agreed, let's get this merged! Thanks for addressing the review comments promptly! 👍

[Gummibeer]

Thanks for merging it! 🚀 Is there any plan on when this will be deployed?

[PyvesB]

@Gummibeer deployments happen on a regular basis, but it's a manual step that can only be done by a couple of the maintainers. So no precise ETA, but hopefully it won't be too long!

[PyvesB]

@platan there's no shields-deployment bot message here, any idea why? 🤔

[shields-deployment]

This pull request was merged to master branch. This change is now waiting for deployment, which will usually happen within a few days. Stay tuned by joining our #ops channel on Discord!

After deployment, changes are copied to gh-pages branch:

[platan]

@PyvesB Thanks for reporting this problem.
I'm not sure what was the cause of the problem. Logs in the app which handles webhooks form GitHub are empty. A webhook request send after merging this PR timed out (We couldn’t deliver this payload: Timed out message is available in the shields-deployment app settings). I redelivered this particular webhook request (it responded in 0.38 seconds) and comment was added.
Within the last year deployment-status worked properly 404 times (https://github.com/badges/shields/pulls?q=merged%3A%3E2019-03-28+base%3Amaster+-author%3Aapp%2Fdependabot-preview+%22This+pull+request+was+merged+to+master+branch.%22)
In 12 cases it didn't work (https://github.com/badges/shields/pulls?q=merged%3A%3E2019-03-28+base%3Amaster+-author%3Aapp%2Fdependabot-preview+NOT+%22This+pull+request+was+merged+to+master+branch.%22)