Hi guys,
I found out we separate our code repo and docs repo into two different
repo:
https://github.com/apache/dolphinscheduler-website
<https://github.com/apache/dolphinscheduler-website> and
https://github.com/apache/dolphinscheduler
<https://github.com/apache/dolphinscheduler>.
I don’t know the original reason, but IMO we should combine the docs and
codebase into same repo.
It is have several advantageous as below:
* when we change our behavior, we could modify related doc to keep our doc up
to date
* when we release our code we could also release our doc, (docs follow our
code), could make our doc versionable
* when adding a tag for specific commit, docs would include with it(base on
first point)
So, I proposal we could combine docs into codebase repo
And here are some of other Apache repo which codebase including docs
* Apache Spark: https://github.com/apache/spark/tree/master/docs
<https://github.com/apache/spark>
* Apache Flink: https://github.com/apache/flink/tree/master/docs/content/docs
<https://github.com/apache/flink/tree/master/docs/content/docs>
BTW, we could still keep https://github.com/apache/dolphinscheduler-website
<https://github.com/apache/dolphinscheduler-website> repo and make it just an
site
for our leading page
Best Wish
— Jiajie
