Ali Cloud high-performance cloud server, 2 fold up! >>> >>>
Last April, we reported on Vitaly Slobodin, one of PhantomJS’s core developers, announcing his exit from maintainer, the project. At that time, many people expressed concern about the future direction of the project, and the lack of resources to support the project, which could face difficulties.
On March 2, 2018, pixiuPL, another core PhantomJS developer, posted an open letter saying that he had been forced to resign as Collaborator. PixiuPL says he was invited by Ariya to be the PhantomJS project’s Collaborator on Github in November, and has since started digging into the PJS source code, merging PR, dealing with Issues, releasing new releases, and more. Recently, due to problems he encountered during development that required access to the project Settings, he contacted Ariya several times over Skype and email, but did not get a reply (even though she was online).
On March 4, after the open letter was published, pixiuPL added that Ariya had replied to him via Skype but was unhappy with his suggestion to take over the project. Ariya seemed more willing to shut down the project and criticized pixiuPL for creating an internal branch of PJS (outside of GitHub).
After that, Ariya issued a “development pause” notice stating that due to the lack of positive contributions, the project would be mothbred and no new Issue submissions would be accepted. However, mailing lists can still be used to post questions and discuss project-related topics. PhantomJS 2.1.1 was the last stable release before archiving. If they pick up the project again in the future (e.g. # 15341, # 15342, # 15343), the project will be unarchived.
Ariya also responded under pixiuPL’s open letter that the two could no longer work together due to their different ways of handling things.
Pixiupl says it will fork a new project based on the current source code and maintain it under a new name.