https://github.com/brenofariasdasilva/research-methodology

My Work Proposal for the Research Methodology Subject.
https://github.com/brenofariasdasilva/research-methodology

availability cap cap-theorem consistency latex overleaf paper partition-tolerance review

Last synced: 29 days ago
JSON representation

My Work Proposal for the Research Methodology Subject.

• Host: GitHub
• URL: https://github.com/brenofariasdasilva/research-methodology
• Owner: BrenoFariasdaSilva
• License: apache-2.0
• Created: 2023-07-20T17:47:08.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-03-29T17:40:51.000Z (9 months ago)
• Last Synced: 2024-04-20T14:46:22.035Z (8 months ago)
• Topics: availability, cap, cap-theorem, consistency, latex, overleaf, paper, partition-tolerance, review
• Language: PostScript
• Homepage:
• Size: 6.07 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        


  

# [Research-Methodology.](https://github.com/BrenoFariasdaSilva/Research-Methodology) 






  

---


My Work Proposal for the Research Methodology Subject that i did my university course at [UTFPR-CM](https://pt.wikipedia.org/wiki/Universidade_Tecnol%C3%B3gica_Federal_do_Paran%C3%A1).

  

---





![GitHub Code Size in Bytes](https://img.shields.io/github/languages/code-size/BrenoFariasdaSilva/Research-Methodology)

![GitHub Last Commit](https://img.shields.io/github/last-commit/BrenoFariasdaSilva/Research-Methodology)

![GitHub](https://img.shields.io/github/license/BrenoFariasdaSilva/Research-Methodology)

![wakatime](https://wakatime.com/badge/github/BrenoFariasdaSilva/Research-Methodology.svg)





  

![RepoBeats Statistics](https://repobeats.axiom.co/api/embed/1a121081a586a21625ff4e058ff4edf59269e1a9.svg "Repobeats analytics image")




## Contributing

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**. If you have suggestions for improving the code, your insights will be highly welcome.

In order to contribute to this project, please follow the guidelines below or read the [CONTRIBUTING.md](CONTRIBUTING.md) file for more details on how to contribute to this project, as it contains information about the commit standards and the entire pull request process.

Please follow these guidelines to make your contributions smooth and effective:

1. **Set Up Your Environment**: Ensure you've followed the setup instructions in the [Setup](#setup) section to prepare your development environment.

2. **Make Your Changes**:

   - **Create a Branch**: `git checkout -b feature/YourFeatureName`

   - **Implement Your Changes**: Make sure to test your changes thoroughly.

   - **Commit Your Changes**: Use clear commit messages, for example:

     - For new features: `git commit -m "FEAT: Add some AmazingFeature"`

     - For bug fixes: `git commit -m "FIX: Resolve Issue #123"`

     - For documentation: `git commit -m "DOCS: Update README with new instructions"`

     - For refactorings: `git commit -m "REFACTOR: Enhance component for better aspect"`

     - For snapshots: `git commit -m "SNAPSHOT: Temporary commit to save the current state for later reference"`

   - See more about crafting commit messages in the [CONTRIBUTING.md](CONTRIBUTING.md) file.

3. **Submit Your Contribution**:

   - **Push Your Changes**: `git push origin feature/YourFeatureName`

   - **Open a Pull Request (PR)**: Navigate to the repository on GitHub and open a PR with a detailed description of your changes.

4. **Stay Engaged**: Respond to any feedback from the project maintainers and make necessary adjustments to your PR.

5. **Celebrate**: Once your PR is merged, celebrate your contribution to the project!

## License

This project is licensed under the [Creative Commons Zero v1.0 Universal](LICENSE), which means you are free to use, modify, and distribute the code. See the [LICENSE](LICENSE) file for more details.