Skip to content

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

Closed
wants to merge 1 commit into from
Closed

Conversation

cdalexndr
Copy link
Contributor

No description provided.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 19, 2021
Copy link
Member

@snicoll snicoll left a 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.
Copy link
Member

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.

Copy link
Contributor Author

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?

Copy link
Member

@snicoll snicoll Mar 1, 2021

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.
Copy link
Member

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.

@snicoll snicoll added the status: waiting-for-feedback We need additional information before we can continue label Mar 1, 2021
@cdalexndr
Copy link
Contributor Author

Contribution section needs a guide to editing docs (#23726 (comment)), to answer questions like:

  1. Where are the docs stored?
  2. What format do the docs use?
  3. How can I edit docs?

@snicoll snicoll added the for: team-attention An issue we'd like other members of the team to review label Mar 1, 2021
@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Mar 1, 2021
@snicoll
Copy link
Member

snicoll commented Mar 1, 2021

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.

@wilkinsona
Copy link
Member

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.

@philwebb philwebb added for: merge-with-amendments Needs some changes when we merge type: documentation A documentation update and removed for: team-attention An issue we'd like other members of the team to review status: waiting-for-triage An issue we've not yet triaged labels Mar 17, 2021
@philwebb philwebb added this to the 2.5.x milestone Mar 17, 2021
@philwebb philwebb self-assigned this Mar 17, 2021
@snicoll snicoll modified the milestones: 2.5.x, 2.5.0-RC1 Apr 12, 2021
@snicoll snicoll assigned snicoll and unassigned philwebb Apr 12, 2021
snicoll pushed a commit that referenced this pull request Apr 12, 2021
@snicoll snicoll closed this in 613462a Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: merge-with-amendments Needs some changes when we merge status: feedback-provided Feedback has been provided type: documentation A documentation update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants