CoffeeAndCode
Add Tests for Node 8.10
Thanks for the heads up @DanielMenjivar! At this point, I'm not sure the site is providing much value since many of the "js-next" features are now commonly found in the versions that AWS Lambda supports. I was actually thinking about letting the website expire soon. What do you think about that?
I just let the website expire so I'll be closing all issues. I'll leave the code open source on Github for now in case the project interests you.
@jonknapp to be honest I strongly disagree, ECMAScript constantly evolves, e.g. Node.js v10 will bring another ES features that v8 doesn't have, and if there are other differences in builds that AWS provides, we really need some source that confirms on that.
Anyway if you don't have time for maintenance, then it's totally fair, but then I would open search for contributors that can take project over :)
Do I hear a volunteer in that response? 😄
I'll update the homepage to mention the project is open to other contributors, but I've changed the website to redirect to this github account since it's not currently being maintained.
Sorry, I've been offline for a couple of days. I was going to say that today it's js-next, tomorrow it'll be js-next-next… But I see that @medikoo said the same thing, only better. I definitely see value in keeping the website up, even if it's passing all tests for now. It would be a shame to see this valuable resource disappear. I also understand that renewing the domain costs money though, on top of the time to run the tests and maintenance, etc. Unfortunately this is something that is currently outside the scope of my capabilities. @jonknapp I was going to offer you to contribute funds towards the domain renewal, if that helps. Let me know.
Thanks for the info. The money is not really the concern (I actually renewed it this morning), but more that I don't want to show bad information to people that looks like it should be correct. My lack of time to focus on fixing the site reflects poorly on the resource to the greater pool.
Maybe just adding a little disclaimer to the top of the website would be enough. Something along the lines of "We're interested in pull requests and additional maintainers to keep this resource up to date. If interested, please let us know by opening an issue."
Thoughts?
That makes sense. And a disclaimer at the top should be enough, I think.