Script repository design document

[Nick Draper]

Create a design document for the script repository implementation.

[Nick Draper]

Moved at the code freeze for release 2.4

[Gesner Passos]

Add ScriptRepository Design and Requirement documentation

under development

re #6174

Changeset: 0106c29f62366918c950e4d94c69fb698a040c85

[Gesner Passos]

Description of two methods ScriptRepository

re #6174

Changeset: 21647542d642b51a77d239be68f26d0805cc1816

[Gesner Passos]

Rewritten after decision to move to a custom solution

re #6174

Changeset: e94357d9f08960635fb5e7dc111f0d5ffcefac26

[Gesner Passos]

Rewritten after moving to custom solution

re #6174

Changeset: c0c3653521301e25544854fe96162915e8cc55c5

[Gesner Passos]

Small improvements on the documentation

re #6174

Changeset: e424815d151f5ab8230d49429285ec368af0c1bc

[Gesner Passos]

Update and add the upload and gui for script repository

re #6174

Changeset: 2a762e12b8bc3ba356d8b5145d2be44328fc8cad

[Gesner Passos]

branch : feature/6174_script_repo_design

Tester: Read the documentation, specially the sections Script Repository GUI and Uploading Strategy. You should agree with this document, and them merge it to master. If you agree, this will be the implemented version of ScriptRepository. (The ScriptRepository Service has already been implemented in #6175).

Attention: the git macros will not work here. You will have to merge using the git commands:

git checkout master
git fetch -p
git pull --rebase
git merge --no-ff origin/feature/6174_script_repo_design

If you agree with the document, publish it:

git fetch
git rebase --preserve-merges origin/master
git push origin master
git push origin :feature/6174_script_repo_design

[Alex Buts]

I need to read, discuss and deal with it anyway, so I am snapping it for verification.

[Alex Buts]

refs #6174 Couple of typing errors

Changeset: cab1908072dc96062808fab96b4c4d03f670d407

[Gesner Passos]

Update and add the upload and gui for script repository

re #6174

Changeset: 2a762e12b8bc3ba356d8b5145d2be44328fc8cad

[Alex Buts]

refs #6174 Couple of typing errors

Changeset: cab1908072dc96062808fab96b4c4d03f670d407

[Alex Buts]

This is very strange situation with the Track.

I have closed this ticket last week and wrote number of comments about it. The ticket has been integrated into the GIT and I closed the ticket. Here I have unfinished ticket again and no comments. Strange.

[Alex Buts]

Apparently Track have gobbled up comments and fixed status, so I do not have confirmation message. Brief comment on the design from one I can remember.

1) A bit better document formatting would be useful, e.g. the design requests formatted as a table would be beneficial -- at least to understand what is implemented and what is not. The good example for the design was Mantid Python scripting.

2) A git forkflow is not really appropriate for documentation. I think Word collaboration would be more convenient.

There were couple more but they are probably minor so I do not remember it now

[Stuart Campbell]

This ticket has been transferred to github issue ​7020