Code_snips(Cap of 5 pull requests on the entire repository during the boost period.)

Take a look at the ISSUE #1 before planning to submit your PR.

It is one PR limited to one individual.

This repository's aims to accept beginner friendly submissions and accepts medium sized scripts of code which can be used elsewhere

example:-

Text_to_speech

Speech_to_text

These particular python codes can be utilised in a larger python code-base that needs these for increasing interactivity on a website or making a personal assistant.

• These BP can be altered depending on the code's complexity, length and usefullness

Uses:-

1. A collection of helpful code snippets.I have made that can be used for larger programs.

2. Open for users to contribute to the codebase so as to help each other out.Algorithms, Object detection algorithms,machine learning algorithms for AI/ML.

3. Basic templates and short codes to allow for creation of web-page elements as well as larger code scripts.

   • For example:-

4. The text_to_speech and speech_to_text codes can be used in a website so as to allow hearing impaired individuals to communicate their thoughts.

5. This can be inserted into a larger codebase for a larger set of individuals with different disabilities.

6. This could also used in websites so as to add extra functionality and cool features.

Parameters for bounty point allocation (Mandatory rules to be followed) :-

1. If you are submitting an AI/Model then you must specify the efficiency of the models.

2. Length of the code must not be lesser than 20 lines or greater than 200 lines unless explained to the maintainer why the code is in the spirit of this repository.

3. Must include Sufficient comments on your code for others to understand your script.

4. Also at the end of the file in comments please do indicate the uses of your script.

Examples of low quailty contributions:-

Note that your PR's will be scrutanised heavily if they follow the parameters and is limited to one PR per participant.

• Pull requests that are automated e.g. scripted opening pull requests to remove whitespace / fix typos / optimize images.

• Pull requests that are disruptive e.g. taking someone else's branch/commits and making a pull request.

• Pull requests that are regarded by a project maintainer as a hindrance vs. helping.

• Something that's clearly an attempt to simply +1 your pull request count for October.

• Last but not least, one pull request to fix a typo is fine, but 5 pull requests to remove a stray whitespace is not.

Proof of when the repo was made