Skip to content
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.

Proposal for new json-schema website #1

Closed
Relequestual opened this issue Jul 27, 2015 · 1 comment
Closed

Proposal for new json-schema website #1

Relequestual opened this issue Jul 27, 2015 · 1 comment
Assignees

Comments

@Relequestual
Copy link
Member

@json-schema-org/owners

Plan proposals

Apologies for not having gotten to writing this proposal out sooner. I think we can all agree, time on this project is stretched thin!

First before discussing the new website, I think some pre-work is needed regarding the structure of the json-schema working group, and formalising yourselves as chairs of the project (if you are willing). I am happy to take on some responsibility for public communications and organisational elements for the project.

My suggested plan is as follows

  1. Review the list of libraries which implement json-schema and the json-schema test suite, and ask each of them if they would like to become involved in json-schema, including an explanation of the current state of affiars (of course after your approval on the wording). I would also like to ask them what teams they could see within the project, and any high level elements they would like to be involved in.
  2. Further, scan through the curren open issues, looking for any potentially interested individuals who also might like to be involved in the project, asking similar questions.
  3. Once this is completed, there should be a list of individuals who are keen to contribute to the re-establishing of the projects workforce. We could then create a private google group to enable internal communications. I would also encouridge everyone to join the irc channel on freenode.
  4. With an established working group, who can then evaluate and re-establish the requirements for draft 5. If I understand / have read correctly, the plan was for draft 5 to be a tidy up release, before the first version of the specification is put out as an RFC. (Speaking of which, did the project get any responses from the RFC? If so, how do we get hold of them?)

This will allow the project to evaluate the state of draft 5, and how to move forward to make it ready for publishing as an RFC. (I'd like to be part of the review process for this!)

I noticed that getting draft 5 sorted has been raised as issues here json-schema/json-schema#167 and here json-schema/json-schema#130 . cc'ed so people can follow discussions.

Regarding the website

Part of contacting a number of people, I would seek comments on the current website, looking to evaluate if it meets the current users expectation and needs. I'd do this in the form of a google questionaire.

If a re-structure of the site is needed, consider a few alternatives.

Start re-build using bootstrap. Bootstrap would allow for a faster build, while also making it easier for others to contribute. After some basic layouts are constructed, create a number of github issues and associated milestones for the website rebuild.

I'd like to also spend some time on / directing people involved, to the Understanding JSON Schema web book from the Space Telescope Institute. Maybe something on how to get involved in the specification.

@Relequestual
Copy link
Member Author

Whole effort seems to have stalled =[

handrews pushed a commit that referenced this issue Apr 2, 2019
Relequestual pushed a commit that referenced this issue May 9, 2019
philsturgeon pushed a commit that referenced this issue Mar 19, 2020
Synchronize with remote master again
Relequestual added a commit that referenced this issue Feb 20, 2021
Add warning that Rel JSON Pointer is not used
Relequestual pushed a commit that referenced this issue Feb 22, 2021
Relequestual pushed a commit that referenced this issue Mar 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant