Design vocabulary design using Github dev tools

[jesserobertson]

I think it would be worthwhile to have a crack at a Github-centered approach to developing vocabularies with the community. We've had some pretty good discussions from tech and non-tech people using the Github discussion boards, and I think we could maintain schemas and contexts alongside this, coupled with a more in-depth use of GitHub's code review tools.

I'd suggest the following groundwork needs to be laid:

• A good contributing.md doc that lays out how you could use pull requests and code reviews to make changes to central contexts and schemas
• A better explanation of what goes where in the repo
• A way of linking issues to new branches (have installed
• [maybe] agreeing on a workflow for linking issues to our project boards so that you can see what bits of the vocab are being worked on

Then we'd have to do the hard work of getting people to actually engage but at least there might be clear guidelines.

@jklump @dr-shorthair @fils @ramdeensarah thoughts?

[jklump]

The benefit of doing the vocabulary development in GitHub would be that everything is on one platform. Is there any example we can learn from and refer to?

The alternative would be to use ARDC's PoolParty, which is a dedicated vocabulary development tool, but it sits on a different system.

[jesserobertson]

@jklump not sure that there is an existing example. The other benefit to using GitHub is that we can maintain the continuous integration aspects, which helps because we're not just creating a vocabulary but also a coupled JSONSchema as part of the profile.

Also I don't know whether PoolParty supports JSON?

[jesserobertson]

Happy to use poolparty for the vocab development if this is easier for everyone though - I guess there just needs to be a path to a working profile somewhere.