🚀 Contribution Guidelines for WOC 4.0 #25
Parnab03
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Please read the entire guideline thoroughly. It contains answers to many common questions, so it’s important not to skip any sections. If you don’t follow these instructions and later ask a question in the Discord channel, there’s a good chance that the answer is already covered here. By overlooking this guide, you might end up asking questions that have already been answered, making your inquiry less effective.
We are excited to have you as a contributor! Please take a moment to review these guidelines. They will help you get started and ensure that the contributions are well-organized and of high quality.
📜 Basic Instructions
1. One Issue at a Time
Each contributor can only be assigned to one issue at a time.
2. Video Submission is Required
When you create a pull request (PR), a video submission is mandatory. The video should demonstrate the following:
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:
Components/GalleryModule
,Components/ErrorModule
, etc.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.
Level 1 Issues:
Level 2 Issues:
Level 3 Issues:
🌍 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
🌱 Fix UI Bugs in the Website #4
💡 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:
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.
Beta Was this translation helpful? Give feedback.
All reactions