docs: move around / delete doc files

Move around `DEVELOPMENT.md` file into the repository root folder.
Delete `doc/CODE_OF_CONDUCT.md` and `doc/CONTRIBUTING.md`, both
duplicates (already present in the repository root folder). Reuse
`doc/CONTRIBUTING.md` content, more up to date. Update file
references wherever required, and use relative ones.

Author: matthieu-d4r

.github/pull_request_template.md

@@ -1,5 +1,5 @@
 ## Description
-<!-- Thank you for submitting a pull request! Find more information in our development guide at [DEVELOPMENT](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/doc/DEVELOPMENT.md) -->
+<!-- Thank you for submitting a pull request! Find more information in our development guide at [DEVELOPMENT](DEVELOPMENT.md) -->
 <!-- Provide an overview of the PR for maintainers and reviewers. -->
 <!-- Please ensure your commit messages follow these [guidelines](https://chris.beams.io/posts/git-commit/). -->
 

CONTRIBUTING.md

@@ -32,14 +32,13 @@ To send us a pull request, please:
 1. Fork the repository.
 2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
 3. Ensure local tests pass.
-4. Commit to your fork using clear commit messages.
+4. Commit to your fork using clear commit messages. When writing a Git commit message, follow these [guidelines](https://chris.beams.io/posts/git-commit/).
 5. Send us a pull request, answering any default questions in the pull request interface.
 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
 [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
-
 ## Finding contributions to work on
 Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
 

doc/DEVELOPMENT.md DEVELOPMENT.mddoc/DEVELOPMENT.md renamed to DEVELOPMENT.md

@@ -28,8 +28,8 @@ Amazon S3, without first saving to local storage.
 pip install s3torchconnector
 ```
 
-Amazon S3 Connector for PyTorch supports only Linux via Pip for now. For other platforms, see 
-[DEVELOPMENT](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/doc/DEVELOPMENT.md) for build instructions.
+Amazon S3 Connector for PyTorch supports only Linux via Pip for now. For other platforms,
+see [DEVELOPMENT](DEVELOPMENT.md) for build instructions.
 
 ### Configuration
 
@@ -45,8 +45,7 @@ on Unix or macOS.
 ### Examples
 
 [API docs](http://awslabs.github.io/s3-connector-for-pytorch) are showing API of the public components. 
-End to end example of how to use `s3torchconnector` can be found under the 
-[examples](https://github.com/awslabs/s3-connector-for-pytorch/tree/main/examples) directory.
+End to end example of how to use `s3torchconnector` can be found under the [examples](examples) directory.
 
 #### Sample Examples
 
@@ -132,8 +131,8 @@ pip install s3torchconnector[lightning]
 
 ### Examples
 
-End to end examples for the Pytorch Lightning integration can be found in the 
-[examples/lightning](https://github.com/awslabs/s3-connector-for-pytorch/tree/main/examples/lightning) directory
+End to end examples for the Pytorch Lightning integration can be found in the [examples/lightning](examples/lightning)
+directory.
 
 ```py
 from lightning import Trainer
@@ -159,13 +158,12 @@ To enable versioning on an S3 bucket, see [Enabling versioning on buckets](https
 S3 Versioning and S3 Lifecycle are not supported by S3 Express One Zone.
 
 ## Contributing
-We welcome contributions to Amazon S3 Connector for PyTorch. Please 
-see [CONTRIBUTING](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/doc/CONTRIBUTING.md) 
-For more information on how to report bugs or submit pull requests.
+
+We welcome contributions to Amazon S3 Connector for PyTorch. Please see [CONTRIBUTING](CONTRIBUTING.md) for more
+information on how to report bugs or submit pull requests.
 
 ### Development
-See [DEVELOPMENT](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/doc/DEVELOPMENT.md) for information 
-about code style, development process, and guidelines.
+See [DEVELOPMENT](DEVELOPMENT.md) for information about code style, development process, and guidelines.
 
 ### Compatibility with other storage services
 S3 Connector for PyTorch delivers high throughput for PyTorch training jobs that access or store data in Amazon S3. 
@@ -180,11 +178,8 @@ If you discover a potential security issue in this project we ask that you notif
 ### Code of conduct
 
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
-See [CODE_OF_CONDUCT.md](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/doc/CODE_OF_CONDUCT.md) for 
-more details.
+See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) for more details.
 
 ## License
 
-Amazon S3 Connector for PyTorch has a BSD 3-Clause License, as found in the 
-[LICENSE](https://github.com/awslabs/s3-connector-for-pytorch/blob/main/LICENSE) file.
-
+Amazon S3 Connector for PyTorch has a BSD 3-Clause License, as found in the [LICENSE](LICENSE) file.