<!-- Add banner here -->
# Project Title
<!-- Add buttons here -->
<!-- Describe your project in brief -->
The project title should be self-explanatory and try not to make it a mouthful. (Although exceptions exist- **awesome-readme-writing-guide-for-open-source-projects** - would have been a cool name)
Add a cover/banner image for your README. **Why?** Because it easily **grabs people's attention** and it **looks cool**(*duh!obviously!*).
Wait, I forgot something. You can use this README as a template from [this link](README-template.md).
The best dimensions for the banner is **1280x650px**. You could also use this for social preview of your repo.
I personally use [**Canva**](https://www.canva.com/) for creating the banner images. All the basic stuff is **free**(*you won't need the pro version in most cases*).
*What are all those flashy thingies below the title?*
Looks nice doesn't it? Those are called badges and they do improve the readability by giving some quick insights right?
There are endless badges that you could use in your projects. And they do depend on the project. Some of the ones that I commonly use in every projects are given below.
I use [**Shields IO**](https://shields.io/) for making badges. It is a simple and easy to use tool that you can use for almost all your badge cravings.
<!-- Add badges with link to Shields IO -->
: This badge shows the version of the current release.
: I think it is self-explanatory. This gives people an idea about how the project is being maintained.
: This is a dynamic badge from [**Shields IO**](https://shields.io/) that tracks issues in your project and gets updated automatically. It gives the user an idea about the issues and they can just click the badge to view the issues.
: This is also a dynamic badge that tracks pull requests. This notifies the maintainers of the project when a new pull request comes.
: If you are not like me and your project gets a lot of downloads(*I envy you*) then you should have a badge that shows the number of downloads! This lets others know how **Awesome** your project is and is worth contributing to.
: This shows what kind of open-source license your project uses. This is good idea as it lets people know how they can use your project for themselves.
: This is not essential but it is a cool way to let others know about your project! Clicking this button automatically opens twitter and writes a tweet about your project and link to it. All the user has to do is to click tweet. Isn't that neat?
# Demo-Preview
<!-- Add a demo for your project -->
After you have written about your project, it is a good idea to have a demo/preview(**video/gif/screenshots** are good options) of your project so that people can know what to expect in your project. You could also add the demo in the previous section with the product description.
Here is a random GIF as a placeholder.
# Table of contents
After you have introduced your project, it is a good idea to add a **Table of contents** or **TOC** as **cool** people say it. This would make it easier for people to navigate through your README and find exactly what they are looking for.
Here is a sample TOC(*wow! such cool!*) that is actually the TOC for this README.
- [Project Title](#project-title)
- [Demo-Preview](#demo-preview)
- [Table of contents](#table-of-contents)
- [Installation](#installation)
- [Usage](#usage)
- [Development](#development)
- [Contribute](#contribute)
- [Sponsor](#sponsor)
- [Adding new features or fixing bugs](#adding-new-features-or-fixing-bugs)
- [License](#license)
- [Footer](#footer)
# Installation
[(Back to top)](#table-of-contents)
*You might have noticed the **Back to top** button(if not, please notice, it's right there!). This is a good idea because it makes your README **easy to navigate.***
The first one should be how to install(how to generally use your project or set-up for editing in their machine).
This should give the users a concrete idea with instructions on how they can use your project repo with all the steps.
Following this steps, **they should be able to run this in their device.**
A method I use is after completing the README, I go through the instructions from scratch and check if it is working.
Here is a sample instruction:
To use this project, first clone the repo on your device using the command below:
```git init```
```git clone https://github.com/navendu-pottekkat/nsfw-filter.git```
# Usage
[(Back to top)](#table-of-contents)
This is optional and it is used to give the user info on how to use the project after installation. This could be added in the Installation section also.
# Development
[(Back to top)](#table-of-contents)
This is the place where you give instructions to developers on how to modify the code.
You could give **instructions in depth** of **how the code works** and how everything is put together.
You could also give specific instructions to how they can setup their development environment.
Ideally, you should keep the README simple. If you need to add more complex explanations, use a wiki. Check out [this wiki](https://github.com/navendu-pottekkat/nsfw-filter/wiki) for inspiration.
# Contribute
[(Back to top)](#table-of-contents)
This is where you can let people know how they can **contribute** to your project. Some of the ways are given below.
Also this shows how you can add subsections within a section.
### Sponsor
[(Back to top)](#table-of-contents)
Your project is gaining traction and it is being used by thousands of people(***with this README there will be even more***). Now it would be a good time to look for people or organisations to sponsor your project. This could be because you are not generating any revenue from your project and you require money for keeping the project alive.
You could add how people can sponsor your project in this section. Add your patreon or GitHub sponsor link here for easy access.
A good idea is to also display the sponsors with their organisation logos or badges to show them your love!(*Someday I will get a sponsor and I can show my love*)
### Adding new features or fixing bugs
[(Back to top)](#table-of-contents)
This is to give people an idea how they can raise issues or feature requests in your projects.
You could also give guidelines for submitting and issue or a pull request to your project.
Personally and by standard, you should use a [issue template](https://github.com/navendu-pottekkat/nsfw-filter/blob/master/ISSUE_TEMPLATE.md) and a [pull request template](https://github.com/navendu-pottekkat/nsfw-filter/blob/master/PULL_REQ_TEMPLATE.md)(click for examples) so that when a user opens a new issue they could easily format it as per your project guidelines.
You could also add contact details for people to get in touch with you regarding your project.
# License
[(Back to top)](#table-of-contents)
Adding the license to README is a good practice so that people can easily refer to it.
Make sure you have added a LICENSE file in your project folder. **Shortcut:** Click add new file in your root of your repo in GitHub --> Set file name to LICENSE --> GitHub shows LICENSE templates ---> Choose the one that best suits your project!
I personally add the name of the license and provide a link to it like below.
[GNU General Public License version 3](https://opensource.org/licenses/GPL-3.0)
# Footer
[(Back to top)](#table-of-contents)
Let's also add a footer because I love footers and also you **can** use this to convey important info.
Let's make it an image because by now you have realised that multimedia in images == cool(*please notice the subtle programming joke).
So that is it... You have completed your training young grasshopper. Now it is time for you to use this ideas for your projects.
Don't forget your **README Sensei**(*cool twitter handle idea*) when your project takes off with your **Awesome README**.
Leave a star in GitHub, give a clap in Medium and share this guide if you found this helpful.
**Now folks, the moment you've all been waiting for! The footer!**
***[Audible gasp]***
<!-- Add the footer here -->
Raw data
{
"_id": null,
"home_page": "https://featureselectionga.readthedocs.io",
"name": "genetic-algorithm-nas",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": "",
"keywords": "feature selection,Genetic Algorithm,DEAP",
"author": "shilash",
"author_email": "kaushalshetty@outlook.com",
"download_url": "https://files.pythonhosted.org/packages/4b/e3/f22c57b17e8f893af17c0cb31ab8f32890fdb61f2e2533653d1621460757/genetic-algorithm-nas-0.1.11.tar.gz",
"platform": null,
"description": "<!-- Add banner here -->\n\n\n# Project Title\n\n<!-- Add buttons here -->\n\n\n\n\n\n\n\n<!-- Describe your project in brief -->\n\nThe project title should be self-explanatory and try not to make it a mouthful. (Although exceptions exist- **awesome-readme-writing-guide-for-open-source-projects** - would have been a cool name)\n\nAdd a cover/banner image for your README. **Why?** Because it easily **grabs people's attention** and it **looks cool**(*duh!obviously!*).\n\nWait, I forgot something. You can use this README as a template from [this link](README-template.md).\n\nThe best dimensions for the banner is **1280x650px**. You could also use this for social preview of your repo.\n\nI personally use [**Canva**](https://www.canva.com/) for creating the banner images. All the basic stuff is **free**(*you won't need the pro version in most cases*).\n\n*What are all those flashy thingies below the title?*\n\nLooks nice doesn't it? Those are called badges and they do improve the readability by giving some quick insights right?\n\nThere are endless badges that you could use in your projects. And they do depend on the project. Some of the ones that I commonly use in every projects are given below. \n\nI use [**Shields IO**](https://shields.io/) for making badges. It is a simple and easy to use tool that you can use for almost all your badge cravings.\n\n<!-- Add badges with link to Shields IO -->\n\n\n: This badge shows the version of the current release.\n\n\n: I think it is self-explanatory. This gives people an idea about how the project is being maintained.\n\n\n: This is a dynamic badge from [**Shields IO**](https://shields.io/) that tracks issues in your project and gets updated automatically. It gives the user an idea about the issues and they can just click the badge to view the issues.\n\n\n: This is also a dynamic badge that tracks pull requests. This notifies the maintainers of the project when a new pull request comes.\n\n: If you are not like me and your project gets a lot of downloads(*I envy you*) then you should have a badge that shows the number of downloads! This lets others know how **Awesome** your project is and is worth contributing to.\n\n\n: This shows what kind of open-source license your project uses. This is good idea as it lets people know how they can use your project for themselves.\n\n: This is not essential but it is a cool way to let others know about your project! Clicking this button automatically opens twitter and writes a tweet about your project and link to it. All the user has to do is to click tweet. Isn't that neat?\n\n# Demo-Preview\n<!-- Add a demo for your project -->\n\nAfter you have written about your project, it is a good idea to have a demo/preview(**video/gif/screenshots** are good options) of your project so that people can know what to expect in your project. You could also add the demo in the previous section with the product description.\n\nHere is a random GIF as a placeholder.\n\n\n\n# Table of contents\n\nAfter you have introduced your project, it is a good idea to add a **Table of contents** or **TOC** as **cool** people say it. This would make it easier for people to navigate through your README and find exactly what they are looking for.\n\nHere is a sample TOC(*wow! such cool!*) that is actually the TOC for this README.\n\n- [Project Title](#project-title)\n- [Demo-Preview](#demo-preview)\n- [Table of contents](#table-of-contents)\n- [Installation](#installation)\n- [Usage](#usage)\n- [Development](#development)\n- [Contribute](#contribute)\n - [Sponsor](#sponsor)\n - [Adding new features or fixing bugs](#adding-new-features-or-fixing-bugs)\n- [License](#license)\n- [Footer](#footer)\n\n# Installation\n[(Back to top)](#table-of-contents)\n\n*You might have noticed the **Back to top** button(if not, please notice, it's right there!). This is a good idea because it makes your README **easy to navigate.*** \n\nThe first one should be how to install(how to generally use your project or set-up for editing in their machine).\n\nThis should give the users a concrete idea with instructions on how they can use your project repo with all the steps.\n\nFollowing this steps, **they should be able to run this in their device.**\n\nA method I use is after completing the README, I go through the instructions from scratch and check if it is working.\n\nHere is a sample instruction:\n\nTo use this project, first clone the repo on your device using the command below:\n\n```git init```\n\n```git clone https://github.com/navendu-pottekkat/nsfw-filter.git```\n\n# Usage\n[(Back to top)](#table-of-contents)\n\nThis is optional and it is used to give the user info on how to use the project after installation. This could be added in the Installation section also.\n\n# Development\n[(Back to top)](#table-of-contents)\n\nThis is the place where you give instructions to developers on how to modify the code.\n\nYou could give **instructions in depth** of **how the code works** and how everything is put together.\n\nYou could also give specific instructions to how they can setup their development environment.\n\nIdeally, you should keep the README simple. If you need to add more complex explanations, use a wiki. Check out [this wiki](https://github.com/navendu-pottekkat/nsfw-filter/wiki) for inspiration.\n\n# Contribute\n[(Back to top)](#table-of-contents)\n\nThis is where you can let people know how they can **contribute** to your project. Some of the ways are given below.\n\nAlso this shows how you can add subsections within a section.\n\n### Sponsor\n[(Back to top)](#table-of-contents)\n\nYour project is gaining traction and it is being used by thousands of people(***with this README there will be even more***). Now it would be a good time to look for people or organisations to sponsor your project. This could be because you are not generating any revenue from your project and you require money for keeping the project alive.\n\nYou could add how people can sponsor your project in this section. Add your patreon or GitHub sponsor link here for easy access.\n\nA good idea is to also display the sponsors with their organisation logos or badges to show them your love!(*Someday I will get a sponsor and I can show my love*)\n\n### Adding new features or fixing bugs\n[(Back to top)](#table-of-contents)\n\nThis is to give people an idea how they can raise issues or feature requests in your projects. \n\nYou could also give guidelines for submitting and issue or a pull request to your project.\n\nPersonally and by standard, you should use a [issue template](https://github.com/navendu-pottekkat/nsfw-filter/blob/master/ISSUE_TEMPLATE.md) and a [pull request template](https://github.com/navendu-pottekkat/nsfw-filter/blob/master/PULL_REQ_TEMPLATE.md)(click for examples) so that when a user opens a new issue they could easily format it as per your project guidelines.\n\nYou could also add contact details for people to get in touch with you regarding your project.\n\n# License\n[(Back to top)](#table-of-contents)\n\nAdding the license to README is a good practice so that people can easily refer to it.\n\nMake sure you have added a LICENSE file in your project folder. **Shortcut:** Click add new file in your root of your repo in GitHub --> Set file name to LICENSE --> GitHub shows LICENSE templates ---> Choose the one that best suits your project!\n\nI personally add the name of the license and provide a link to it like below.\n\n[GNU General Public License version 3](https://opensource.org/licenses/GPL-3.0)\n\n# Footer\n[(Back to top)](#table-of-contents)\n\nLet's also add a footer because I love footers and also you **can** use this to convey important info.\n\nLet's make it an image because by now you have realised that multimedia in images == cool(*please notice the subtle programming joke).\n\nSo that is it... You have completed your training young grasshopper. Now it is time for you to use this ideas for your projects.\n\nDon't forget your **README Sensei**(*cool twitter handle idea*) when your project takes off with your **Awesome README**.\n\nLeave a star in GitHub, give a clap in Medium and share this guide if you found this helpful.\n\n**Now folks, the moment you've all been waiting for! The footer!**\n***[Audible gasp]***\n\n<!-- Add the footer here -->\n\n\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Feature Selection using Genetic Algorithm (DEAP Framework)",
"version": "0.1.11",
"split_keywords": [
"feature selection",
"genetic algorithm",
"deap"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "4be3f22c57b17e8f893af17c0cb31ab8f32890fdb61f2e2533653d1621460757",
"md5": "942f07941ebc430e024b70224b8f1230",
"sha256": "59ba95aead25ba482c1e4f348dee989bef75f6fd5de686b151d49a78df532e8d"
},
"downloads": -1,
"filename": "genetic-algorithm-nas-0.1.11.tar.gz",
"has_sig": false,
"md5_digest": "942f07941ebc430e024b70224b8f1230",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 16340,
"upload_time": "2023-03-29T01:26:45",
"upload_time_iso_8601": "2023-03-29T01:26:45.594718Z",
"url": "https://files.pythonhosted.org/packages/4b/e3/f22c57b17e8f893af17c0cb31ab8f32890fdb61f2e2533653d1621460757/genetic-algorithm-nas-0.1.11.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-03-29 01:26:45",
"github": false,
"gitlab": false,
"bitbucket": false,
"lcname": "genetic-algorithm-nas"
}
JSON