chore: remove dead root files (.travis.yml, .lgtm.yml, *.bat)

[JohnMcLear]

Summary

Sweep four stale files out of the repo root. None of them are read by any CI/tooling we still use.

File	Why remove
`.travis.yml`	Etherpad moved to GitHub Actions years ago; `.github/workflows/` is the source of truth
`.lgtm.yml`	LGTM was sunset by GitHub in late 2022
`start.bat`	README only documents the PowerShell installer for Windows now (`irm .../installer.ps1 | iex`); no docs or scripts reference it
`bin/installOnWindows.bat`	Same — not referenced by README, docs, or workflows

Also dropped the stale `.travis.yml` line from the plugin layout doc in `doc/plugins.md` (replaced with a pointer at `.github/workflows/`).

Generated with Claude Code

[qodo-free-for-open-source-projects]

Review Summary by Qodo

Remove stale root files and update plugin documentation

📦 Other

Walkthroughs

Description

• Remove four stale files no longer used by CI/tooling
• Delete .travis.yml (replaced by GitHub Actions workflows)
• Delete .lgtm.yml (LGTM sunset by GitHub in 2022)
• Delete start.bat and bin/installOnWindows.bat (undocumented Windows scripts)
• Update plugin documentation to reference .github/workflows/ instead

Diagram

flowchart LR
  A["Stale Files<br/>(.travis.yml, .lgtm.yml,<br/>*.bat)"] -- "Delete" --> B["Removed from repo"]
  C["doc/plugins.md"] -- "Update reference" --> D[".github/workflows/"]

Loading

File Changes

1. bin/installOnWindows.bat Cleanup +0/-49

Remove undocumented Windows installer script

• Entire file deleted (49 lines)
• Windows batch script for installing Etherpad dependencies
• Not referenced in README, docs, or workflows

bin/installOnWindows.bat

---

2. start.bat Cleanup +0/-12

Remove legacy Windows startup script

• Entire file deleted (12 lines)
• Windows batch script for starting Etherpad
• Replaced by PowerShell installer documented in README

start.bat

---

3. .lgtm.yml Cleanup +0/-9

Remove deprecated LGTM configuration

• Entire file deleted (9 lines)
• LGTM code scanning configuration
• LGTM service was sunset by GitHub in late 2022

.lgtm.yml

---

View more (2)

4. .travis.yml Cleanup +0/-145

Remove obsolete Travis CI configuration

• Entire file deleted (145 lines)
• Travis CI configuration with multiple test jobs
• Etherpad migrated to GitHub Actions years ago

.travis.yml

---

5. doc/plugins.md 📝 Documentation +1/-1

Update plugin docs CI workflow reference

• Updated plugin layout documentation line 41
• Changed .travis.yml reference to .github/workflows/
• Added clarification about CI workflow types (backend/frontend tests, npm publish)

doc/plugins.md

---

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Misleading workflows tree entry 🐞 Bug ≡ Correctness

Description

doc/plugins.md now lists .github/workflows/ as a top-level sibling entry even though the example
tree already includes .github/ with nested workflows/, making the folder structure example
internally inconsistent.

Code

doc/plugins.md[41]

+ ├ .github/workflows/   ◄─ CI workflows (backend / frontend tests, npm publish)

Evidence

The folder structure example already shows .github/ and its workflows/ child; adding
.github/workflows/ again at the top level implies it is a sibling of .github/ (which cannot be
correct) and duplicates the same directory in the tree.

doc/plugins.md[22-47]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The plugin folder structure example in `doc/plugins.md` is internally inconsistent: it shows `.github/` with nested `workflows/`, and also shows `.github/workflows/` again as a separate top-level entry.

### Issue Context
This was introduced when replacing the old `.travis.yml` line.

### Fix Focus Areas
- doc/plugins.md[22-47]

### Expected fix
Remove the redundant `.github/workflows/` top-level line and, if you want to describe CI workflows, attach that description to the existing `.github/` and/or `workflows/` entries (keeping the tree accurate and non-duplicative).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more