)]}'
{"README.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_85803e9f","updated":"2018-12-19 08:26:55.000000000","message":"This is a very long page, and is probably not suitable for a README. I believe most of this content is valuable into another documentation page though.\n\nI would reduce this page to say:\n\n1) OSH is an official OS project providing a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.\n\n2) Point to the following:\n- Home documentation page\n- Deployment guide main page\n- Developer Documentation main page (But I\u0027d call it \"Contributor\u0027s guide\" to not alienate some personas :p)\n- source code locations\n- ML/IRC\n\nThe rest of the content can probably go into an \"onboarding page\" which would be linked from the developer documentation.","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[{"line_number":12,"context_line":"Communication"},{"line_number":13,"context_line":"-------------"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"* Join us on `Slack \u003chttps://kubernetes.slack.com/messages/C3WERB7DE/\u003e`_ - #openstack-helm"},{"line_number":16,"context_line":"* Join us on `IRC \u003circ://chat.freenode.net:6697/openstack-helm\u003e`_:"},{"line_number":17,"context_line":"  #openstack-helm on freenode"},{"line_number":18,"context_line":"* Community IRC Meetings: [Every Tuesday @ 3PM UTC],"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f79a3b5_854d9ec7","line":15,"range":{"start_line":15,"start_character":2,"end_line":15,"end_character":90},"updated":"2018-12-19 08:26:55.000000000","message":"Even if there is a bridge, the official channel should be IRC, so I don\u0027t think this should be mentioned in the README.rst, but maybe as onboarding instead.","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}],"doc/source/devref/endpoints.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_659c0201","updated":"2018-12-19 08:26:55.000000000","message":"To be consistent with other upstream projects, I\u0027d change the folder for all the \u0027devref\u0027 documents to \u0027reference\u0027.\n\nThis would be the location of all the more detailed architecture/configuration/development would appear","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}],"doc/source/install/common-requirements.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_05298ea0","updated":"2018-12-19 08:26:55.000000000","message":"Install is probably the deployment guide, and therefore should be renamed deploy-guide, and moved to the root of openstack-helm-docs.","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}],"doc/source/operation/fluent-logging.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_452226ba","updated":"2018-12-19 08:26:55.000000000","message":"operation folder should be renamed \"admin\" as this is how to administer/manage the cluster. This is to be conform with latest docs specs.","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}],"doc/source/usecase/index.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_e50c9244","updated":"2018-12-19 08:26:55.000000000","message":"This folder should be renamed \"user\" as it explains what the users should do (user stories should be here).","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}],"tools/deployment/armada/010-armada-host-setup.sh":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"3f1fff0d8898b76a9ccb09fbcadff6c1601cd5d0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_f001ae03","updated":"2018-12-19 08:26:55.000000000","message":"Re-adding the file seem a bad idea. Instead, can we just rely on a relative inclusion mechanism, and force users to have the latest code git cloned next to this repository?","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"},{"author":{"_account_id":21830,"name":"Jaesang Lee","email":"jaesang_lee@sk.com","username":"jaesanglee"},"change_message_id":"df141aba654eb57ef44d568411fc9ef9e4f92b97","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"3f79a3b5_b002560c","in_reply_to":"3f79a3b5_f001ae03","updated":"2018-12-19 09:21:43.000000000","message":"I also want to solve this part. Since the document repository and the source repository are different, there is no way to include the source.","commit_id":"c7ba4196a87a8c9b56c1937a1388307a15e4700b"}]}