dzamo commented on a change in pull request #2138:
URL: https://github.com/apache/drill/pull/2138#discussion_r552524939
##########
File path:
_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md
##########
@@ -137,8 +136,11 @@ JIRA's automatically sent messages. If you change your
mind, note this in a
new comment, rather than editing an older comment. The issue should preserve
this history of the discussion.
+### Welcome to update the docs together!
+
+We shared the opinion that these do not need the full `JIRA -> PR -> Review ->
Merge` cycle. Welcome to join our `Slack` discussion and update the document,
we can quickly push these changes. (Mistakes in `gh-pages` branch can't hurt
users' deployments.)
Review comment:
### Contributing documentation
Documentation contributions are most welcome and there are many
opportunities for them including
1. features which have been implemented but not completely documented and
2. HOWTOs for using Drill with other popular software.
Documentation committed into the `gh-pages` branch does not have any effect
on the Drill code base and so does not require a JIRA ticket or a corresponding
PR from a repo fork. It does still require a Drill committer to check it and
push it into the Drill code repo. This means
1. Drill committers can add documentation with little overhead.
2. Anyone can easily send documentation to a Drill committer (find us on
Slack or the mailing lists) as markdown or plain text and she/he can
incorporate it for you with little overhead.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
