Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audit of online documentation for Livepeer #8

Closed
chrishobcroft opened this issue May 10, 2018 · 2 comments
Closed

Audit of online documentation for Livepeer #8

chrishobcroft opened this issue May 10, 2018 · 2 comments

Comments

@chrishobcroft
Copy link
Contributor

Currently we have the following repositories of content for Livepeer:

  • readthedocs
  • wiki
  • forum
  • github
  • livepeer.org
  • livepeercommunity.org

It is unclear to me the distinct purpose of each of these repositories, and what content belongs where.

This issue proposes an audit of what content currently lives where (the "as is"), in order to inform some decision making about what content should live where (the "to be").

@dob
Copy link
Member

dob commented May 10, 2018

Here's my take on the purpose of these platforms:

ReadTheDocs - official developer focused documentation for the Livepeer node. How to run the node to broadcast, to transcode, what the command line options means, how to run private networks, test networks, how to run local eth node vs remote node, etc. Needs to be maintained actively.

Wiki - Open community wiki for any reference content that needs to be maintained and updated and serve as a source of truth. Anyone can create a page on the wiki to share anything. The content can be formatted, linked to, and updated. It doesn't need to be official documentation. The SPEC and the FAQ are great examples. Content is likely not meant to solicit feedback or spur a discussion - if so it may better belong in the forum.

Forum - Discussion threads. Q&A. This is content that is likely temporal in nature and will likely be responded to with questions or suggestions. It is not necessarily maintained over time, so if the content is a tutorial that needs to be kept up to date, then put it on the wiki, since there's no expectation anyone go back and update their forum post.

Github - The code. README's for the code and development of a particular repo or project, but not necessarily for the product. For example, ReadTheDocs is how to use the node as a product, with documentation for all the features. The README may contain a little overlap, but largely should focus on how to develop the node.

Livepeer.org - web site for the project. I think we know what this is.

livepeercommunity.org - experimental content homepage for the livepeer community node. It's whatever the community wants it to be!

reddit - I actually think that this could be a great entrypoint for mainstream community members who want to engage in and discuss things around the project. But it would require us to actually participate actively by submitting content and engaging in discussion. And I don't think it's a priority to force this if no one here is doing it organically.

I think the most overlap/ambiguity is likely to come between ReadTheDocs and the Wiki. What is an example of a piece of content that someone is not sure what the proper home is?

@Randy1Burrell Randy1Burrell mentioned this issue Jun 19, 2018
@dob
Copy link
Member

dob commented Nov 6, 2018

Closing this as out of date and non-actionable at the moment. Can revisit docs when productizing for scaled video developers.

@dob dob closed this as completed Nov 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants