Official-ify this fork

[loganvolkers]

There's a few things to do to make this fork more official.

• Release a new version on NPM (Using semver plz)
• Setup a .github folder tool
• Comment on individual issues and PRs and request people move their issues to the new repo
• Talk to @jdorn if he ever returns from the dead
• Setup protected branches
• Submit an application to the JsFoundation: https://js.foundation/
• Write a blog article about the above

[loganvolkers]

I have reserved the json-editor organization namespace on NPM: https://www.npmjs.com/org/json-editor/

[submitteddenied]

Hi Logan, thanks for taking the initiative with this project! Have you reached out to @jdorn using the contact details on his website? If not I'm happy to shoot him an email, which might be a more reliable way to reach him than via github mentions :)

[matthewslaney]

I would suggest as well that if there is no reply from @jdorn then the demo page in the readme should be replicated on a different server and an acknowledgement/link to the homepage of his site. This will both preserve the great demo page if his site goes down, and it will prevent superfluous traffic to the demo page on his site.

[jdorn]

Hi everyone. Thanks for taking initiative on json-editor and keeping it alive in my absence. Maintaining the project became too time consuming and overwhelming and I had to take a break. I'm happy to support this fork as the official version going forward. What can I do to help the transition?

[schmunk42]

@jdorn Great to hear from you!

Also sorry for not chiming in earlier from my side. I am very happy to see this project gaining some traction again. Thanks to @xvaara and @loganvolkers for taking care of setting up the fork.

Just some background information from our side... We're using json-editor heavily in our PHP app templates. I don't code that much with JavaScript, but we have several JS-dev in-house, but I surely can help with testing.

[loganvolkers]

@jdorn I think the least effort, highest impact thing you can do is to provide access to the project assets to this project's owners:

• Grants access to original github repo
• Grant access to NPM package
• Grant access to bower package
• Grant access to website (noticed it's your personal website so a redirect may be more appropriate?)

That will let us migrate the project to this fork under a Meritocracy governance model source

Alternatively if you want to maintain heavy control of the project, you could remain our BDFL (Benevolent Dictator for Life) and we could govern the project that way source

[danielo515]

I think one of the main points should be the NPM support. Everybody uses npm nowadays, and not being able to install this library through it is a deal breaker.

What about the CDNs ? They are an important way of distribution and nobody is talking about them

[eduo]

Not a bad idea also to edit the main page so it doesn't link to the original pages and downloads. It's easy to wind up back there by mistake by following the links in the main readme.

Other than that, I was very happy to see this project getting jdorn's official blessing.

[schmunk42]

I did some work on https://github.com/json-editor/json-editor/tree/develop - including fixed testing.

For publishing it on npm we'd need a release process which builds the dist files, see also #17 (comment)

Test & build has not to be done with Docker, for sure - feedback about this is very welcome.