This is just my personal todo list
The order is just general precedence, not absolute.
That means I'll still work on issues later in the list, but less often than issues earlier in the list.
Also this todo list may not be accurate. It's just for me to keep track of everything.
Many of the issues are at the bottom because I have no idea where to start. Which is actually an accurate predictor of how much I work on an issue.
- Right now the biggest priority is to get Atom to successfully build on the
windows-2019CI Azure Pipelines image. The deadline is June 30: actions/runner-images#5403 - Some user-facing improvements are of course done by upgrading Electron
- Developer wise, it would be nice to update Node/Npm/Python/Babel
- Depend less on Native npm modules
I would add "Fixing tests" and "Improve performance" but the above seem to solve that already
Don't expect me to work very much on this todo list. And it's growing.
I also mantain https://docs.google.com/spreadsheets/d/161qC0zbFiwfSV7Yat3-ZHqCGl6RlQ1Hs0hroW6-aXCE/edit?usp=sharing
I'm too lazy to update it daily, so I'll just update after every commit.
- Update https://github.com/atom/atom/blob/master/docs/build-instructions/build-status.md
(Issue atom/atom#22669) - atom/atom#22462
- atom/atom#2654
- atom/github#2684
- atom/atom#14020
- Fix atom/github's flaky/failing tests
- atom/atom#22129 (big)
- Fix atom's vulnerabilities: https://github.com/icecream17/atom-update-backlog/blob/main/Vulnerabilities.md
See spreadsheet above - atom/atom#21049
- atom/atom#20222
- Figure out how to get the
atom --devstacktraces from the unhelpful<embedded>stacktraces in non dev mode.
(This would also be useful for other issues)
- Figure out how to get the
- atom/atom#22306
- atom/atom#6939
- atom/atom#5362
- atom/autocomplete-plus#1107
- atom/language-javascript#677 (I actually have an idea of what to do here, it's just that everything else is more helpful/urgent)