Benjamin Lupton

It's inside the v1.8 branch, though that branch isn't stable yet. Not sure when I'll be able to line up more work to pay for history.js development, so feel free...

Alright invitations to the browserstate github organisation have been sent to each of you. Let's discuss how the workflow and permissions should work. Currently, you all have read access, this...

@EminezArtus doesn't seem you are on the slack yet? @nevace @dherran I've started the conversation on slack, will be more active from today.

Hrmm. Anyone keen to take over maintenance, I'm happy to make this commonjs compliant and do other improvements providing we can get some funding behind it. For some background on...

> @balupton Is the company which took over the copyright to history.js planning to maintain it, or just list it on their projects page? Bevry is my company. We created...

Not sure. My last content edits were 3 years ago. Someone could certainly check. What we really need is a acid test for the html5 history API so a table...

@istrasoft I believe that in a beta build I was working on before I handed it over to @andreasbernhard I had caused the separation. It was initially done as best...

Sweet, is there a particular branch I should fork to do this on?

Working on this on the docpad branch - https://github.com/browserstate/history.js/tree/docpad

This is ready. The branch needs the latest changes merged in. We also need to decide how to name the files going forward, as providing pre-bundled files is very 3...