Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looking for new maintainers #277

Closed
pbiggar opened this issue Jul 8, 2022 · 7 comments
Closed

Looking for new maintainers #277

pbiggar opened this issue Jul 8, 2022 · 7 comments

Comments

@pbiggar
Copy link
Member

pbiggar commented Jul 8, 2022

Since both we and Rescript moved away from OCaml, we aren't seeing the same value in maintaining tablecloth, and we certainly haven't kept up with the work required to keep it relevant and useful.

I'd love to see someone take over the maintainership who has the time and inclination to take it in the right direction (see #214 for what I think that is)

If no-one is interested, it might be best to deprecate tablecloth.

If you're interested, feel free to reach out by email or in the Darklang slack, or just comment below.

@Lomand
Copy link
Contributor

Lomand commented Jul 9, 2022

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.

@pm5
Copy link
Collaborator

pm5 commented Oct 8, 2022

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.

@pbiggar
Copy link
Member Author

pbiggar commented Oct 9, 2022

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 Change of direction #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

@pm5
Copy link
Collaborator

pm5 commented Oct 10, 2022

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?

@pbiggar
Copy link
Member Author

pbiggar commented Oct 10, 2022

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

@pbiggar
Copy link
Member Author

pbiggar commented Oct 10, 2022

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.

@pbiggar
Copy link
Member Author

pbiggar commented Oct 11, 2022

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.

@pbiggar pbiggar closed this as completed Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants