Looking for new maintainers about tablecloth HOT 7 CLOSED

Hi Paul,
The last quarter of the year was a bit rough for me (currently undergoing a relocation, so zero to none time for open source), but once dust will settle I'll be glad to finish the transition to the next branch, as well as the X.Mutate submodules, as was originally planned.

I use tablecloth regularly and really want this project to thrive.

from tablecloth.

I still see tablecloth as a very viable choice for an alternative standard library of OCaml. Its API is much more consistent to me compared to Stdlib or Base, and much more modernistic with borrowed bits from Elm and maybe Rust.

I would love to take up the work of moving tablecloth forward on OCaml platform.

from tablecloth.

Thanks! Here's my current plan for moving forward:

• release current code as tablecloth-rescript
• merge next into main
• rewrite README to reflect current direction (see #214)
• split repo into 2 new repos: tablecloth-ocaml-base, tablecloth-rescript
• release 0.1.0 onto opam and npm
• add fsharp implementation, release onto nuget
• add "spec" - lists of functions/types and test cases that are then used in the 3 implementations

from tablecloth.

Looks good to me. The only thing I would add is at some point in the future we should move these repositories to a tablecloth GitHub organisation.

@pbiggar I suppose we can start picking up the work when we're splitting the repo? Or do you think there are things in next that we can help wrap up?

from tablecloth.

Hmmm, tablecloth org is taken, but not by me. I wonder is it possible to contact the owner.

from tablecloth.

Looking through the codebase, splitting the repo has some unanswered questions, such as what do we do about the website. So maybe let's work on switching to the new plan from #214 and go from there.

from tablecloth.

I'm going to close this issue for now as it seems I'm still here. Let's move discussion into other issues, mostly #214.

from tablecloth.