Instructions
Before we go, please note that on our platform "packet" refers to the library, module, source code, or even a complete project submitted by you.
Here are some things you have to check:
- We will not provide any task/project/packet from our side. You are free to think and choose your own packet. But the packet should be useful for users or for developers who can use it in their complete project. You can submit a complete project and also source code, modules, or libraries that can be useful for other developers.
- If you are interested in receiving project title suggestions from us, simply drop an email saying that you want to receive project titles from our end.
- The packet must not be taken from anywhere. You cannot submit packets made by others.
- The About section must have clear instructions on how to use the packet.
- Run and test the project on your machine first, then upload a screenshot of the running project/program to our portal. Make sure you have successfully inserted the image in the description part of the project when submitting a packet.
-
No extra unnecessary spaces in the About section, short description, or title. For example, the following contain unnecessary spaces:
Below is the given Python codein this wayUse this tool to detect extra spaces.
- Use this tool to detect mistakes in grammar, extra spaces, etc.
-
Packet title must include the minimum required information.
Do not use titles like "Password Generator Code" or "Video to GIF converter".
Instead, use titles like Password generator in Python or JavaScript Video to GIF converter using OpenCV library.
Always put the programming language in the title. If a library plays an important role, include it — e.g. "Object Detection in Python using TensorFlow" includes TensorFlow because it is critical. If the library is not important, you may omit it.
- Please mention the programming language in both the short description and the About section. If any major library or module plays an important role, also mention it.
- In the About section, clearly mention what the packet/project does and what its functionality is.
- Content must not be copied from other resources or websites.
-
Maintain quality — break up long paragraphs. The About section should not contain only a single lengthy paragraph. Long paragraphs have low readability.
✗ Not like this
One massive block of text with no paragraph breaks, making it very hard to read or understand how to use the packet in a real project...
✓ Should be like this
A short intro sentence.
Step-by-step instructions on how to use it.
A code snippet with expected output. - Don't use any unauthorized or unofficial external links.