JEP for specifying the connectionfile

[JohanMabille]

Connection file JSON schema

This proposes to specify the connection file through a JSON schema, and have the specification and documentation live in a dedicated repo.

The JSON schema is joined as a standalone file.

---

I(s been a while since we proposed to move to the voting phase, let's fix it now ;) Ntice that further JSON specs should not been JEPs, but PRs to https://github.com/jupyter/schema

Voting from @jupyter/software-steering-council

• @gabalafou
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @ivanov
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @JohanMabille
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @jtpio
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @marthacryan
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @martinRenou
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @minrk
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @rpwagner
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @SylvainCorlay
  • [x] Yes
  • [ ] No
  • [ ] Abstain
• @vidartf
  • [x] Yes
  • [ ] No
  • [ ] Abstain

[JohanMabille]

@jupyter/software-steering-council kind ping on this one, similar to https://github.com/jupyter/enhancement-proposals/pull/105

[Zsailer]

I propose we move this to a voting phase. This has been open for nearly a year, so I think we can safely close the comment period. Now that the jupyter/schema repo is moving forward, this seems like a good time to proceed.

[SylvainCorlay]

The JEP has been approved unanimously.

• Yes: 10
• No: 0
• Abstention: 0

Merging