software.hifis.net issueshttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues2020-02-03T11:29:41+01:00https://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/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/199Team information Kalali2020-11-30T17:28:59+01:00Amir KalaliTeam information KalaliAs stated in #130 I am not represented as a member on the website.\
My profile will be added by myself with the corresponding merge request.As stated in #130 I am not represented as a member on the website.\
My profile will be added by myself with the corresponding merge request.Amir KalaliAmir Kalalihttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/193Rephrase text of consulting page to address increased requests2020-11-03T14:13:06+01:00Martin Stoffersmartin.stoffers@dlr.deRephrase text of consulting page to address increased requestsIn our [meeting](https://pad.gwdg.de/eFGLKVLYTACM3xTweorNfg?both#) on the 15th of October we decided to address the increased consulting requests by rephrasing the introduction of the [consulting page](https://software.hifis.net/services...In our [meeting](https://pad.gwdg.de/eFGLKVLYTACM3xTweorNfg?both#) on the 15th of October we decided to address the increased consulting requests by rephrasing the introduction of the [consulting page](https://software.hifis.net/services/consulting).
The following text shall serve as initial draft.
> We are a small team and want to reach as many researcher/groups as possible. <INSERT?: We can offer support in form of answering questions or implementation work (except feature development) of up to a maximum of one or two weeks.> Depending on the request type the processing can take a bit longer. We try to setup an initial meeting as early as possible.Martin Stoffersmartin.stoffers@dlr.deMartin Stoffersmartin.stoffers@dlr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/188Job Failed #1696002020-09-22T14:45:29+02:00Frere, Jonathan (FWCC) - 142176Job Failed #169600Job [#169600](https://gitlab.hzdr.de/hifis/software.hifis.net/-/jobs/169600) failed for ad1381fb2d27859abaf18270efd38772ad17f456:
From @bezaye:
> Regarding the event pages, the computing center changed the gitlab pages to redirect to h...Job [#169600](https://gitlab.hzdr.de/hifis/software.hifis.net/-/jobs/169600) failed for ad1381fb2d27859abaf18270efd38772ad17f456:
From @bezaye:
> Regarding the event pages, the computing center changed the gitlab pages to redirect to https. So its a url change (this workshttps://swc-bb.gitext-pages.gfz-potsdam.de/swc-pages/2020-06-22-virtual/).Frere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/186Introducing Consulting URL is incorrect2020-09-07T09:58:35+02:00Frere, Jonathan (FWCC) - 142176Introducing Consulting URL is incorrectintroducting -> introducing
* Rename page
* Setup redirectintroducting -> introducing
* Rename page
* Setup redirectFrere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/180event registration information grouping2020-08-27T11:25:24+02:00bezayeevent registration information groupingTo post an event, the section that allow us to [add registration information](https://gitlab.hzdr.de/hifis/software.hifis.net/-/blob/master/_includes/events/event_registration_text.html) groups all registration variables in a single *if ...To post an event, the section that allow us to [add registration information](https://gitlab.hzdr.de/hifis/software.hifis.net/-/blob/master/_includes/events/event_registration_text.html) groups all registration variables in a single *if clause* using AND. This makes the possibility of displaying for example a registration link and leave out the remaining registration links difficult and also results in unwanted default text to be displayed
- A base-line suggestion: *take out registration link as a separate option*
- since there are events we might need to announce that are hosted some where else(e.g. conferences we organize with other RSEs) and we only need to put a registration link and don't need to keep track of waiting list, or check if the event is booked out (which for the case of conferences I don't see this might be used), or unable to get registration period if the event has dynamic scheduling and is recurrent.Hueser, ChristianHueser, Christianhttps://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/134Blog RSS feed2020-03-04T10:59:26+01:00Lars BilkeBlog RSS feedPlease add a RSS feed to the blog. Thanks!Please add a RSS feed to the blog. Thanks!Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/128Profile/Timeline of build pipelines2020-02-27T07:46:41+01:00Guido JuckelandProfile/Timeline of build pipelinesAfter yesterdays edit to an event and the following hotfix, I had the subjective feeling that the regeneration of the webpages via the current CI/CD means takes quite some time (about 30 minutes). I would like to understand where this co...After yesterdays edit to an event and the following hotfix, I had the subjective feeling that the regeneration of the webpages via the current CI/CD means takes quite some time (about 30 minutes). I would like to understand where this comes from and propose to generate a trace of the involved pipelines. This could then also be used for training purposes to build the correct expectation for the audience on how long CI-tests take.
For the presentation, I would suggest a typical timeline view.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/125Handle events and posts which have been renamed after public announcement2020-02-26T10:45:06+01:00Hueser, ChristianHandle events and posts which have been renamed after public announcementWe need to consider cases in which filenames will be renamed after they have been announced publicly.
Permalinks can be used to fix the gap short-term.
The solution are redirects, making the old and the new URL valid.We need to consider cases in which filenames will be renamed after they have been announced publicly.
Permalinks can be used to fix the gap short-term.
The solution are redirects, making the old and the new URL valid.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/118Show "TBD/TBA" locations to enable early, "save the date"-like announcements2020-01-31T12:51:12+01:00Katrin LeinweberShow "TBD/TBA" locations to enable early, "save the date"-like announcementsCan we modify [event_digest.html](https://gitlab.hzdr.de/hifis/software.hifis.net/blob/6d8c92f088df9359f1119509922b5a519f3a5c26/_includes/event_digest.html#L56-62) so that it falls back to whichever free-text the event organizer added af...Can we modify [event_digest.html](https://gitlab.hzdr.de/hifis/software.hifis.net/blob/6d8c92f088df9359f1119509922b5a519f3a5c26/_includes/event_digest.html#L56-62) so that it falls back to whichever free-text the event organizer added after the `campus:` field, in case the [campii](https://gitlab.hzdr.de/hifis/software.hifis.net/blob/6d8c92f088df9359f1119509922b5a519f3a5c26/_data/helmholtz-centers.yml) still needs to be decided? The code for `lecturer` seems to do that, but @schlauch & me weren't sure how to adapt that templating code.
Alternatively, a `TBD` campus could be added, however, sometimes at least the city or region can be added, like DLR would like to do in !159, !163 & !164. For example, the latter's result like this would be helpful to learners already:
![image](/uploads/cbf31430c29f49307c372a43d16850ef/image.png)Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/111Announce 9. & 10. June 2020 workshop2020-02-10T10:00:27+01:00Katrin LeinweberAnnounce 9. & 10. June 2020 workshop# Request to add an Event Announcement
>>>
This template can be used by people who want to announce an event
related to the HIFIS Software Cluster.
This Issue will be resolved by a merge request adding the event.
>>>
## Required I...# Request to add an Event Announcement
>>>
This template can be used by people who want to announce an event
related to the HIFIS Software Cluster.
This Issue will be resolved by a merge request adding the event.
>>>
## Required Information
### Title
GitLab for Software Development in Teams
### Type
workshop
### Organizers
@katrinleinweber
### Instructors
@katrinleinweber @schlauch + 1x HZDR
### Timeframe
* Start: 2020-06-09, 09:00
* End: 2020-06-10, 17:00
# Location
>>>
Check one. If you are not located on a main campus, please provide the
address of the sub-campus.
>>>
* [ ] AWI
* [ ] DESY
* [ ] DKFZ
* [ ] DLR **(TBD)**
* [ ] FZJ
* [ ] GFZ
* [ ] HIDA **(TBD)**
* [ ] HMGU
* [ ] HZB
* [ ] HZDR
* [ ] KIT
* [ ] UFZ
>>>
Please also fill in the room
>>>
* Room:
### Registration Link
>>>
Provide a link for the registration and a date from when on the
registration is open
>>>
* Registration Link: mailto:hifis-info@hzdr.de?subject=Registration%20for%20%22GitLab%20for%20software%20development%20%20in%20teams%22%20workshop%202020-06-09&body=Dear%20HIFIS%20team,%0D%0A%0D%0AI%27d%20like%20to%20make%20...%20ready%20for%20publication.%0D%0A%0D%0A
### Content Description
>>>
What topic is the workshop about?
Do participants need prior knowledge?
Should something be prepared before participating?
>>>
### Additional Information
>>>
Provide additional information
>>>Katrin LeinweberKatrin Leinweberhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/95Optimize Twitter cards2019-12-20T11:32:37+01:00Huste, TobiasOptimize Twitter cardsOptimize the provided metadata to be able to provide proper Twitter cards. The implementation can be validated using https://cards-dev.twitter.com/validator.Optimize the provided metadata to be able to provide proper Twitter cards. The implementation can be validated using https://cards-dev.twitter.com/validator.Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/86Use GitLab Wiki to add sections about how to add events to HIFIS Software web...2020-01-27T09:04:34+01:00Hueser, ChristianUse GitLab Wiki to add sections about how to add events to HIFIS Software web pageIt seems to be reasonable to use GitLab Wikis for documenting knowledge about how to contribute and extend HIFIS Software webpage.
First entry would be a section about the content of the "Front Matter" for event pages.It seems to be reasonable to use GitLab Wikis for documenting knowledge about how to contribute and extend HIFIS Software webpage.
First entry would be a section about the content of the "Front Matter" for event pages.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/83Ordering of events on events page should be done by event start date2019-12-16T15:18:24+01:00Hueser, ChristianOrdering of events on events page should be done by event start dateDue to the fact that events in the future only appear with flag --future set, we put event publication/creation date as prefix of the event page filename. Therefore, ordering is not properly done. We would like to order events according ...Due to the fact that events in the future only appear with flag --future set, we put event publication/creation date as prefix of the event page filename. Therefore, ordering is not properly done. We would like to order events according to event start date given in the "Front Matter" of the event page.Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/75Style blockquotes2019-12-03T13:14:27+01:00Huste, TobiasStyle blockquotesProvide a styling for a blockquote block (`<blockquote></blockquote>`) in order to lift it visually from the other content.
Example in GitLab:
> This is an important quote.Provide a styling for a blockquote block (`<blockquote></blockquote>`) in order to lift it visually from the other content.
Example in GitLab:
> This is an important quote.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/63Blog Post: Caveats of Programming with Floating Point Numbers2020-02-05T16:42:54+01:00Erxleben, Fredof.erxleben@hzdr.deBlog Post: Caveats of Programming with Floating Point Numbers# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
@o.knodel (Factual correctness)
@hueser93
@frust45
## Topic and Content
* Short introduction into the binary composition of floating point numbers (IEEE 754)
* Special cases of...# Blog Post Suggestion
## Authors
@erxleb87
## Reviewers
@o.knodel (Factual correctness)
@hueser93
@frust45
## Topic and Content
* Short introduction into the binary composition of floating point numbers (IEEE 754)
* Special cases of floating point representation (±0, ±∞, NaN)
* Caveat 1: Numeric instability, Reasons and examples
* Caveat 2: Comparisons and why a fixed Ɛ still is not sufficient
* Caveat 3: Computational Performance Impact
* Possible Alternatives
## Target Audience
* Authors of code with high numerical volatility, e.g.
* Simulations of complex systems
* High-precision calculations
* Performance-critical applications
No special mathematical or technical knowledge is required.
The topic will generally be presented in a programming-language-agnostic way.
Practical examples in a specific language may be given to motivate the reader to try them for themselves.
No complete proofs will be given for mathematical properties to not distract from the topic at hand.
## Publishing Date
December 2019
## Contribution
The post will educate scientists about the pitfalls of a seemingly comfortable solution for problems spanning multiple magnitudes of precision.
It will educate the reader to recognize the impact of these caveats in their own code.
Alternatives will be outlined to be adapted at the readers discretion.
Improvements in reproducibility, performance and stability can be expected if the programmer is aware of the presented topic.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/56Optimize HTMLProofer options2019-10-28T14:14:23+01:00Huste, TobiasOptimize HTMLProofer optionsCurrently, we check, if external links are properly resolved and also expect to have the `.html` extension, which we do not require. Jekyll, as well as our future production setup, as well as GitLab Pages don't require that. Furthermore,...Currently, we check, if external links are properly resolved and also expect to have the `.html` extension, which we do not require. Jekyll, as well as our future production setup, as well as GitLab Pages don't require that. Furthermore, dead links are somehow not properly checked. There are a plenty of dead links, e.g. on the frontpage at the moment, but the pipeline succeeds.
I suggest to run the *htmlproofer* with the following options. Like this, we also don't need to have a local web server running.
```bash
$ bundle exec htmlproofer \
--internal-domains localhost:4000 \
--assume-extension \
public
```
We could also discuss, if we should check for external links in a seperate pipeline, that is only running once a week for example. Otherwise our jobs could fail, only if a dependent service is currently offline.
I will submit a MR in a minute, to see if my assumptions are correct.Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/44Build in Bootstrap2019-10-22T11:26:38+02:00Erxleben, Fredof.erxleben@hzdr.deBuild in BootstrapAdd a Bootstrap SCSS version as dependency.
I hereby reserve any rights to future "told you so"-moments regarding that matter :smiley:Add a Bootstrap SCSS version as dependency.
I hereby reserve any rights to future "told you so"-moments regarding that matter :smiley:Huste, TobiasHuste, Tobias