Open WIN Community issueshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues2022-07-03T11:14:37+01:00https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/42[gitlab/github] how to mirror repositories between gitlab and github2022-07-03T11:14:37+01:00Bernd Taschler[gitlab/github] how to mirror repositories between gitlab and githubThere are ways to mirror (and sync) repositories from gitlab to github and vice versa. This is a way of using the strengths of both platforms (e.g. better CI on gitlab, larger community on github, etc.).
The official documentation about...There are ways to mirror (and sync) repositories from gitlab to github and vice versa. This is a way of using the strengths of both platforms (e.g. better CI on gitlab, larger community on github, etc.).
The official documentation about mirroring from gitlab: https://docs.gitlab.com/ee/user/project/repository/mirror/
A useful guide by a developer: https://dev.to/brunorobert/github-and-gitlab-sync-44mn
Quick take-aways:
- Syncing from gitlab to github is easier (apparently can be turned on from settings in a few simple steps).
- Wikis, issues, discussions, boards will not sync between the mirrored repos.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/37[documentation] protocols db - format for user guides on gitlab pages2022-03-02T13:05:38+00:00Bernd Taschler[documentation] protocols db - format for user guides on gitlab pagesThe `just-the-docs` theme for jekyll gitlab pages allows only for a maximum of 3 levels in the section hierarchy. For the MR protocols database, the first and second level are already taken by *Open WIN Tools* > *Open MR Protocols*.
Th...The `just-the-docs` theme for jekyll gitlab pages allows only for a maximum of 3 levels in the section hierarchy. For the MR protocols database, the first and second level are already taken by *Open WIN Tools* > *Open MR Protocols*.
This means that the user guides live on the third level (e.g. *Open WIN Tools* > *Open MR Protocols* > *Guide for WIN Users*) and can't have any further subsections.
So I was thinking about a couple of possible options:
1. Publish each guide as a one long, self-contained page.
2. Split off the step-by-step db access guides from other thematically distinct topics (e.g. why make protocols public, how to create a DOI, etc.) and indicate on each page whether this applies to all users or internal users only.
3. Create a pseudo-hierarchy by adding numbered sections in the title of individual pages. For example:
- *Open WIN Tools*
- *Open MR Protocols*
- *1. Guide for WIN Users*
- *1.1 Why make your protocol public*
- *1.2 How to add a DOI*
- *1.3 How to access the database*
- *...*
- *2. Guide for External Users*
- *2.1 How to access the database*
I'm leaning towards option 3 but it might look a bit messy / clumsy. Any preferences or other suggestions?Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/63Add information about zenodo as a data repository2023-07-04T08:58:41+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd information about zenodo as a data repository## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/how/#zenodo
## What is the issue?
information incomplete
## How do we solve the issue?
Describe main features and benfits of zenodo. Link to thier guides as appropriate.
Benefits I can think of:
- "restricted access" deposits for reviewer only and senestive materials.
- Could link in the future to a "WIN zenodo community".
- doi versions
- Integration with GitLab CI (see [FSLeyes CI](https://git.fmrib.ox.ac.uk/fsl/fsleyes/fsleyes/-/blob/master/.gitlab-ci.yml))
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/60Update links to WIN intranet when things move over from Sharepoint2023-07-04T08:57:58+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukUpdate links to WIN intranet when things move over from Sharepoint## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] documentation (eg. typos, broken links)
## Where is the issue?
> Please include links to the affected ...## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] documentation (eg. typos, broken links)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
Check accross all community pages.
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
WIN Intranet content will be moved from Sharepoint at the end of March. Some links on the community pages will need to be updated. Links to university Sharepoint pages will also be moved.
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
- [ ] Search across whole project for "https://sharepoint.nexus.ox.ac.uk/"
- [ ] Find replacement pages on new intranet
- [ ] Update links
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
Cass and @stuart will communicate when new pages are live. Try to replace as quickly as possible to keep community pages current.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/59Report on ambassadors dinner2023-07-04T08:57:04+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukReport on ambassadors dinner## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>...## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
> <p> Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk. </p>
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] feature request (eg. add GitLab tutorial)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
[Events on community pages](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/community/events/)
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
Would be nice to include a short write up on the Ambassadors dinner, with photos and chairs notes (see [ambassadors comms folder](https://git.fmrib.ox.ac.uk/open-science/community/open-win-ambassadors/-/tree/master/comms). This is to advertise how nice the event was, and as something to work from for next time :)
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Write up a short report of the day. Can be narative and general.
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/Peter DoohanPeter Doohanhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/58make open@win.ox.ac.uk the primary contact address2023-02-28T11:34:55+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukmake open@win.ox.ac.uk the primary contact address## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>...## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
> <p> Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk. </p>
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [x] documentation (eg. typos, broken links)
- [ ] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
[Contact page](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/contact/) and other references to cassamdra.gouldvanpraag@psych.ox.ac.uk
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
Cass' personal email is listed as the primary contact for all enquiries. This would be better handled by a share inbox, to share the learning and outcomes of conversations.
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Replace appropriate references to cassandra.gouldvanpraag@psych.ox.ac.uk with open@win.ox.ac.uk
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/56Update/change issues template2023-02-20T11:29:22+00:00Miguel FarinhaUpdate/change issues template> <p>Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.</p>
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/communit...> <p>Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.</p>
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets.
- [ ] bug/error report
- [ ] documentation/typos
- [X] feature request (enhancement)
- [ ] question
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend.
## Where is the issue?
> Please include links to the affected page(s) and lines or sentences.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
Having an issue template that's more intuitive and easier to complete and associated instructions in Open Win Community Pages.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
Make this simpler to use for non-experienced users.
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/55alternative to Atom text editor2023-07-04T08:54:55+01:00Bernd Taschleralternative to Atom text editor## What is the current behaviour?
The gitlab tutorials are recommending to use the Atom text editor. Unfortunately, Atom has recently been discontinued (see official [blog post](https://github.blog/2022-06-08-sunsetting-atom/)) and alth...## What is the current behaviour?
The gitlab tutorials are recommending to use the Atom text editor. Unfortunately, Atom has recently been discontinued (see official [blog post](https://github.blog/2022-06-08-sunsetting-atom/)) and although people can still use it, it is no longer maintained (i.e. no new security updates, package management stopped working, etc.).
## What is the expected/preferred behaviour?
We should find an alternative and update the community pages accordingly (especially the [Atom tutorial](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/1-3-tools-atom/) page).
## Other information
A potential alternative is sublime text: https://www.sublimetext.com/
Other options: https://stackshare.io/atom/alternativesMiguel FarinhaMiguel Farinhahttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/54Meet the Ambassadors 2022-2023 - all information correct?2023-07-04T08:56:12+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukMeet the Ambassadors 2022-2023 - all information correct?## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
## What is the current behaviour?
Cass quickly wrote some [stuff to introduce the new ambassadors](https://open.win.ox.ac.uk/pages/open-scienc...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
## What is the current behaviour?
Cass quickly wrote some [stuff to introduce the new ambassadors](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/ambassadors/meet_ambassadors/), but this has not been verified! Also links to some people's departmental pages etc are missing.
## What is the expected/preferred behaviour?
Please review this information and amend as appropriate. Please confirm below if you are happy with all content under your name.
## What is the motivation / use case for changing the behaviour?
This information reflects you, so it should be accurate and consistent with the image your want to show! This is also a useful page which you can use to evidence your engagement with this program (e.g. link to it on your CV), so let's make it good :).
## Confirmed up to date:
- [x] @wym003
- [x] @vyp730
- [x] @pfr545
- [ ] @mtach
- [x] @bpz864https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/53Roadmap needs updating2022-10-11T19:47:21+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukRoadmap needs updating## I'm submitting a ...
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
The [roadmap](http://localhost:4000/pages/open-science/community/Open-WIN-Community/docs/community/roadmap/) is out of date and sh...## I'm submitting a ...
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
The [roadmap](http://localhost:4000/pages/open-science/community/Open-WIN-Community/docs/community/roadmap/) is out of date and should probably reflect more about the open data portal or what we're working on more broadly.
## What is the expected/preferred behaviour?
Update the roadmap to reflect the project more broadly. Perhaps separate roadmaps for 'community' and 'resources'?https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/52Links don't work on Open Tasks Pages2022-07-12T12:28:56+01:00Stuart ClareLinks don't work on Open Tasks Pages> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
Links on https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tasks/ for WIN members and external users seem to point to the wrong page. Tried to fix myself, but couldn't work out where the page was. Sorry :(
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/50Fix typos2023-07-04T09:01:07+01:00Yingshi FengFix typos> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
There are a few typos on the community page, suggested by @nym920.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
The typos being fixed.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.
We might copy and paste the pages into word for an automatic spelling check, or fix this issue in another session when we have more time.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/49[documentation] Mirroring to GitHub2022-07-03T11:13:31+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Mirroring to GitHub
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
It is often beneficial to host material on GitHub, for added external engagement. Th...
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
It is often beneficial to host material on GitHub, for added external engagement. The recommenced way of doing this is to mirror your GitLab repository to GitHub. We should write guidance on how to do this.
## What is the expected/preferred behaviour?
Link to this guide: https://git.fmrib.ox.ac.uk/help/user/project/repository/mirror/index.mdCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/46Community feedback at guidance on pros and cons of sequences2022-07-06T10:52:44+01:00Verena SarrazinCommunity feedback at guidance on pros and cons of sequences
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would...
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
After presenting the MR protocol database to my lab, my colleagues suggested that we add a section to the documentation to ask researchers to describe the pros and cons of the sequences.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
We have added some new text (commit 3816bfcceb5da160f8edf61a258421d4e2d3f15f) to the documentation in the description section. It would be useful to get feedback from my lab to confirm this meets the requirement.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/45Add links to info about fslpy, data-tree and pipe-tree2022-06-18T09:36:22+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd links to info about fslpy, data-tree and pipe-tree## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Some very cool stuff exists on [https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html]...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Some very cool stuff exists on [https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html](https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html). Could we link to that from the community pages, e.g. under [Open Analysis](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/analysis/)?
Also developments on data-tree and pipe-tree would be wonderful to share!
## What is the expected/preferred behaviour?
Submit a merge request to update the [Open Analysis](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/analysis/) page with some blurbs about (and links to):
1. fslpy and conda installation
2. data-tree
3. pipe-tree
## What is the motivation / use case for changing the behaviour?
Share these developments!
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/43[website] Add information about how to create and publish interactive figures2022-10-11T19:35:32+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] Add information about how to create and publish interactive figures## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two people have asked me about how to make interactive web-apps to support their pub...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two people have asked me about how to make interactive web-apps to support their publications. We should add this information to the community pages.
## What is the expected/preferred behaviour?
Here is the information I've shared:
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/40[documentation] GDPR => UK GDPR2022-05-06T14:07:25+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] GDPR => UK GDPR> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
documentation currently refers to GDPR. As of 2022 year UK GDPR has passed equivalency testing and is now in use.
## What is the expected/preferred behaviour?
references to "GDPR" throughout the pages should be updated to "UK GDPR"
## What is the motivation / use case for changing the behaviour?
Stay current!
## Other information
[ISO guide](https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/)https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/39Upper level links not accessible2022-04-06T11:15:03+01:00Yingshi FengUpper level links not accessible> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
- The open WIN community page can only be accessed via open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/ but not any of the upper domain (e.g. open.win.ox.ac.uk, open.win.ox.ac.uk/pages/open-science/community). It could be confusing for users who could like to find the community by typing the weblink.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
- The open WIN community page can be directly linked to the root page (i.e., open.win.ox.ac.uk) and the root page should be accessible for users.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
- To make the open WIN community page more accessible.
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/38[documentation] Add link to GitLab Pages template2022-05-06T13:50:51+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Add link to GitLab Pages template## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There are some Jekyll templates for creating GitLab Pages sites, but they are only accessible if you know to look for them.
## Wh...## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There are some Jekyll templates for creating GitLab Pages sites, but they are only accessible if you know to look for them.
## What is the expected/preferred behaviour?
Link the [beautiful Jekyll](https://git.fmrib.ox.ac.uk/open-science/community/beautiful-jekyll) [just-the-docs](https://git.fmrib.ox.ac.uk/open-science/community/just-the-docs) and [basic Jekyll](https://git.fmrib.ox.ac.uk/open-science/community/gitlab_pages_jekyll_template) templates from the [community gitlab pages](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/).
## What is the motivation / use case for changing the behaviour?
Improves accessibility and knowledge sharing
## Other information
Be sure to include details on how to give feedback on the templates, i.e. as issues of MRs on the template repos themselves.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/36[GitLab Pages] basic template2022-02-22T19:53:20+00:00Bernd Taschler[GitLab Pages] basic templateHi,
I've been trying to create a basic template repo that includes the necessary files to publish a repo with GitLab Pages (maybe to be included in future in addition to the existing guide for GitHub pages).
I couldn't find any documen...Hi,
I've been trying to create a basic template repo that includes the necessary files to publish a repo with GitLab Pages (maybe to be included in future in addition to the existing guide for GitHub pages).
I couldn't find any documentation on the intranet, so I tried to reverse-engineer the existing setup for the 'Open WIN Community' repo.
Because the WIN/FMRIB gitlab instance is managed differently than the (main) gitlab.com, there are additional install requirements and dependencies to be sorted out. After some trial and error I got the CI/CD runner compiling everything successfully. However can't get the pages to display at the designated location, i.e. when trying to view the GitLab pages in a browser I get an error saying 'This page can't be reached.'
Checking with the 'Open WIN Community' repo, I noticed that the given URL where the pages are supposed to be served also doesn't work. I.e. accessing from within the repo --> 'Settings' --> 'Pages' --> "Your pages are served under:" https://open-science.pages.fmrib.ox.ac.uk/community/Open-WIN-Community" ... this link doesn't work. In fact, the repo is served at: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/ instead.
So, I don't understand how the pages are served at a different URL than what the repo thinks it should be:
- Why does the first link above not work?
- How have the existing Community pages been set up?
- What is necessary to serve a different repo with GitLab Pages from within the fmrib/WIN gitlab instance?Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk