Possibly fork/re-write? (v3)

[bradtaniguchi]

@JLuboff How would you feel if I tried to fork/re-write a replacement for this library?

The main things I'd want to work on are ease of testing changes, via github-actions (see: #75) codespace development (#79), and updating the unit testing? (#79)

I also don't use this library but could think of a project I could use as a test-bed for this library.

Today I'm still interested in github-actions and automation testing, so it falls right in my ballpark to essentially get a project "on-top" of this one to help test it. With what I figured out back in #75, it shouldn't be a step or two out from getting a full stack test that runs in github actions to help maintain it going forward.

but I'd do that in my own fork/v3, that will use this codebase as a rough starting point, especially for the actual implementation.

Wanted to reach out here first, mainly for visibility as I saw #82 and #81 come in, and realized my older PRs are still floating around open as well.

LMK what you think, thanks!

[JLuboff]

@bradtaniguchi As we briefly spoke yesterday, I'm happy for you to do as you'd like with this library. You're welcome to continue to make/fine tune this repo or fork it and make it fully your own. I think you have some great ideas and can help further promote this library to a higher standard :D

[bradtaniguchi]

Adding a v3-rewrite tag and tagging any issues that will be targeted as part of a v3 version.

[bradtaniguchi]

Quick update, I started on the new repo, not on github yet but there is progress on this side. Easier to work on this than #87, since I can't break anything. But both are on my radar.