froster02 commited on
Commit
c85f265
·
1 Parent(s): d487ea1

docs: add monitoring checklist and license note

Browse files
Files changed (2) hide show
  1. README.md +9 -3
  2. docs/monitoring-checklist.md +25 -0
README.md CHANGED
@@ -175,6 +175,12 @@ This monorepo is fully prepared for zero-cost, continuous deployment on **Huggin
175
  git push -f hf main
176
  ```
177
  3. **Automatic Deployment Build**:
178
- * Hugging Face will automatically detect the root `Dockerfile`.
179
- * It builds Stage 1 (React static assets compilation) and Stage 2 (installs Python 3.11, packages, upgrades to PyTorch 2.6.0, and downloads all models).
180
- * Once complete, the Space will transition to `RUNNING` and expose your secure application portal publicly!
 
 
 
 
 
 
 
175
  git push -f hf main
176
  ```
177
  3. **Automatic Deployment Build**:
178
+ * Hugging Face will automatically detect the root `Dockerfile`.
179
+ * It builds Stage 1 (React static assets compilation) and Stage 2 (installs Python 3.11, packages, upgrades to PyTorch 2.6.0, and downloads all models).
180
+ * Once complete, the Space will transition to `RUNNING` and expose your secure application portal publicly!
181
+
182
+ ---
183
+
184
+ ## 📄 License
185
+
186
+ This project is licensed under the GNU AGPLv3. See `LICENSE` for details.
docs/monitoring-checklist.md ADDED
@@ -0,0 +1,25 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Monitoring Checklist
2
+
3
+ Use this checklist to track forks, reuse, and license compliance for the
4
+ public repository.
5
+
6
+ ## Weekly Review
7
+ - Check the GitHub "Forks" list for new forks.
8
+ - Review the top 5 recent forks for license compliance signals (LICENSE
9
+ present, README attribution).
10
+ - Search GitHub for exact project name and unique phrases from README.
11
+
12
+ ## Monthly Review
13
+ - Search Hugging Face for your repo name and key phrases.
14
+ - Check for new public deployments that reference your repo name.
15
+ - Review open issues/PRs for third-party usage disclosures.
16
+
17
+ ## Response Steps
18
+ - Capture evidence (URL, screenshots, commit hash).
19
+ - Notify the maintainer of the fork with a polite compliance request.
20
+ - Escalate to platform takedown if non-compliant and unresponsive.
21
+
22
+ ## Suggested Alerts (Manual Setup)
23
+ - GitHub notifications: Watch the repo for "All Activity".
24
+ - GitHub search alerts: Save searches for your repo name and key phrases.
25
+ - Google Alerts: Create alerts for project name and unique phrases.