whatevery1says / manifest Goto Github PK

consistent with -data -notebook -cloud et cetera.

If we have external links to https://github.com/whatevery1says/manifest however we will need to update them -- no forwarding from github repo urls.

not integrated into pages, but automatically appears in social media links to repo.

The projects file is named project-manifests-draft.md

Is our goal to have this out of draft before the end of the project? Should we just assign it an early release -- 0.1, 0.2 -- and release what we have?

Currently relationships is described under the RawData manifest description. It should probably move to collection manuscripts so that related documents are associated with all data in the collection. The property could be applied to each of the sub-nodes so that documents could be associated with data in individual branches.

I tagged the commits that I believe best represent v1.1 and v2.0.

Then in releases I created one for each -- github automatically creates a zip and tar, but I also manually attached the relevant file (1.1 and 2.0) as a named attachment. This also gives it a direct download link.

1. are the labeled commits correct?
2. should basic release notes of any kind be added to the releases?