There isn’t one.
Yes and the result is the main docs, which as Bruce points out far too few consult before asking on the forum. We’ve also created a template to fill out in some categories and created lots and lots of posts which provide the answers to commonly asked questions. We tried creating a FAQ post awhile back but it wasn’t really populated nor used.
Even a post like the OP is frankly an attempt to herd cats. Users are going to read the docs or not read the docs and will do what they do. and get mad at us for asking them to read stuff already written instead of rewriting a custom response just for them.
The way the openHAB Foundation is incorporated in Germany as a specific type of non-profit, I don’t think they would be allowed to hire such a person. But there are several who contribute to and coordinate contributions to the docs. @Confectrician is the primary lead on that front right now.
But it’s also important to realize we are in a state of transition. Work on OH 2.x core is done and OH 3 is the main focus. OH 3 is going to require a significant if not complete rewrite of the docs. And since we have no idea what OH 3 will actually be or how it will work, we have to wait before we can initiate that effort.
What I do and what I encourage other forum helpers to do is if you answer the same question more than a couple of times, create a new post that is easily findable and link to that post for subsequent answers. Once that post has seen some exposure and been polished, consider moving the contents to the docs.
But did you look in the docs? Here is the docs for cron triggers.
A cron expression takes the form of six or optionally seven fields:
- Seconds
- Minutes
- Hours
- Day-of-Month
- Month
- Day-of-Week
- Year (optional field)
for more information see the Quartz documentation.
You may also use CronMaker or the generator at FreeFormatter.com to generate cron expressions.
It clearly states how many fields there are and even provides a link to a tool to help you generate the expression you are after.
This kind of leads back to me initial answer and Bruce’s comments. Almost all of the stuff that people struggle with are actually documented in the docs, sometimes in great detail. But far too often users don’t think to look there or don’t bother to.
Now, if there is anything unclear about the docs I quoted above, we more than welcome contributions, updates, and suggestions for improvement. There is a link at the bottom of the page that will take you straight to the form on GitHub where you can edit the source and create a PR to be added to the docs.