Update GitHub group references (#455)

ByteWelder -> TactilityProject
This commit is contained in:
Ken Van Hoeylandt 2026-01-24 16:34:04 +01:00 committed by GitHub
parent 4b6ed871a9
commit d3797abf4e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
6 changed files with 10 additions and 10 deletions

2
.github/FUNDING.yml vendored
View File

@ -1,6 +1,6 @@
# These are supported funding model platforms # These are supported funding model platforms
github: [ByteWelder] github: [TactilityProject]
patreon: # Replace with a single Patreon username patreon: # Replace with a single Patreon username
open_collective: # Replace with a single Open Collective username open_collective: # Replace with a single Open Collective username
ko_fi: # Replace with a single Ko-fi username ko_fi: # Replace with a single Ko-fi username

View File

@ -1,7 +1,7 @@
### Checklist ### Checklist
- [ ] I read [contribution guidelines](https://github.com/ByteWelder/Tactility/blob/main/CONTRIBUTING.md) - [ ] I read [contribution guidelines](https://github.com/TactilityProject/Tactility/blob/main/CONTRIBUTING.md)
- [ ] Code adheres to the [coding style](https://github.com/ByteWelder/Tactility/blob/main/CODING_STYLE.md) - [ ] Code adheres to the [coding style](https://github.com/TactilityProject/Tactility/blob/main/CODING_STYLE.md)
### Description ### Description

View File

@ -2,7 +2,7 @@
## New features and boards ## New features and boards
Feel free to open an [issue](https://github.com/ByteWelder/Tactility/issues/new) Feel free to open an [issue](https://github.com/TactilityProject/Tactility/issues/new)
to discuss ideas you have regarding the implementation of new boards or features. to discuss ideas you have regarding the implementation of new boards or features.
Keep in mind that the internal APIs are changing rapidly. They might change considerably in a short timespan. Keep in mind that the internal APIs are changing rapidly. They might change considerably in a short timespan.

View File

@ -6,8 +6,8 @@
2. Merge the branch and wait for a build. 2. Merge the branch and wait for a build.
3. Upload the new Tactility SDK to the CDN 3. Upload the new Tactility SDK to the CDN
1. Upload it to the [CDN](https://dash.cloudflare.com) 1. Upload it to the [CDN](https://dash.cloudflare.com)
2. Update `sdk.json` from [TactilityTool](https://github.com/ByteWelder/TactilityTool) and upload it to [CDN](https://dash.cloudflare.com) 2. Update `sdk.json` from [TactilityTool](https://github.com/TactilityProject/TactilityTool) and upload it to [CDN](https://dash.cloudflare.com)
4. Update the [TactilityApps](https://github.com/ByteWelder/TactilityApps) with the new SDK and also release these to the CDN: 4. Update the [TactilityApps](https://github.com/TactilityProject/TactilityApps) with the new SDK and also release these to the CDN:
1. Download the `cdn-files.zip` from the pipelines 1. Download the `cdn-files.zip` from the pipelines
2. Upload them to the CDN at `apps/x.y.z/` 2. Upload them to the CDN at `apps/x.y.z/`
3. Also upload them to the CDN for the upcoming version, because the upcoming a.b.c version will also need some basic apps to download 3. Also upload them to the CDN for the upcoming version, because the upcoming a.b.c version will also need some basic apps to download
@ -18,8 +18,8 @@
6. Test the firmwares on all devices with the local web installer 6. Test the firmwares on all devices with the local web installer
7. Push a tag e.g. `v1.2.3` - the `v` prefix is crucial for the pipelines 7. Push a tag e.g. `v1.2.3` - the `v` prefix is crucial for the pipelines
8. The pipelines should now kick off a build that releases the build to the stable channel of the Web Installer. Verify that. 8. The pipelines should now kick off a build that releases the build to the stable channel of the Web Installer. Verify that.
9. Make a new version of the docs available at [TactilityDocs](https://github.com/ByteWelder/TactilityDocs) 9. Make a new version of the docs available at [TactilityDocs](https://github.com/TactilityProject/TactilityDocs)
10. Make a new [GitHub release](https://github.com/ByteWelder/Tactility/releases/new) 10. Make a new [GitHub release](https://github.com/TactilityProject/Tactility/releases/new)
11. Double-check that all CDN/TactilityApps/Tactility repository changes are merged. 11. Double-check that all CDN/TactilityApps/Tactility repository changes are merged.
12. Ensure that the CDN is not in development mode anymore. 12. Ensure that the CDN is not in development mode anymore.

View File

@ -52,7 +52,7 @@ The Tactility logo copyrights are owned by Ken Van Hoeylandt.
Logo usage is permitted in these scenarios: Logo usage is permitted in these scenarios:
- News, blog posts, articles and documentation that write about the official Tactility project. - News, blog posts, articles and documentation that write about the official Tactility project.
- Firmwares built with unmodified source code from [the official repository](https://github.com/ByteWelder/Tactility) can be redistributed with the Tactility logo. - Firmwares built with unmodified source code from [the official repository](https://github.com/TactilityProject/Tactility) can be redistributed with the Tactility logo.
- Personal use for local builds that contain Tactility source code (original or modified), and aren't re-distributed online. - Personal use for local builds that contain Tactility source code (original or modified), and aren't re-distributed online.
Logo usage is forbidden in all other scenarios unless an exception was granted by the author. Logo usage is forbidden in all other scenarios unless an exception was granted by the author.

View File

@ -59,7 +59,7 @@ License: [MIT](https://github.com/Xinyuan-LilyGO/T-Echo/blob/main/LICENSE)
Website: https://github.com/UsefulElectronics/esp32s3-gc9a01-lvgl Website: https://github.com/UsefulElectronics/esp32s3-gc9a01-lvgl
License: [Explicitly granted by author](https://github.com/ByteWelder/Tactility/pull/295#discussion_r2226215423) License: [Explicitly granted by author](https://github.com/TactilityProject/Tactility/pull/295#discussion_r2226215423)
### Other Dependencies ### Other Dependencies