-
Notifications
You must be signed in to change notification settings - Fork 41.4k
Docs contribution section #25374
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
Docs contribution section #25374
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. Can you share what made you create a dedicated section for the documentation? I'd rather keep a general contribution section (perhaps improving it?) rather than creating a dedicated section like this.
|
||
The documentation is stored in this repository, in the link:https://github.com/spring-projects/spring-boot/tree/master/spring-boot-project/spring-boot-docs/src/docs/asciidoc[spring-boot-docs] project. | ||
|
||
You may use GitHub's built-in editor for Asciidoc by pressing the top-right Edit button to edit the documentation in browser. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure we should bother describing the various ways changes can be contributed on GitHub. As a matter of a fact, I prefer contributions that originate from "real branches" as it makes the follow-up easier. We expect contributors to build the documentation and check that the output is valid which you cant' do using the web editor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't there automatic checks (doc build) on a PR request even when using the github's web editor?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A contributor is expected to validate their changes before submitting a PR and I am not keen to let contributors use our CI infrastructure to validate their changes.
Part of that is because if you keep this trial and error until you push something that works, you'd trigger a notification for each commit attempt to the 3K people watching this repository.
Having said that, I can see how simple documentation changes could be easily validated from your browser.
The documentation is stored in this repository, in the link:https://github.com/spring-projects/spring-boot/tree/master/spring-boot-project/spring-boot-docs/src/docs/asciidoc[spring-boot-docs] project. | ||
|
||
You may use GitHub's built-in editor for Asciidoc by pressing the top-right Edit button to edit the documentation in browser. | ||
Alternatively, you can clone and change it in an editor of your choice on your machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure what that sentence brings to this section.
Contribution section needs a guide to editing docs (#23726 (comment)), to answer questions like:
|
I saw that but I am not sure why we should create a dedicated section for this. Flagging for team attention to get some more feedback. |
To me, the documentation is part of the project's code. I think a subsection in the "Working with the Code" section, describing where the documentation lives and noting that it's written in Asciidoc, would be a good addition. |
No description provided.