🤝 Contribution Guidelines for JWOC Season 6

[Parnab03]

Welcome to JWOC Season 6! We're thrilled to have you on board as a contributor. To get started, it's mandatory to join our official Discord community and complete the form available there to validate your contributions. If you wish to raise an issue, you must first discuss it on the Discord General channel. Only if deemed valid will you be allowed to submit it on GitHub; otherwise, it won't be accepted.

Before diving in, please read this guideline thoroughly. It's packed with answers to common questions and essential instructions that will save you time and effort. Skipping any part might lead to confusion or repetitive questions that have already been answered here.

Take a moment to explore this guide—it will set you up for an organized and impactful contribution journey. Let’s create something amazing together!

---

📜 Basic Instructions

1. One Issue at a Time

Each contributor can only be assigned to one issue at a time.

• After completing an issue and having your work merged, you will be free to assign yourself to a new issue.
• If you are working on an issue but wish to abandon it and work on a different one, you must first comment on the issue and wait for confirmation from the maintainer before reassignment.

2. Video Submission is Required

When you create a pull request (PR), a video submission is mandatory. The video should demonstrate the following:

• What your changes do: Show the feature in action or explain how the bug fix works.
• How you implemented it: Provide a brief explanation of the approach you took.

This helps the maintainers understand what was changed and review your contribution. Without this video, your PR will not be merged.

3. Wallpaper Submission for WallGodds

If your contribution involves adding a new wallpaper, attach a screenshot or photo of the wallpaper in your PR. This visual is crucial for the review process.

Without this image, your submission cannot be approved. Therefore, ensure that the wallpaper is presented clearly.

4. File Structure Adherence

Our project follows a strict file structure to ensure consistency and maintainability. Please ensure that your files adhere to this structure when adding new content.

For example:

• When adding a new feature, ensure the code is placed in the appropriate folder, such as Components/GalleryModule, Components/ErrorModule, etc.
• If adding a wallpaper, place it in the Wallpapers/<Desktop/Tablet/Mobile> directory on GitHub.

Failure to adhere to this structure may result in your PR being rejected. Consistency is key!

---

🔢 Issue Levels

Issues in the project are categorized into levels, which determine the number of contributors required and the steps for resolution.

Easy:

• This level is suitable for tasks that require minimal effort and can be completed quickly.
• Submit your work within 1 day of being assigned the issue.
• If your PR is successfully merged, you will earn 1 point.

Medium:

• Tasks in this category are moderately complex and may take additional time and effort.
• Submit your work within 3 days of being assigned the issue.
• If your PR is successfully merged, you will earn 3 points.

Hard:

• These issues are the most challenging, often requiring in-depth problem-solving and advanced development skills.
• Submit your work within 5 days of being assigned the issue.
• If your PR is successfully merged, you will earn 5 points.

Reassignment Policy:

• If you miss the assigned deadline for any issue level, your issue will be reassigned to other contributors, and you will no longer be eligible to work on that issue.
• No extensions will be granted unless discussed and approved in exceptional cases.

---

🌍 Always Open Issues

Some issues are always open and can be worked on at any time. These tasks are ongoing, and you are welcome to jump in whenever you wish.

🖼️ Design Wallpapers and Add Them to the Project #8

• You are free to submit creative and new wallpapers at any time.
• Simply submit your wallpaper along with a clear image and description.
• The wallpaper can be a photo you took or a piece of artwork you created.

🌱 Fix UI Bugs in the Website #4

• If you notice any UI-related bugs or inconsistencies, feel free to fix them.
• These issues are always open since UI improvements are always needed.

---

💡 Important Notes

1. Communication is Key

Effective communication is essential. If you have any questions or need clarification, please feel free to ask! You can communicate through comments in your PR or the project discussions. Always keep communication lines open.

Example:

• Comment in your PR: "I fixed the alignment of the buttons. Please review."
• If you're unsure: "I'm not sure if this wallpaper fits the theme. Could someone provide feedback?"

2. Respect Deadlines

We work in a timely manner, so please make sure to submit your PRs by the given deadlines. If you need more time, inform the maintainers. This helps everyone stay organized and on track.

3. Focus on Quality, Not Quantity

We prioritize quality over quantity. A small, well-written PR is far more valuable than a large, rushed one. Take your time to understand the issue, write clean code, and thoroughly test your changes.

Example:
If you are fixing a bug, test it under different conditions to ensure it’s completely resolved.

---

If you have any questions, feel free to ask in the Discord server, comment on the issue, or reach out to the project maintainers. We are here to assist you!

---