Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Q] Atom sunset #457

Open
UziTech opened this issue Jun 8, 2022 · 9 comments
Open

[Q] Atom sunset #457

UziTech opened this issue Jun 8, 2022 · 9 comments
Labels
question ❓ Further information is requested

Comments

@UziTech
Copy link
Member

UziTech commented Jun 8, 2022

It seems GitHub has finally pulled the plug and are sunsetting Atom.

I have been using a somewhat custom version of Atom for a while and plan on still using it for some development for a while.

Question is: Do people want x-terminal to continue to get updates? or should we archive it (and the rest of the terminals)?

@UziTech UziTech added the question ❓ Further information is requested label Jun 8, 2022
@the-j0k3r
Copy link
Member

the-j0k3r commented Jun 9, 2022

security updates are always welcome.

Not surprised they did this to Atom, classic MS move, embrace Opensource and then smother it to death.

I dont plan on ever using their offering (if forced by total lack of Atom security patches I will goto VSCodium) and its sad to see that @aminya hard work on fork has also gone to waste, when rebranding would be the only way for MS to not kill legal opensource forks like the community one, which in all fairness cannot contain any Atom branding nor names or imagery since they are trademarks.

I hope that @aminya will reconsider and rebrand, but highly doubtful and in the end, welcome to MS the opensource killers.

@mjrodgers
Copy link

I'd like to see continued development, I have some hope that the Pulsar-edit fork of Atom will continue to show promise. As of right now, it can pull the x-terminal package that was archived from apm (v 13.1.0) but any updates since then need to be installed manually.

@UziTech
Copy link
Member Author

UziTech commented Dec 20, 2022

I have been somewhat following the Pulsar-edit fork but not too closely. What would be needed to change this to be used in Pulsar-edit?

@wwWT000
Copy link

wwWT000 commented Dec 22, 2022

and , how to install it manually?

@mjrodgers
Copy link

Hmm, looking into this, they have a package manager that has all of the old Atom packages, but maybe they are still working on a way to update it... so maybe I jumped the gun on this suggestion.

I think to install manually you just download it from GitHub and put it in your packages folder.

@UziTech
Copy link
Member Author

UziTech commented Dec 23, 2022

In atom you could install any package from GitHub using the cli apm install [repo URL]. I'm guessing you can still do something similar withppm

@UziTech
Copy link
Member Author

UziTech commented Dec 23, 2022

Currently our GitHub actions scripts attempt to use apm to release new versions to the atom package manager (which is failing for obvious reasons). If you wanted to switch that to use ppm to release to the pulsar package manager that would be helpful. 😁👍

@liquidmetalrob
Copy link

I totally agree with keeping Atom and X-Terminal alive

@EchedelleLR
Copy link

I am unsure if after this you moved a bit, but I have received a very warm welcome with Pulsar and this package works there perfectly so far.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question ❓ Further information is requested
Development

No branches or pull requests

6 participants