Re: Maintainer nominations
toggle quoted messageShow quoted text
I think that it is important not to conflate things. There's a request to add two maintainers who's role will be
to help manage the Fabric documentation. I think that should be handled independent of any discussion of repository disposition.
Let's please address the two PRs for Chris and Joe independent of this broader discussion.
The generated documentation *should be* generated from the source code, and should most certainly NOT be
segregated to another repository. The authored documentation, written by humans has for the most part been
developed by a mostly disjoint set of people than those who author the code. Now, it would certainly
be nice to ensure that the code and the documentation were kept in lock-step, and even managed such that the code and doc
(and tests) were all committed as a unit; but that has almost never been the case, and it is rare to see it in practice.
There's a different skill set in developing good documentation than there is in writing good code. Both types of skills are important
to a successful project, and especially to one as significant as Fabric. I don't see a problem in having the authored content
managed in a separate repository.
Another factor is that we wanted to integrate the i18n translations and associated workflow that us currently managed
as a Hyperledger Lab process to formally incorporate it into the same repository as we manage the english source
for the documentation. We had previously discussed reconsidering that when we had separated the docs from the
core Fabric repo, as Dave had suggested. I do think that we need to revisit all of that now that we are finally over on GH.