Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement LICENSE files for third party software #86

Closed
apolopena opened this issue Mar 31, 2021 · 0 comments
Closed

Implement LICENSE files for third party software #86

apolopena opened this issue Mar 31, 2021 · 0 comments
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main

Comments

@apolopena
Copy link
Owner

Problem this feature will solve

Currently, third party softwares do not have LICENSE files

Background

Give credit where credit is due. Also comply with copyright laws.

Proposed Solution

All code in bash/third-party should be in its own directory, named by the repository it came from.
Currently the only third party software used in this project is tlatsas/bash-spinner#6
This script has been modified a little (spinner uses four shades of green) so put

# Modified by: Apolo Pena

In the comments in the header.
Also put this file in bash/third-party/bash-spinner/

Constraints and Assumptions

Refactor code to call bash/third-party/bash-spinner/spinner.sh

@apolopena apolopena added the enhancement New feature or request label Mar 31, 2021
@apolopena apolopena changed the title Implement LICENSE files for thrid party software Implement LICENSE files for third party software Mar 31, 2021
@apolopena apolopena added in-dev-qa passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main and removed in-dev-qa labels Mar 31, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main
Projects
None yet
Development

No branches or pull requests

1 participant