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

Copy documentation from gh-pages to doc/contribute #1707

Merged
merged 51 commits into from
Aug 12, 2020

Conversation

sarakonradi
Copy link
Contributor

@sarakonradi sarakonradi commented Jul 31, 2020

This PR copies content from the gh-pages branch into doc/contribute. It addresses the checklist items in #1659 related to the contributing guide.

More specifically, it

  • moves the NEST_Contributor_Agreement.pdf to doc/contribute
  • converts the Git workflow and C++ coding guidelines to RST
  • updates doc/contribute/index.rst
  • adds the "two reviewers" guideline to the contributing page

I did not remove too much from the Git workflow (yet), due to its references to NEST throughout. Please feel free to suggest which sections we can remove with clear conscience!

@terhorstd terhorstd added I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation. labels Jul 31, 2020
Copy link
Contributor

@jougs jougs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot! Nice to see all these pages coming home ;-)

I have a lot of small suggestions that I should probably already have had when the files were added to the developer space in the first place. In addition, here are some general remarks:

  • make sure Git is spelled consistently in regular text
  • I prefer repository over repo, please search and replace
  • I did not review the Eclipse and Xcode workflows, as I've never used those. @heplesser might be able to help.

doc/contribute/coding_guidelines_cpp.rst Outdated Show resolved Hide resolved
doc/contribute/coding_guidelines_cpp.rst Outdated Show resolved Hide resolved
doc/contribute/coding_guidelines_cpp.rst Outdated Show resolved Hide resolved
doc/contribute/coding_guidelines_cpp.rst Outdated Show resolved Hide resolved
doc/contribute/coding_guidelines_cpp.rst Outdated Show resolved Hide resolved
doc/contribute/development_workflow.rst Outdated Show resolved Hide resolved
doc/contribute/development_workflow.rst Outdated Show resolved Hide resolved
doc/contribute/eclipse_workflow.rst Outdated Show resolved Hide resolved
doc/contribute/eclipse_workflow.rst Outdated Show resolved Hide resolved
doc/contribute/xcode_workflow.rst Outdated Show resolved Hide resolved
@sarakonradi sarakonradi requested a review from heplesser August 10, 2020 08:40
@sarakonradi
Copy link
Contributor Author

@jougs Thanks for the detailed review! I have applied your suggestions and replied to your comments inline.

Copy link
Contributor

@jougs jougs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks for the quick reaction and updates. Fine by me!

@heplesser
Copy link
Contributor

@sarakonradi It is going to take me some time to review (and revise) the Eclipse workflow. I'd suggest to drop it from this PR and create a separate issue for adding it. I am about to recreate my Eclipse setup, so I will definitely update the instructions.

Concerning XCode, maybe @tammoippen could chip in?

@jougs
Copy link
Contributor

jougs commented Aug 10, 2020

Just for the record: I'd be totally fine with removing the two IDE related pages for now.

@sarakonradi sarakonradi removed the request for review from heplesser August 12, 2020 15:04
@sarakonradi
Copy link
Contributor Author

sarakonradi commented Aug 12, 2020

I'd suggest to drop it from this PR and create a separate issue for adding it. I am about to recreate my Eclipse setup, so I will definitely update the instructions.

@heplesser Sounds good! I have created a separate issue for the Eclipse workflow and undone the review request here.

@jougs
Copy link
Contributor

jougs commented Aug 12, 2020

@sarakonradi: many thanks!

As this is "only" concerning documentation and really just a move of existing pages, I think we can do with a single review here. I'm thus merging.

@jougs jougs merged commit 0619107 into nest:master Aug 12, 2020
@sarakonradi sarakonradi deleted the update_contribute_page branch September 21, 2020 08:55
@terhorstd terhorstd mentioned this pull request Nov 11, 2020
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants