names: add ORCiD public data sync

inveniosoftware / docs-invenio-rdm

InvenioRDM docs

https://inveniordm.docs.cern.ch/

MIT License

25 stars 68 forks source link

names: add ORCiD public data sync #682

Closed jrcastro2 closed 3 months ago

jrcastro2 commented 4 months ago

closes https://github.com/inveniosoftware/invenio-vocabularies/issues/353

utnapischtim commented 4 months ago

i think this is referring to https://github.com/inveniosoftware/invenio-vocabularies/pull/366. it is v13

That would mean it the flag for _Introduced in v13_ should be set or?

utnapischtim commented 4 months ago

we should really discuss how we handle that sort of documentation. i think waiting until the next version will be released is not a good option. IMHO. it produce a lot more work afterwards.

slint commented 4 months ago

we should really discuss how we handle that sort of documentation. i think waiting until the next version will be released is not a good option. IMHO. it produce a lot more work afterwards.

I fully agree, we should add a _Introduced in v13_ in this case and just merge in master. I will be a bit chaotic, but I don't see another way that doesn't make it very difficult to maintain different versions of docs in sync.

utnapischtim commented 4 months ago

I fully agree, we should add a _Introduced in v13_ in this case and just merge in master. I will be a bit chaotic, but I don't see another way that doesn't make it very difficult to maintain different versions of docs in sync.

good, but i think we should wait until dev and so v12 documentation has been merged. otherwise it would be little bit strange to see v13 documentation but no v12 documentation

fenekku commented 4 months ago

I fully agree, we should add a _Introduced in v13_ in this case and just merge in master. I will be a bit chaotic, but I don't see another way that doesn't make it very difficult to maintain different versions of docs in sync.

good, but i think we should wait until dev and so v12 documentation has been merged. otherwise it would be little bit strange to see v13 documentation but no v12 documentation

Yup, that's what I meant by parking it. :car:

ntarocco commented 3 months ago

Normally, we merge to master only things that are in the current (v12) or previous versions.

Anything else for future version should:

have the sub-header Introduced in InvenioRDM v...
merged to dev branch

When realising a new InvenioRDM version, the dev branch should be merged to master

ntarocco commented 3 months ago

I have changed the target branch. However, dev might need rebase on top of master. @jrcastro2 can you add the sub-header?

jrcastro2 commented 3 months ago

I have changed the target branch. However, dev might need rebase on top of master. @jrcastro2 can you add the sub-header?

Added.