Here are some tasks that we will probably be doing in the incoming weeks to setup impress.js in a state where everything is focused well documented for future contributors and users of impress.js.

Clean up

The tasks here take in consideration my comment in the state of the project and @bartaz suggestions in the same thread.

• Check all Pull Requests to find the ones where the OP is still interested in keeping track of it with the following message:

Hi , in an effort to clear up older issues/PRs we are pinging back to know if you are still tracking this request.

To give a little bit of context, recently a decision was made in the project to make the development more active and the first task is to clear up older PRs like this one to see if the OP is still interested in keep it going.

If the OP does not want it anymore, just close it or create an issue for tracking purposes.

• Check all issues and close duplicates. If one issue refers to more than one feature, create one issue for each. (X-reference everything with github linking so we can get the whole context from any endpoint.). If the issue is solved, close it.
• Review all PRs and close the ones that doesn't make sense or the ones that are doing more than one thing after acknowledgement of the OP (or 1 week of no response).
• Review all issues and close the ones that doesn't make sense after acknowledgement of the OP (or 1 week after no response).

At this point we will have only the essential issues/PRs open, all the others will be closed.

Contributing

• Create a CONTRIBUTING.md file to guide new contributions (or filter existing ones). Here is a nice example. Add to the "WANT TO CONTRIBUTE?" section of the README.
• Review the changelogs (Fill the changelog in the "Releases" page for every version released so far)

Documentation

• Clear the wiki, removing projects that are no longer maintained and useless pages (Fixed on choiceschances.com redirecting, may be compromised #524 (comment)).
• Document the currently supported API in the README (API reference docs #563).
• Document the support only for evergreen browsers that support CSS 3D transform (easier than always having to update the support) (Document support only for evergreen desktop browsers based on feature detection #565)

Release

• Create a new minor release
• Release on npm (Feature Request: NPM #426)

... After all that, I will create a new issue with tasks regarding the open PRs and what we will be doing next for the future of impress.js!

ping @impress/mergers