software.hifis.net issueshttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues2021-01-11T13:04:31+01:00https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/203Mention post-installation steps in Docker blog post2021-01-11T13:04:31+01:00Erxleben, Fredof.erxleben@hzdr.deMention post-installation steps in Docker blog postWhen reading the Docker Tutorial: After installing Docker, some post-installation steps have to be taken on Linux to be able to run Docker as a non-root user. Since these are easily overlooked, specifically hinting at [these](https://doc...When reading the Docker Tutorial: After installing Docker, some post-installation steps have to be taken on Linux to be able to run Docker as a non-root user. Since these are easily overlooked, specifically hinting at [these](https://docs.docker.com/engine/install/linux-postinstall/) would be nice.Frere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/194Blogpost: Survey Results - Languages and VCS2020-12-17T09:41:34+01:00Erxleben, Fredof.erxleben@hzdr.deBlogpost: Survey Results - Languages and VCS# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
@KatDwo (correct interpretation of survey)
## Topic and Content
The blog post presents two graphs from the HIFIS 2020 survey analysis regarding language usage and VCS usage....# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
@KatDwo (correct interpretation of survey)
## Topic and Content
The blog post presents two graphs from the HIFIS 2020 survey analysis regarding language usage and VCS usage.
It outlines the implications for HIFIS consulting and education as well as the research software developers at Helmholtz.
## Target Audience
Helmholtz scientists who also write research software and RSEs in general
## Publishing Date
## Contribution
Informs about the results of the survey and provides transparency regarding the work of HIFISErxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.de2020-11-07https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/168GFZ Hackathon post has plain Markdown in excerpt2020-06-19T10:22:29+02:00Erxleben, Fredof.erxleben@hzdr.deGFZ Hackathon post has plain Markdown in excerptThe excerpt contains a markdown link that does not get processed and is inserted as-is..The excerpt contains a markdown link that does not get processed and is inserted as-is..Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/161Issue in S/MIME blog post2020-05-12T14:42:06+02:00Huste, TobiasIssue in S/MIME blog postWe were notified that the article is missing a step.
> I followed the instructions shown in
> https://software.hifis.net/tutorial/2020/04/15/smime-signing-git-commits
> , and it *almost* worked. I had to set the following git config too...We were notified that the article is missing a step.
> I followed the instructions shown in
> https://software.hifis.net/tutorial/2020/04/15/smime-signing-git-commits
> , and it *almost* worked. I had to set the following git config too:
>
> $ git config --global gpg.program gpgsm
>
> It appears git version 2.25.1 defaults to gpg on Pop!_OS Linux 20.04.
Please also verify if there is a difference between the operating systems when working on this issue.
The article was introduced by #138.Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/138Blog post S/MIME signing of Git commits2020-05-04T16:15:04+02:00Huste, TobiasBlog post S/MIME signing of Git commits# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@erxleb87 @hueser93
## Topic and Content
Both GitHub and Gitlab now support S/Mime signing of Git commits and display a proper `Verified` button along with the commit inform...# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@erxleb87 @hueser93
## Topic and Content
Both GitHub and Gitlab now support S/Mime signing of Git commits and display a proper `Verified` button along with the commit information. On GitLab, [MR!207612](https://gitlab.com/gitlab-org/gitlab/issues/207612#note_294972563) needs to be merged in order to fix some bugs. This blog post describes on how to setup and use signing of Git commits on Windows, Mac and Linux machines.
Examples:
- Github: https://github.com/tobiashuste/test-x509/commits/master
- GitLab@HZDR: https://gitlab.hzdr.de/frust45/test-x509
- GitLab: https://gitlab.com/tobiashuste/test-x509/-/commits/master (not working yet)
## Target Audience
Helmholtz scientists who have access to X509 certificates and want to use them for their Git commits as well.
## Publishing Date
`2020-03-06`
## Contribution
Scientists will be encouraged to sign their Git commits to prove that this work has really been done by this person.Huste, TobiasHuste, Tobias2020-03-20https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/158Test blog post for demonstration2020-04-20T14:45:20+02:00Huste, TobiasTest blog post for demonstration# Blog Post Suggestion
## Authors
@frust45
> Name the involved authors here, maybe suggesting contributors.
> If you know their GitLab aliases, use @username to keep them
> involved.
## Reviewers
@erxleb87
@jandt-desy
> Who do y...# Blog Post Suggestion
## Authors
@frust45
> Name the involved authors here, maybe suggesting contributors.
> If you know their GitLab aliases, use @username to keep them
> involved.
## Reviewers
@erxleb87
@jandt-desy
> Who do you want as reviewers of your Blog Post?
## Topic and Content
> Outline what you want to write about.
> Specify the style of your post (e.g. report, user story, guide, etc.).
## Target Audience
> Who is your blog post aimed at?
> Should these people have previous knowledge or skills?
## Publishing Date
> When is your preferred date to publish your Blog Post?
> 1. Add the date as text in this section
> 2. Replace <date> in the quick action below with the date to generate an
> automated entry in the GitLab Issue
## Contribution
> How does the content of your Blog Post contribute to the goals of
> HIFIS Software-Services?Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/148Blog Post: SWC@HZDR 2020-03.312020-04-20T08:27:56+02:00Erxleben, Fredof.erxleben@hzdr.deBlog Post: SWC@HZDR 2020-03.31# Blog Post Suggestion
## Authors
* @frust45
* @hueser93
* @erxleb87
* @lokama42
* @steinb95
## Reviewers
Suggested:
* @mdolling-gfz
* @schlauch
## Topic and Content
* **Report** on the proceedings of the SWC@HZDR.
* Explain t...# Blog Post Suggestion
## Authors
* @frust45
* @hueser93
* @erxleb87
* @lokama42
* @steinb95
## Reviewers
Suggested:
* @mdolling-gfz
* @schlauch
## Topic and Content
* **Report** on the proceedings of the SWC@HZDR.
* Explain the circumstances and applied technology and methods
* Evaluate the effectiveness of said methods and techniques
* Highlight issues and their causes
* Highlight what went well
* Include the evaluation of pre- and post-workshop survey
## Target Audience
Other instructors planning to hold workshops, looking for ideas, similarities and differences.
## Publishing Date
2020-04-30
## Contribution
The post will help other HIFIS instructors by conveying lessons learned on methods and technical environments, helping them to improve their own workshops.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.de2020-04-30https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/101Blogpost: Announcement of Helmholtz Software Guideline2020-02-03T11:29:41+01:00Erxleben, Fredof.erxleben@hzdr.deBlogpost: Announcement of Helmholtz Software Guideline# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@erxleb87
## Topic and Content
* Announce the finalization of the software guideline and recommend its usage
* Briefly summarize its content, benefits and impact on future s...# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@erxleb87
## Topic and Content
* Announce the finalization of the software guideline and recommend its usage
* Briefly summarize its content, benefits and impact on future software projects
* Link to the document
([https://doi.org/10.2312/os.helmholtz.007](https://doi.org/10.2312/os.helmholtz.007))
(Only German version available for now)
## Target Audience
* Helmholtz employees who areā¦
* Setting up new software projects
* Migrating software projects to be compliant with the new guidelines
* Helmholtz research centers, that want to install a local policy basing on the template.
## Publishing Date
17. January 2020
## Contribution
By spreading knowledge about the software guideline, the initial quality of future software projects adhering to the guideline will be increased.Huste, TobiasHuste, Tobias2020-01-23https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/88Add blog post about SWC@GFZ2020-01-29T16:21:55+01:00mdolling-gfzAdd blog post about SWC@GFZ# Blog Post Suggestion
## Authors
* @mdolling-gfz
## Reviewers
* @bezaye (if not author)
## Topic and Content
* Experience report from the SWC@GFZ (11/2019)
## Target Audience
* Potential carpentries stakeholders (instructors,...# Blog Post Suggestion
## Authors
* @mdolling-gfz
## Reviewers
* @bezaye (if not author)
## Topic and Content
* Experience report from the SWC@GFZ (11/2019)
## Target Audience
* Potential carpentries stakeholders (instructors, helpers, attendees)
* No additional requirements
## Publishing Date
* As soon as possible
## Contribution
* Other carpentries organizers/instructors/helpers can learn from it
* Possible future attendees can take a look at the carpentriesmdolling-gfzmdolling-gfz2019-12-13https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/102Blogpost: Contributing in 4 Simple Steps2020-01-09T16:41:29+01:00Erxleben, Fredof.erxleben@hzdr.deBlogpost: Contributing in 4 Simple Steps# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
* @hueser93
* @frust45
## Topic and Content
Write a short manual to achieve blog post contributions without having to use _git_ manually.
Rely on the _gitlab_ WebUI instea...# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
* @hueser93
* @frust45
## Topic and Content
Write a short manual to achieve blog post contributions without having to use _git_ manually.
Rely on the _gitlab_ WebUI instead and guide the interested contributors by providing pictures where to click.
(Note that this may require additional interaction from the core team with regards to formatting)
## Target Audience
Interested contributors with little time and no prior knowledge in any of the systems used by us.
## Publishing Date
17. January 2020
## Contribution
Extend the pool of possible contributors by lowering the entrance hurdles for blog posts.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.de2020-01-17https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/90Blog post suggestion: Welcome to HIFIS Software2019-12-20T09:52:05+01:00Huste, TobiasBlog post suggestion: Welcome to HIFIS Software# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@schlauch or @katrinleinweber
## Topic and Content
The topic of this blog post is planned to be *Welcome to HIFIS Software*. It is planned to briefly describe what our plans...# Blog Post Suggestion
## Authors
@frust45
## Reviewers
@schlauch or @katrinleinweber
## Topic and Content
The topic of this blog post is planned to be *Welcome to HIFIS Software*. It is planned to briefly describe what our plans with this website are, what HIFIS Software is about and how the website is structured. It is also planned to briefly describe how the website is implemented and to emphasize that everyone can contribute.
## Target Audience
All people that visit software.hifis.net for the first time and want to briefly inform themselves about us.
## Publishing Date
Week 51, 2019
## Contribution
It helps people to quickly introduce themselves about HIFIS Software and especially software.hifis.net.Huste, TobiasHuste, Tobias2019-12-20