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

Add License to files inside project #757

Merged
merged 2 commits into from
Apr 17, 2021
Merged

Add License to files inside project #757

merged 2 commits into from
Apr 17, 2021

Conversation

yamelsenih
Copy link
Member

This is recommended by GNU/gpl v3 according with it: https://www.gnu.org/licenses/gpl-3.0.html

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>.

This is recommended by GNU/gpl v3 according with it: https://www.gnu.org/licenses/gpl-3.0.html
```
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>.
```
@yamelsenih yamelsenih self-assigned this Apr 17, 2021
@yamelsenih yamelsenih added the 01 Enhancement New feature or request label Apr 17, 2021
@yamelsenih yamelsenih merged commit 82d1045 into adempiere:develop Apr 17, 2021
@yamelsenih yamelsenih deleted the feature/#LC-Add-License-Files branch April 17, 2021 20:19
yamelsenih added a commit to adempiere/adempiere-vue-docker that referenced this pull request Apr 23, 2021
- support search table mode mobile
[#740](adempiere/adempiere-vue#740)
- fix errors in the fields of the mobile interface with long names
(#746) [#746](adempiere/adempiere-vue#746)
- Add License to files inside project
[#757](adempiere/adempiere-vue#757)
- adaptable to different types of screens
[#758](adempiere/adempiere-vue#758)
- Allows timeout for backed request
[#759](adempiere/adempiere-vue#759)
- adaptable to different types of screens
[#758](adempiere/adempiere-vue#758)
- Allows timeout for backed request
[#759](adempiere/adempiere-vue#759)
- Change timeout by default
[#764](adempiere/adempiere-vue#764)
- get the currency code to be paid
[#750](adempiere/adempiere-vue#750)
- Fixes: [#767](adempiere/adempiere-vue#767)
[#767](adempiere/adempiere-vue#767)
- record access mode mobile support
[#755](adempiere/adempiere-vue#755)
- Add sub-menu to context menu
[#762](adempiere/adempiere-vue#762)
- Feature/refactory pos
[#760](adempiere/adempiere-vue#760)
- Converting for payment methods
[#749](adempiere/adempiere-vue#749)
- style context menu the field
[#755](adempiere/adempiere-vue#755)
- Error List Order
[#779](adempiere/adempiere-vue#779)
- add popover for ping in the point of sales
[#776](adempiere/adempiere-vue#776)
- shading in the table when selecting mobile mode
[#781](adempiere/adempiere-vue#781)
- add validation the isDisplayedGrid to table
[#783](adempiere/adempiere-vue#783)

## Available Docker Images:

- [ADempiere
gRPC](https://hub.docker.com/r/erpya/adempiere-grpc-all-in-one)
```shell
docker run -d \
    -it \
    --name adempiere-grpc-all-in-one \
    -p 50059:50059 \
    -e SERVER_PORT=50059 \
    -e SERVICES_ENABLED="access; business; core; dashboarding;
dictionary; enrollment; log; ui; workflow; store; pos; updater;" \
    -e SERVER_LOG_LEVEL="WARNING" \
    -e DB_HOST="localhost" \
    -e DB_PORT="5432" \
    -e DB_NAME=\"adempiere\" \
    -e DB_USER="adempiere" \
    -e DB_PASSWORD="adempiere" \
    -e DB_TYPE="PostgreSQL" \
    erpya/adempiere-grpc-all-in-one
```
- [Proxy ADempiere
API](https://hub.docker.com/r/erpya/proxy-adempiere-api)
```shell
docker run -it -d \
    --name proxy-adempiere-api \
    -p 8085:8085 \
    -e AD_DEFAULT_HOST="Your_gRPC_Server_IP" \
    -e AD_DEFAULT_PORT="50059" \
    -e AD_TOKEN="Your_ADempiere_Generated_Token" \
    -e VS_ENV="dev" \
    -e RESTORE_DB="N" \
    erpya/proxy-adempiere-api
```
- [ADempiere Vue](https://hub.docker.com/r/erpya/adempiere-vue)
```shell
docker run -it \
    --name adempiere-vue \
    -p 80:80 \
    -e API_URL="http://localhost:8085" \
    erpya/adempiere-vue
```
- [ADempiere](https://hub.docker.com/repository/docker/erpya/adempiere-base)
```
docker pull erpya/adempiere-base
docker run -p 8888:8888 erpya/adempiere-base
```

## Available Previews

- [ADempiere-Vue](https://demo-ui.erpya.com)
- [ADempiere-ZK](https://demo.erpya.com)

Authentication values:
### A Demo
```
User: demo
Password: demo
```
### Garden World
```
User: GardenAdmin
Password: GardenAdmin
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 Enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant