From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#9

Create an .exe or an executable installer for the project and each version. Also, create a setup.py and requirements.txt file for each project with program dependencies and information.

Use PyInstaller or cx_Freeze.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#8

Create an PLANNING.md file to make the project more welcoming.

Ideas:

• Github Docs

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#6

Create an PULL REQUEST TEMPLATE.md file to make the project more welcoming.

Ideas:

• Github Docs

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#15

Add buttons or commands that display each of the legal documents when they are executed.

The following need to be completed:

• Universal License
• Universal EULA
• Universal Terms and Conditions
• Univeral Priacy Policy

Create a space, or just an invitation, to allow other people to submit logos/designs that could be added to this project.

A good idea may be to use pull requests and issues, as they are built in and work well for this.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#18

Go in-depth on documentation and programming style through the wiki pages.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#13

Convert all boring .txt files to easy-to-read .md files.

Also ensure that all files have a file extension, and are formatted to that extension.

Add LambdaTest integrations.

Help:

• https://www.lambdatest.com/support/docs/

Update the icon sets to the latest version. Also ensure that icon licenses are included with the project.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#16

Add a license preface to the top of each code document. This can be from a personal license, or like something that the GNU GPL v3 has:

        How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program.  If not, see <https://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

  If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:

    <program>  Copyright (C) <year>  <name of author>
    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".

  You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.

  The GNU General Public License does not permit incorporating your program
into proprietary programs.  If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library.  If this is what you want to do, use the GNU Lesser General
Public License instead of this License.  But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

Create a Docker container that already has Python and this package installed.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#4

Create a CONTRIBUTING.md file to make the project more welcoming.

Ideas:

• Github Docs

Add Sentry integration.

Help:

• https://sentry.io/docs/

In discovering the new GitHub Next feature of file and code visualization, one should be created for this repo.

Links:

• https://mango-dune-07a8b7110.1.azurestaticapps.net/?repo=willtheorangeguy%2Fwilltheorangeguy.GitHub.io
• https://githubnext.com/projects/repo-visualization/

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#17

Create a dynamic, responsive website that makes the program more welcoming, and provides the information of the README.md and screenshots in a more dynamic and engaging way.

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#5

Create an ISSUE TEMPLATE.md file to make the project more welcoming.

Ideas:

• Github Docs

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#3

Create a proper README.md, using bookmarked templates.

Should have many areas of key program information.

Ideas:

• Electron-Markdownify
• Choo
• Redoc

Add DataDog integrations.

Help:

• https://docs.datadoghq.com/getting_started/application

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#7

Create an CODE OF CONDUCT.md file to make the project more welcoming.

Ideas:

• Github Docs

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#11

Create a /github folder in the project root directory to hold GitHub specific files such as guidelines and templates.

Make the following workflows work:

• Build & push to PyPI
• PyLint
• Test

After legal documents have been created, at and edit each one to/for this project.

The following need to be completed:

• Universal License
• Universal EULA
• Universal Terms and Conditions
• Univeral Priacy Policy

Add Doppler integrations.

Help:

• https://docs.doppler.com/docs/getting-started

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#12

Add screenshots to the project documentation (README, website, etc.), and to the /docs folder.

Create wheels and a PyPI package.

Also, create a setup.py and a requirements.txt.

Add HoneyBadger integrations.

Help:

• https://docs.honeybadger.io/lib/python/

DeepSource integration has already been created, now the problems it has created need to be fixed. Also add a DeepSource badge to the README.

• Fix DeepSource Issues
• Add Badge

From PyWorkout created by willtheorangeguy: Dog-Face-Development/PyWorkout#10

Create a /docs folder in the project root directory to hold screenshots and project documentation.

Add NewRelic integration.

Help:

• https://docs.newrelic.com/docs/infrastructure/host-integrations/installation/new-relic-guided-install-overview