Will HeroDevs maintain this project after August 2023?

[alexsch01]

Will HeroDevs maintain this project after August 2023?

[thw0rted]

If y'all do wind up seeing this issue, can you also please update the README for this project and Protractor as well? The README files for both repos currently say nothing about EOL status, so people are still participating in issues here. If nobody is going to answer issues then the repos should be configured to prevent new submissions. When NPM left Github (for a while), they put their repo in Archived status.

[alexsch01]

@thw0rted Instructions to fix it yourself: #517 (comment)

[dwelch2344]

Thanks for the DIY method @alexsch01, and apologies on the delayed response.

We're still exploring a few options on how we'll tackle issues like this, but what we can commit to is keeping protractor running in good form 🤘

@thw0rted thanks for pointing out the repo-level visibility concerns. I'll raise both points with our team & partners to get addressed asap

[StanislavKharchenko]

@dwelch2344 Do you need some contribution helps for upgrade Protractor with latest selenium-webdriver (4.x) treatment?
This approach will eliminate needs to use webdriver-manager, but just rely on selenium-manager which now works and maintain driver updates under the hood.
There are also more things from selenium 4, which is fully w3c and has broader browser supports. Selenium 3 is deprecated (JWP deprecated as well) and some time it will stop working with modern browsers (Protractor 7 will also stop working)

[dwelch2344]

@StanislavKharchenko yes! We definitely care and are committed for the long haul of keeping Protractor running, which invariably means staying on top of browsers + tools + etc.

Would love to chat. Shoot me an email and let's connect? Dave-at-HeroDevs.com

[VolodymyrDmytriukhin]

@thw0rted Instructions to fix it yourself: #517 (comment)

Thank you, it works for me