☂️ [Roadmap]: Clean Up

[jsjoeio]

This is an umbrella issue to related to one of our priorities for code-server: clean up.

They're chores. Think of this as cleaning up the repository and making things easier both for maintainers and contributors.

1. Easier for Maintainers

code-server is a big project. The easier to maintain, the faster we can fix bugs, ship features and help the community.

• ✅ separate unit and e2e testing [dev]: separate unit and end-to-end testing #2646
• ⏳ improve updating vscode process
  • ⏳ improve existing script [dev]: improve update-vscode.sh script #2787
  • figure out a way to pull in their changes on a regular cadence (so updating is easier)
• ⏳ pre-install script that checks dependencies [dev]: pre-install script that checks dependencies #2807
• 🚧 automate release process [dev]: research automating the release process #2817
  • ✅ automate first step of process dev: add release:prep script #2952
  • TODO automate attaching artifacts to release
• ✅ add homebrew job to publish.yaml [dev]: add homebrew job to publish.yaml #2841
• ⏳ add aur job to publish.yaml [dev]: add aur job to publish.yaml #2845
• TODO investigate dropping nfpm see comment
• TODO clean up images see comment

  particularly in light of the fact that CentOS changed their model recently with CentOS Stream

• ⏳ split up github workflows [dev]: split up test & release into separate workflows #2903
• ⏳ try changing esModuleInterop to false

2. Easier for Contributors

If we want to encourage contributions from the community (and even Coder employees), we need to make it as simple as possible to contribute.

• ✅ Remove shfmt as a dependency [dev]: replace shfmt dependency #2772
• ⏳ "...maybe we could make an image to do code-server development inside code-server, and also a variant for code-server development inside coder." —@jawnsy refactor: remove debian10/Dockerfile and update CONTRIBUTING #3134 (review)

3. Remove Dead Code

We need to do an analysis to see how much unused code exists in the code-server codebase. This could slim down the size, maybe help performance but also help with maintenance long-term.

• ✅ remove pages/updates.css chore: Remove pages/update.css #2823
• TODO add more tasks here

4. Improve Security Practices

We want to make sure we're staying on top of security vulnerabilities in code-server by following best practices.

-⏳ utilize GitHub security tools #2839

LEGEND

⏳ = to do
🚧 = in progress
✅ = done

Note: this is part of an experiment to be more transparent about our priorities and our roadmap. See everything related to this effort in the project board

[greyscaled]

@jsjoeio can we mark remove pages/updates.css from 🚧 -> ✔️

[jsjoeio]

We are moving away from the umbrella issue approach and instead only using the Project Board. Things that are not yet issues are cards. Once they are to be worked on, they will be converted to issues.

See items under "To do" in Roadmap: https://github.com/cdr/code-server/projects/4