Replies: 5 comments 18 replies
-
|
I have some JavaScript skills to put where needed if those could be identified. Additionally some server hosting resources. Although I can't find Atom's repo for their website API, which may not be opensource. But as I understand it the main functionality for the website:
But it seems to my understanding that the packages themselves are never hosted on the Atom.io website instead returning links to the Git repo, and Atom.io only stores a modified package.json file. Which you can see by visiting https://atom.io/api/packages. If this is the case I would be happy to get started on a functioning website, and could likely be done quite quickly if making it in Golang. Then try to keep it compliant with the existing API Calls. But am unclear in what way it integrates with Github and Auth in general for any requests that must be authenticated. If anyone could shed some light or confirm the existing maintainers are not working on this I could get started. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I think re-implementing the API server logic from scratch would be the only way, if only because I don't think the server code was ever open-sourced, and there aren't devs responding to any of the issues over at https://github.com/atom/atom, I think the community are effectively on their own. Edit to add: At least the documentation is clear as to how the API should respond. And the official server is still up, so if we have remaining questions about how the actual official implementation works, we can poke the official API a bit and find out. (We could open a separate, low-traffic issue or discussion post and try to ping past Atom team members and try to get code, [and/or thoughts on intellectual property of the data???] for the official API server.) |
Beta Was this translation helpful? Give feedback.
-
|
Miscellaneous thoughts I'm having: I do want to be up-front: I don't have much strong coding skills myself. I'm happy to provide my knowledge of having seen and troubleshooted lots of the code. But architecturing/authoring a lot of novel code isn't something I can do for this effort. If you want to go for it, I'll try to be helpful in whatever way I can. (Anyone else sitting back and reading, thinking "I could do that!", feel free to jump in and offer what you have in the way of skills as well!) So looking forward: there are some implications for re-implementing the API server. Work/to-do items for Atom core and apm: (switch the hard-coded API URL from There's also the sort of "intellectual property" question of who owns the old package metadata, and the sense of an implicit contract package authors had with a trusted entity of GitHub. Is it cool for us to plug that metadata into the new community server? Will package authors get bothered by support requests with our somewhat non-standard (not by much, but still) forked Atom? Do we need to start from scratch and re-populate the community package API database from zero? Does GitHub mind us using the old data/packages list? Do package authors mind? Kind of unclear. I think having pure intentions is a good start (we do), communicate openly and welcome anyone's questions or concerns, be responsive, and wait to see if anyone has a problem with it? Hmm. (Other than starting "clean-room" from scratch, there's no other way around it but being open and taking feedback on it.) |
Beta Was this translation helpful? Give feedback.
-
|
All great thoughts, and I definitely think a new Discussion might be best to focus on this. As for the code, I have already started laying some bare bones groundwork, available at my repo Atom-Community-Server-Backend. But reaching out for some information, especially how auth was handled, and the type of search algorithm that was implemented for As for the thought of who owns the package metadata that's a hard one. But there are some solid approaches you've outlined:
In the meantime luckily much of work can continue to lay the groundwork without knowing the answers here. But it is absolutely something that needs to be addressed. Additionally, like you mentioned, if anyone is reading our thread thinking to themselves they can do this or want to help, please feel free to start your version or contribute to my existing one, anything helps. |
Beta Was this translation helpful? Give feedback.
-
|
Might be useful to use this, this seems to partially document it. (who knew searching api off the atom org would help?) https://flight-manual.atom.io/atom-server-side-apis/ Whether or not that's of any use to anyone that can get it done before the deadline is another story. |
Beta Was this translation helpful? Give feedback.
-
|
Also might be useful to look at this new reply where they're supposedly discussing this in a atom community server as well on discord #361 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
I'd honestly like to see if this would continue here despite the sunset of the official atom repositories. I noticed the comment that basically linked me to this community repo and I'm certain it can't be hard with all the interest in the offical repos issues(that have blown up my email since the announcemnent) to find people that can maintain it on this side or at least I'd hope so. I wish I could offer myself up but I'm not sure I'd be the best person for that since I don't have nearly enough knowledge to program let alone lead something like this. It'd be nice to hear something from the people who are maintaining these forks and have been doing so from the looks of it and being a bit more active than MS's leftover team they had on atom.... |
Beta Was this translation helpful? Give feedback.
-
|
I would like to support efforts on this project here and there as I can, but cannot at this time devote significant technical skill. I do have some ideas for reworking the CI pipeline and moving it over to github actions (or perhaps Gitlab). I hesitate, however, to spearhead such an effort - as I am still teaching myself many things about CI pipelines. I will check in here and there as I can... but am by no means a professional nor should I be regarded as a primary contributor to the project moving forward. |
Beta Was this translation helpful? Give feedback.
-
|
Definitely should be using actions, however I'm still trying to teach myself those with pages so I can get some custom stuff on mine....which that could possibly be how the site is handled too but idk. Not like it'd need much other than a external source for the api database...which it looks like pretty much could just be a request to update a data file in any number of these static pages generators. |
Beta Was this translation helpful? Give feedback.
-
I don't think moving things to GitHub Actions helps the end-users. I redesigned the whole Azure CI system when we created this fork. I made everything reusable templates and unified the scripts to use Powershell on all platforms. Many of the changes were upstreamed. Moving to new technologies takes time, and such decisions do not make a noticeable difference for the end-user. https://github.com/atom-community/atom/tree/master/script/vsts https://github.com/atom-community/atom/tree/master/script/vsts/platforms/templates |
Beta Was this translation helpful? Give feedback.
-
|
To me, a major problem with GitHub Actions is that I have to be signed in to download the artifacts. |
Beta Was this translation helpful? Give feedback.
-
|
Folks, we're discussing on Discord (https://discord.gg/CdSBwZMU) some of the challenges and what we can do. I'm currently working on making the whole process of "compiling a working version" of Atom more easily available (no outdated node, no strange packages, no failures while running Also, thanks for keeping the discussions open here, so we have a public place to know that we may not be dead yet :D |
Beta Was this translation helpful? Give feedback.
-
|
I have a website project written in php and some of its functionality are provided by javascript code executed on the browser (I entirely developed it inside atom). So I have some javascript skills, even if a big project like atom is a very different thing from what I do with my website. Anyway I feel like I could contribute somehow, but there are some issues at the moment. There's no roadmap or a list of things to do. For example, imagine there are some functions to change for a new naming convention, which you don't need very specific skills, I can change them in 5 seconds with atom search and replace feature through project workspace, but I'm not aware of it. There should be a place here to list those things. Since you have to use Github.com because it's tied to the codebase and migrating to Gitlab it's too complex, just use all the features of this platform. I know you're on Discord, but honestly, it's not used by everyone and its app is one of the worst on Linux, I'd use it in the browser, but it's not really convenient in my opinion. Another issue is that I don't have any clue on how to test this project. Even if I don't want to contribute, just for curiosity, I have Arch Linux but I can't build it because it's broken. There's an AUR PKGBUILD not working. I'm currently using the old Arch upstream packages which were deleted after the sunset. I'm contributing to EasyEffects on Linux and my motivation is that it's quite easy just because it has a working PKGBUILD on AUR, even if I compile the testing build outside pacman. Anyway, in the end, having a roadmap here with list of things to do would be a good starting point. |
Beta Was this translation helpful? Give feedback.
-
Well that's one thing I've been trying to ask about fixing. I know right now @mauricioszabo has been working on some updates to make the editors core a bit more up to date. I'd like to see the projects section converted to the more modern interface(it's using the old version and is a bit out of date since it fell out of use for awhile). I'd like to see a proper roadmap too but I think at the moment we're stuck at getting it from electron v11(which Mauricio got it to 12) to as close to up to date as possible.
Well doesn't help that the only other decent alternative which is matrix imo is lacking a bit in it's organization features. With what changes probably need to be made in the discord for ease of use it's easier to use that and the discussion tab here afaik. But that's a question for the ones with read/write access(namely @aminya @DeeDeeG and ice cream(idk what their name is here)
This too is probably fixed in the pr that @mauricioszabo has open as well. I know he supposedly got builds working again-ish with that. A definite roadmap tho wouldn't be a bad idea but I know we're still debating whether a rename is in order(it might but not entirely sure). It'd help a lot to build some kind of team that has a couple people that are responsible for each major part(api, core, frontend, docs, etc). Which I've got a personal repo that will be pushed towards the website/docs side of things hopefully soon. I know the state things are in now we're in the 1.63-dev side of things from upstream but with the amount of work to be done bumping to 2.0 might be nice to give a clear end to atoms side and where we begin with going forward. |
Beta Was this translation helpful? Give feedback.
-
|
There are low-hanging fruits here on the Atom API that needs to be done: https://github.com/confused-Techie/atom-community-server-backend-JS/issues One of the really bad parts of Atom is that it's not easy to build from source. That's actually what I'm doing right now: trying to make build from source works better: https://github.com/AtomRebirth/atom/tree/build-without-scripts. I tried to build some packages with CircleCI, but I quickly got into its monthly limits so I'm trying Cirrus-CI now, to at least be able to produce binaries easily |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely feel free to work on some of the issues on the Atom-Community-Server-Backend-JS, I tried to make it as easy as possible to understand to anyone that wanted to help. Plus feel free to look through the README as I've done what I can to make it as easy as possible for others to contribute. Like a list of all functions/methods/routes that are not yet finished, and need work. Or if more advanced complexity reports to help know where may need more thorough testing. But even pointing out issues that still need to be worked on is helpful, to help get someone to look that direction. Anything at this point is appreciated |
Beta Was this translation helpful? Give feedback.
-
Atom official sunset is 15th December, 2022. If people would like to keep using atom, there will need to be an active fork. I believe this is the best place for people interested in continuing the project to congregate and begin discussing a gameplan for reigniting the community.
atom#25510 (comment)
Linking/Quoting comment by @DeeDeeG in Atom/Atom below. They present a good foundation for what this fork will need to survive.
I'd like to see an active healthy Atom fork. I believe that calls for a team that can handle it.
Skills needed for a team wanting to successfully fork Atom:
(Note: No one person needs to have all these skills! Any one of the above is helpful. I personally believe a team with all of those skills collectively is pretty much a requirement, though.)
Major development to-do items:
Unclear if needed, but the fork may need to re-implement or replace the functionality of the atom.io website:
atom.io, in case that site goes down.atom.iohosts Atom's package ecosystem, including the API thatapminteracts with to publish or download/install packagesgithubpackage. (The bundled/default package that handles git and GitHub integration in Atom.)Sorry for the long post. I hope that if there is passion for a fork, that this can point people in the right direction.
Beta Was this translation helpful? Give feedback.
All reactions