Is the `website` folder maintained?

[mathiasbynens]

There used to be a website at https://tc39.github.io/test262/website/default.html. Today that no longer works, but the website folder is still here: https://github.com/tc39/test262/tree/master/website Were the HTML files deleted by accident, or was the website folder supposed to be deleted entirely?

Example of what the website used to look like: https://v8.github.io/test262/website/default.html

[leobalter]

I believe the website has not been actively maintained since 2014.

With the amount of work we've had for ES2015, we highly focused in the coverage. I don't ever recall publishing the website since I started in this project (2015).

If we need to decide this, I'd suggest we drop this and in favor of decoupled tools for running tests. @bakkot also has a web-based tests runner.

Separately, I'd suggest we could have an informative-only website, with info we have in our markdown files and possibly suggestions how to run tests or pointing to current existing reports: test262.report + public browser CIs.

WDYT?

[leobalter]

I believe this is resolved by #2677. @mathiasbynens please let me know if there is anything else to be tackled on this topic.

[leobalter]

Reopening this with a question, should we remove the tools/packaging folder as well?

cc @rwaldron @syg

[syg]

Having stuff in tree is easier than having to sync another repo for V8, but I don't really have strong opinions here.

Ideally we should deduplicate parseTestRecord.py. The copy inside tools/packaging has diverged from the copy in https://github.com/test262-utils/test262-harness-py. (V8 uses the copy inside https://github.com/test262-utils/test262-harness-py.)

[rwaldron]

I also don't have a strong opinion about this. I generally err on the side of caution, which sometimes leads to dead weight, but maybe someone, somewhere depends on the dead weight 🤷🏼‍♂️