Skip to content

Latest commit

 

History

History
92 lines (66 loc) · 4.08 KB

Learn.md

File metadata and controls

92 lines (66 loc) · 4.08 KB
Raw

Learn

Table of Contents

Introduction

Welcome to the Agrilearn Network open-source project! Whether you're a seasoned developer or new to open-source contribution, this guide will provide you with the essential information to get started and contribute effectively to the project.

Contributing Guidelines

Before diving into the learning resources, please familiarize yourself with the following contributing guidelines:

  • Participants/contributors must comment on issues they wish to work on.
  • Issues will be assigned on a first-come, first-serve basis by mentors or the Project Administrator (PA).
  • Participants can open new issues using the provided template, but these need verification and labeling by a mentor or PA.
  • Ensure issues are assigned to you before starting work.
  • Each participant can work on a maximum of one issue at a time.
  • Don't work on issues already assigned to others.
  • Discuss issues with the team before starting work.
  • Explain your approach to solving any issue in the comments for better understanding.
  • Pull requests will be merged after review by a mentor or PA.
  • Create PRs from branches other than main.
  • Include a descriptive summary of your work in the PR description.
  • Use the format Fixes: issue number in your commit message when creating a pull request.
  • Complete assigned issues within the specified deadline. Failure to do so may result in reassignment.
  • Follow project guidelines and coding style.
  • Aim for structured and optimized code.
  • Mistakes are allowed and part of the learning process!

Getting Started

To contribute to the Agrilearn Network project, follow these steps:

  1. Fork the Repository: Start by forking the repository to your GitHub account.
  2. Clone the Repository: Clone your forked repository to your local machine.
  3. Choose an Issue: Comment on an issue you'd like to work on or open a new one following the guidelines.
  4. Set Up Development Environment: Refer to the project's development guidelines for setting up your development environment.
  5. Start Working: Once the issue is assigned to you, start working on it following your chosen approach.
  6. Submit a Pull Request: After completing your work, submit a pull request from your branch for review.

Issue Management

Issues are managed as follows:

  • Participants must comment on issues they wish to work on.
  • Issues will be assigned on a first-come, first-serve basis.
  • Participants can open new issues using the provided template, but these need verification and labeling by a mentor or PA.
  • Ensure issues are assigned to you before starting work.
  • Each participant can work on a maximum of one issue at a time.
  • Don't work on issues already assigned to others.
  • Discuss issues with the team before starting work.

Communication and Collaboration

Effective communication and collaboration are crucial for successful contributions:

  • Discuss issues with the team before starting work.
  • Explain your approach to solving any issue in the comments for better understanding.

Pull Requests (PRs)

Pull requests are managed as follows:

  • PRs will be merged after review by a mentor or PA.
  • Create PRs from branches other than main.
  • Include a descriptive summary of your work in the PR description.
  • Use the format Fixes: issue number in your commit message when creating a pull request.

Deadline and Completion

Ensure timely completion of assigned tasks:

  • Complete assigned issues within the specified deadline.
  • Failure to meet the deadline may result in reassignment.

Quality and Learning

Focus on quality and continuous learning:

  • Follow project guidelines and coding style.
  • Aim for structured and optimized code.
  • Mistakes are allowed and part of the learning process!