Upstream/dynmap
1
0
Fork 0
mirror of https://github.com/webbukkit/dynmap.git synced 2025-02-25 16:21:57 +01:00
Code Issues Projects Releases Wiki Activity

Fix typos, pt. 2

Browse Source
This commit is contained in:
Adam Tunnic 2021-02-07 01:33:22 -05:00 committed by GitHub
parent 0a6aea50d8
commit 5d50e6624a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -93,7 +93,7 @@ not yet (or no longer) supported by the Dynmap team. If the Dynmap team comes t
cease distribution of the unofficial version, unless otherwise authorized to continue doing so. Further:
- The team distributing the modified version must cite the origin of the Dynmap code, but must also clearly indicate that the version is NOT supported by
nor endorsed by the Dynmap team, and that ALL support should be directed through the team providing the modified version.
- Any modified version CANNOT be monitized or otherwise charged for, under any circumstances, nor can redistribution of it be limited or restricted.
- Any modified version CANNOT be monetized or otherwise charged for, under any circumstances, nor can redistribution of it be limited or restricted.
- The modified code must continue to be Apache Public License v2, with no additional conditions or restrictions, including full public availability of the
modified source code.
- Any code from Dynmap used in such versions should be built from an appropriate fork, as DynmapCore and other components (other than DynmapCoreAPI and
@ -101,8 +101,8 @@ cease distribution of the unofficial version, unless otherwise authorized to con
least, removed). The modified version should NOT refer to the Dynmap Discord nor to /r/Dynmap on Reddit for support. in any case.
- Any bugs or issues opened in conjunction with the use of the modified version on this repository will be closed without comment.
Additions of new funtion, including new platform support, in this official Dynmap code base MUST be fully contained within the PRs submitted to this
repository. Further, it is always exptected than any updates will be built and tested across all relevant platforms - meaning anh chances to shared code
Additions of new functions, including new platform support, in this official Dynmap code base MUST be fully contained within the PRs submitted to this
repository. Further, it is always expected than any updates will be built and tested across all relevant platforms - meaning any chances to shared code
components (DynmapCore, DynmapCoreAPI) MUST be successfully built and tested on ALL supported platforms (Forge, Spigot, etc). Changes which break
supported platforms will be rejected.