Turn repo into pull request?

[ProLoser]

Wouldn't it make more sense to pull request this into the original project?

[evancz]

Sure, I think it makes sense to add it for people who don't know Elm. What needs to be done? I have not looked into this much.

That said, having this as a separate repo with simple build instructions seems really valuable for people interested in Elm specifically. So I'd want to keep a version that I control so it can be totally up to date with whatever is going on in Elm and so that it is easy for people to fork and build.

Can all of these goals be met?

[ProLoser]

I think other people would be just as capable (including yourself) to keep
the project up to date if it's a fork or branch vs this repo but whatever
you want to do, I was just suggesting.
On Oct 14, 2014 4:48 PM, "Evan Czaplicki" notifications@github.com wrote:

Sure, I think it makes sense to add it for people who don't know Elm. What
needs to be done? I have not looked into this much.

That said, having this as a separate repo with simple build instructions
seems really valuable for people interested in Elm specifically. So I'd
want to keep a version that I control so it can be totally up to date with
whatever is going on in Elm and so that it is easy for people to fork and
build.

Can all of these goals be met?

—
Reply to this email directly or view it on GitHub
#7 (comment).

[passy]

For reference: tastejs/todomvc#1041

And by the way, I'd still recommend to keep this repo once it lands and sync it regularly. That way this repository can be used to iterate on top of the latest version of elm-html while the TodoMVC-version can provide a live version of the latest stable release.