Join forces with voxpupuli/json-schema

[sandstrom]

Would it make sense for this gem and json-schema (https://github.com/voxpupuli/json-schema/) to merge the two projects?

That way, efforts could be concentrated on a single gem.

Maybe this doesn't make any sense, but wanted to bring up the idea. Either way, thanks for an awesome gem! 💎

[davishmcclurg]

Hi @sandstrom—thanks for the suggestion. I'm open to the idea (and considered bringing it up over there), but I'm hesitant because it feels like a lot of work. Do you have any ideas for how merging would work?

[sandstrom]

I don't know either code base, so hard to say on a technical level.

But I think the best approach is simply to decide among the maintainers on one of the projects, write a migration guide for the other one, and then make a statement saying something along these lines:

Hello everyone!

There are currently several JSON Schema validators in the Ruby community [list…],
but only a handful are updated. Keeping them up to date with JSON Schema updates
take some work.

We think that the Ruby community is better served by us focusing our effort on one project.
With more maintainers, we'll have more people that can help out. So myself and [others] have decided to combine the efforts of [project A] and [project B], and going forward
we will concentrate our work in the [project A] repo.

We'll continue to provide bug fixes for [project B], but support for new versions of
JSON Schema will be focused on [project A] going forward.

…

(which project work should continue in is kind of besides the point, but from my limited view your project seems to be more up-to-date)

Obviously, if there are key functionality only available in one project, it could make sense to port it.

But generally this is just a realisation that maintaining a project requires work, and combining is sometimes a good idea.

An alternative could obviously be to just try to recruit more maintainers, without subsuming another project.

[davishmcclurg]

I reached out over there: voxpupuli/json-schema#423 (comment)