Skip to content

Commit e5580e9

Browse files
Update docs/blog/20240624-Daeraxa-3kStars.md
Co-authored-by: Andrew Dupont <andrew@andrewdupont.net>
1 parent 7eb592b commit e5580e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/blog/20240624-Daeraxa-3kStars.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ Finally, on the 8th of June, 2022, GitHub made an announcement that Atom would b
6868

6969
<img src="./assets/atom-community.png" height="200" />
7070

71-
As soon as the news hit, there was a flurry of activity. Some were looking for direct replacements for Atom; others were looking for active forks or continuations of the project. [Atom Community](https://atom-community.github.io/) was the logical place for these discussions. This was a community that had taken on the maintenance of a bunch of Atom packages (originally for the Abandoned Facebook [Nuclide](https://nuclide.io/) project to turn Atom into an IDE) and had since taken on other packages from the original Atom maintainers.
71+
As soon as the news hit, there was a flurry of activity. Some were looking for direct replacements for Atom; others were looking for active forks or continuations of the project. [Atom Community](https://atom-community.github.io/) was the logical place for these discussions. This was a community that had taken on the maintenance of a bunch of Atom packages (originally for the abandoned Facebook [Nuclide](https://nuclide.io/) project to turn Atom into an IDE) and had since assumed stewardship of other packages from the original Atom maintainers.
7272

7373
At this time, the Atom Community Discord server was rather active with discussions about what could be done. Could the community keep Atom alive? Could they take ownership of any of the original repos? Would a community project be allowed to use the original name? However, it became clear there was somewhat of a split in the goals of the group; some wanted to take Atom and radically change it, upgrade it and take it into the future, get it into a state it might have been in had development not slowed to a crawl. Others wanted to be a little more conservative, keep the Atom they knew and loved, and make sure it was kept up-to-date with patches and fixes.
7474

0 commit comments

Comments
 (0)