grpc.io icon indicating copy to clipboard operation
grpc.io copied to clipboard

Migrate documentation from grpc doc folder to the grpc/grpc.io repository

Open remyleone opened this issue 4 years ago • 10 comments

Currently, I see two main sources of documentation for the grpc.io:

  • There is this website, generated by hugo.
  • There is the doc folder in the grpc repository: https://github.com/grpc/grpc/tree/master/doc

I think it would be a good idea to have a centralized place for the documentation so that contributors know where to contribute new content.

I would suggest to migrate it here as it will have a clean URL that will make it easier to find through a web search.

remyleone avatar Mar 01 '20 23:03 remyleone

From what I can gather, the docs in grpc/grpc are intended for developers of gRPC, whereas the docs here are intended for people writing gRPC-based services. I’m not sure it’s advisable to combine these sources into one. Though I do think that (a) the purpose of each source should be made more clear on both sides and (b) any info that’s in grpc/grpc that may be of use to end users should be added to these docs.

lucperkins avatar Mar 12 '20 05:03 lucperkins

I think having a single site with clear content architecture (user of gRPC / developer of gRPC itself) could build a large audience. This website could help create bridges between the two communities and improve communication for both.

remyleone avatar Mar 12 '20 07:03 remyleone

@srini100 - office hour cc

muxi avatar Mar 18 '20 18:03 muxi

@muxi Could you please explain why you added this comment to 10+ issues today?

lucperkins avatar Mar 18 '20 20:03 lucperkins

@lucperkins, sorry, that's the process for the grpc team to delegate the issues if no activity is seen for a week. Should we change it to ping you instead?

srini100 avatar Mar 18 '20 21:03 srini100

@lucperkins, if there is an assignee then we won't triage the issue. Please set the assignee if you can.

srini100 avatar Mar 18 '20 21:03 srini100

@srini100 Understood! And good to know for the future. This issue is currently in the discussion phase so no assignee yet.

lucperkins avatar Mar 18 '20 21:03 lucperkins

I've seen a similar setup as a part of other projects where the main project repo docs are considered "engineering notes", best maintained by core project developers.

That being said, I do believe that there is duplication in some of the documentation. For example, the last section of the Java tutorial refers the reader back to the Java examples README. But the README contains instructions that are already found in the Java Quick Start. There might be an opportunity to clean things up a bit here.

chalin avatar Mar 20 '20 20:03 chalin

Office hour ping to participants. This issue is still not assigned to anyone and not active over two weeks.

dapengzhang0 avatar Apr 15 '20 18:04 dapengzhang0

Assigning to @chalin, so we can skip this in our triaging effort each week. This doesn't mean this issue is actionable yet.

srini100 avatar Apr 15 '20 18:04 srini100