Commit 47bf6689 authored by Hueser, Christian (FWCC) - 138593's avatar Hueser, Christian (FWCC) - 138593 Committed by Huste, Tobias (FWCC) - 111645

Incorporating all review suggestions

* Rephrasing some sentences according to review.
parent 84b8fa63
......@@ -6,9 +6,8 @@ author: none
additional_css:
- services/services-page-images.css
excerpt: >-
HIFIS Software offers a Helmholtz-wide GitLab service
that is free-of-charge and available to all people affiliated with
the Helmholtz Association and its partners.
HIFIS Software offers a free-of-charge Helmholtz-wide GitLab service
that is available to all people within the Helmholtz Association and their partners.
---
<p>
......@@ -18,21 +17,20 @@ excerpt: >-
Offering a sophisticated Software Project Management Platform is an
important prerequisite to achieve this.
The Software Project Management Platform
<a href="https://gitlab.com">GitLab</a>
<a href="https://about.gitlab.com">GitLab</a>
has already become a de-facto standard for many Helmholtz centers
in the past years.
Most of the centers offer GitLab already as a service to their
scientists.
Many centers offer GitLab to their scientists.
In order to bundle resources and foster cross-center collaboration
HIFIS decided to offer a
HIFIS Software offers
<a href="https://gitlab.hzdr.de">Helmholtz GitLab</a>
to all Helmholtz disregarding the center affiliation of scientists.
to all Helmholtz disregarding the center affiliation.
The benefits and synergies of using GitLab are manifold.
Nowadays, research software needs to be open, transparent, reproducible,
accessible, findable, reusable just to name a few desired properties.
We believe that a full-fledged feature-rich open-source software like
GitLab is the right tool to support scientists to develop such software
that adhere to these properties.
that adheres to these properties.
</p>
<h1>Features of the Helmholtz GitLab Service</h1>
......@@ -46,13 +44,11 @@ excerpt: >-
<div>
<h3>Version Control with Git</h3>
<p>
One reason for many Helmholtz research centers to chose GitLab as
One reason for many Helmholtz research centers to have chosen GitLab as
the right tool might be the popularity of the Version Control System
<a href="https://git-scm.com/">Git</a>.
GitLab is using Git under the hood and Git and GitLab interact
with each other just seamless.
While it is possible to use Git only locally or GitLab only remotely
the most benefits arise by combining those two.
with each other seamlessly.
With Version Control scientists are able to keep track of their
changes they make during research software development due to the
fact that Git stores the complete history of changes in the
......@@ -61,12 +57,12 @@ excerpt: >-
previous versions or even restore previous versions of the software.
GitLab or any other Git-based Software Project Management Platform
offer a central point to exchange code and ideas with others and
render close and fruitful collaboration between scientists possible.
But what if a scientist already uses another Git-based Software
render close and fruitful collaboration between scientists.
But what if you already use another Git-based Software
Project Management Platform?
That's perfect, no worries.
GitLab offers an
<a href="https://docs.gitlab.com/ee/user/project/import/">import wizard</a>
<a href="https://gitlab.hzdr.de/help/user/project/import/index.md">import wizard</a>
with which researchers can migrate their remote Git repositories
just easily if the necessity arises.
</p>
......@@ -87,9 +83,9 @@ excerpt: >-
<div>
<h3>Project Management with GitLab</h3>
<p>
Collaboration is such a necessity mentioned in the previous section.
As mentioned in the previous section, collaboration is such a necessity.
Today, there is literally no research project that is not driven
by collaboration with other researchers.
by collaboration.
Hence, project management is an important task and duty of
researchers in order to make good progress in their research
projects.
......@@ -102,14 +98,13 @@ excerpt: >-
<a href="https://gitlab.hzdr.de/help/user/project/milestones/index.md">Milestones</a>,
<a href="https://gitlab.hzdr.de/help/user/project/labels.md">Labels</a>,
<a href="https://gitlab.hzdr.de/help/user/project/repository/branches/index.md">Branches</a>,
<a href="https://gitlab.hzdr.de/help/user/project/merge_requests/index.md">Merge Requests</a>,
<a href="https://gitlab.hzdr.de/help/ci/review_apps/index.md">Review Apps</a>
<a href="https://gitlab.hzdr.de/help/user/project/merge_requests/index.md">Merge Requests</a>
among many other useful features.
This platform is very open in terms of supported workflows in
research software projects and can be adapted to almost any
practical software development workflow you may think of.
It is just so easy to see and keep track of who is doing what and
how much progress is made in a project.
Using the <a href="https://gitlab.hzdr.de">Helmholtz GitLab Service</a>
makes it easier to see and keep track of the progress of your projects.
</p>
<p>
<a href="https://gitlab.hzdr.de/help/user/project/index.md" type="button" class="btn btn-outline-secondary btn-sm">
......@@ -128,22 +123,18 @@ excerpt: >-
<div>
<h3>GitLab Continuous Integration</h3>
<p>
Continuous Integration (CI) is one of the key features we would like
to promote and introduce to scientists new to these tools.
Almost every software product benefits from automated tasks that
may be triggered when interacting with GitLab like when scientists
push new changes to GitLab.
So called CI pipelines may be triggered that for example
automatically build, test and finally deploy the software product
to a container or package registry or some staging or production
Continuous Integration (CI) is a first-class citizen available free-of-charge
and already activated for all users.
Almost every software product benefits from automated tasks.
CI pipelines can automatically build, test and finally deploy the
software product to a container, package registry or a staging/production
environment on which simulations may run.
Often these automated task are used as quality gates which
need to be passed successfully in order to be able to integrate
the code change into some mainline.
Developers are able to "integrate" their contributions
"continuously" and often because a high level of automation done
in the background supersedes many of the time consuming tasks that
need to be done manually otherwise.
"continuously" and due to a high level of automation many of the time
consuming tasks don't need to be done manually.
Thus, researchers can focus on doing research and not on doing
tedious tasks again and again.
</p>
......@@ -164,11 +155,10 @@ excerpt: >-
<div>
<h3>GitLab Container Registry</h3>
<p>
Containers have become very popular, Gitlab takes that into account
by offering a so called Container Registry that is very similar
to Docker Hub and is able to store Docker images among others.
Containers have become very popular: Gitlab takes that into account
by offering Container Registry very similar to Docker Hub.
Once research software developers build their own images they can
be stored centrally in such a registry for later use.
be stored centrally in such a registry for later reuse.
</p>
<p>
<a href="https://gitlab.hzdr.de/help/user/packages/container_registry/index.md" type="button" class="btn btn-outline-secondary btn-sm">
......@@ -191,7 +181,8 @@ excerpt: >-
the most prominent candidates like PyPI (Python), Conan (C++),
Maven (Java), NPM (NodeJS), Composer (PHP), NuGet (.NET), etc.
so that packages can be stored independently from these public
registries.
registries. On top GitLab also adds access control to
keep the group of project members manageable.
</p>
<p>
<a href="https://gitlab.hzdr.de/help/user/packages/package_registry/index.md" type="button" class="btn btn-outline-secondary btn-sm">
......@@ -211,14 +202,12 @@ excerpt: >-
<h3>GitLab Pages</h3>
<p>
Additionally, there is a feature called GitLab Pages that can be
used to publish static web sites regarding your project or software
project documentation.
In the same way like with other features, e.g. GitLab Container
and Package Registries, GitLab Pages can be used during automation
with CI pipelines.
That means each time there is a contribution to your project
the static web site or software project documentation is built
anew and made accessible to anyone with the right permissions.
used to publish static web sites e.g. your documentation.
Like other features, e.g. GitLab Container andd Package Registries,
GitLab Pages can be used during automation with CI pipelines.
Each time a contribution is made to your project
your documentation is rebuilt including the new changes
and automatically made accessible to anyone with the right permissions.
</p>
<p>
<a href="https://gitlab.hzdr.de/help/user/project/pages/index.md" type="button" class="btn btn-outline-secondary btn-sm">
......@@ -235,16 +224,12 @@ excerpt: >-
src="{{ site.directory.images | relative_url }}/services/undraw_feeling_proud_qne1.svg"
/>
<div>
<h3>HIFIS Helpdesk</h3>
<h3>Help and Support</h3>
<p>
Finally, we would like to suggest our HIFIS Helpdesk to our dear
fellows in case you would like to contact us regarding questions
you have when using GitLab, issues and bugs to report, or ideas
to be shared on how to improve the service.
Please visit our helpdesk or write us an email.
Thank you very much for your mindful contribution.
Please contact us regarding questions, issues, bugs or ideas
on how to improve the service via the HIFIS Helpdesk.
{% include contact_us/mini.html %}
{% include contact_us/mini.html contact_mail_link=site.contact_mail_for_gitlab %}
{% include helpdesk/mini.html %}
</p>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment