ghostofgoes/adles

Automated Deployment of Lab Environments System (ADLES)

adles's Issues

Add Pipenv

Add pipenv to handle:

• Installation (pipenv sync)
• Development environment setup
• Commands do common tasks: run tests, cut a release, etc.

What's involved:

• Update the README
• Add Pipfile and Pipfile.lock

Long-term vision: I would like to use Pipenv to install and manage the "full system" (user interface, server, etc.), while the PyPI package is simply the library providing the functionality leveraged by the various interfaces and tooling.

Documentation Localization/Translation

Make documentation usable by international folks.

• Tooling for distribution of documentation in multiple languages (does ReadTheDocs have mechanisms for this? Should we evaluate other sites/tools?)
• Guide on how to contribute (and maintain) a translation
• Add a basic set of automated translations

Usage videos

Add a few videos or animations to the README demonstrating usage of adles. These can be recorded using asciinema or other such tools.

Localization

Improve the accessibility of ADLES to those who don't speak English or non-native speakers.

Tasks

• Identify areas that need to be localized
• Determine if there are any localization standards or guidelines we should adhere to
• Localize text in a portable manner (gettext and friends, as long as the database can be distributed with the package)
• Abide by system localization settings where applicable (e.g. locale)

RPM package

Build a RPM package for Linux distributions that use yum (RHEL, CentOS, Fedora). Need to make something that can be distributed on EPEL and meets the guidelines for CentOS and Fedora.

Edit: I'm tired, It's RPM, not YUM

Appveyor

Setup and configure automated Windows testing using Appveyor. Copy what I've done for get-mac: https://github.com/GhostofGoes/get-mac/tree/master/appveyor

Accessibility

Improve accessibility of the system to people with disabilities.

• Identify areas that require accessibility changes (e.g. CLI, text output, visuals)
• What guidelines/standards exist that we should adhere to?
• Respect system configured accessibility settings for the identified areas, e.g. changing the color scheme for the CLI colors.
• Are there improvements that should/could be made to the documentation (e.g. compatibility with screen readers)?

Build Debian Package

Build a .deb package for Debian-based Linux distributions (Ubuntu, Kali, etc.)

Add tox testing and linting

Setup and configure tox

• Run all the current tests being performed by TravisCI (.travis.yml)
• Add configuration of pylint
• Add documentation of how to run tox to the README

Screenshots for documentation

Screenshots of output to put in README and other documentation