search

WICG / EventListenerOptions

An extension to the DOM event pattern to allow authors to disable support for preventDefault
Other
1.17k stars 140 forks source link

Should this repo be set to "archived"? #62

Open patrickhlauke opened 6 years ago

patrickhlauke commented 6 years ago

As work on this has migrated/merged to WHATWG, should we use github's archive feature to make it read-only, and somehow amend the readme to call this out a bit more somehow?

marcoscaceres commented 6 years ago

Ah, nice! I had no idea this was a thing! I'm fine to do that, but are there consequences/side-effects that we need to deal with first?

marcoscaceres commented 6 years ago

Ok, Github says:

This will make the WICG/EventListenerOptions repository, issues, pull requests, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions and comments read-only and disable any future comments. The repository can still be forked. Ensure you've changed any repository settings, considered closing all open issues and pull requests and updated your README before you archive this repository. Once archived, you can unarchive the repository at any time.

So, can someone update the README first to say that has all migrated to the WHATWG?

patrickhlauke commented 6 years ago

it's usually good practice to close all pending PRs/issues. and if you ever need to make changes, it needs to be unarchived first https://help.github.com/articles/about-archiving-repositories/

patrickhlauke commented 6 years ago

@marcoscaceres done https://github.com/WICG/EventListenerOptions/commit/139eb342e1cccb71c9be849927566a2ab6657097#diff-04c6e90faac2675aa89e2176d2eec7d8

patrickhlauke commented 6 years ago

@rbyers @dtapuska happy for this repo to be archived? i notice you have a few issues open (for yourselves)

RByers commented 6 years ago

Yeah everything should be tracked in WHATWG/Dom now, so I think this repo is valuable only from a history perspective. As long as archiving doesn't break URLs, I'm fine with that.