software.hifis.net issueshttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues2021-02-05T11:43:42+01:00https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/207Missing workshop in Events Atom feed2021-02-05T11:43:42+01:00Norman ZiegnerMissing workshop in Events Atom feedAm I wrong or is the upcoming [Git/Gitlab workshop](https://software.hifis.net/events/2021/02/18/git-gitlab-introduction) missing in the [Events Atom feed](https://software.hifis.net/feed/events.xml)? At least I got no notification about...Am I wrong or is the upcoming [Git/Gitlab workshop](https://software.hifis.net/events/2021/02/18/git-gitlab-introduction) missing in the [Events Atom feed](https://software.hifis.net/feed/events.xml)? At least I got no notification about it.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/205Revisit if the citation page is back online2021-01-20T09:21:25+01:00Huste, TobiasRevisit if the citation page is back onlineOn the education and training page we referenced https://research-software.org/citation/ which is not working any longer. Also the possible replacement https://cite.research-software.org/ seems to be in maintenance mode for quite a coupl...On the education and training page we referenced https://research-software.org/citation/ which is not working any longer. Also the possible replacement https://cite.research-software.org/ seems to be in maintenance mode for quite a couple of weeks now.
This issue is here to see, if the original link is functional again.
Related to !3512021-03-31https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/202Blog post S/MIME Signing Git Commits: issue with multiple secret keys2020-12-10T15:51:16+01:00Rolf KrahlBlog post S/MIME Signing Git Commits: issue with multiple secret keysIn the blog post [S/MIME Signing Git Commits](https://software.hifis.net/tutorial/2020/04/15/smime-signing-git-commits), the Linux instructions uses in step 4 the following command to identify the signing key:
```sh
$ export SIGNINGKEY=$...In the blog post [S/MIME Signing Git Commits](https://software.hifis.net/tutorial/2020/04/15/smime-signing-git-commits), the Linux instructions uses in step 4 the following command to identify the signing key:
```sh
$ export SIGNINGKEY=$( gpgsm --list-secret-keys | egrep '(key usage|ID)' | grep -B 1 digitalSignature | awk '/ID/ {print $2}' )
```
This will not work if the user has more then one secret key (which likely happens if you once renewed your certificate):
```sh
$ gpgsm --list-secret-keys
/home/rolf/.gnupg/pubring.kbx
-----------------------------
ID: 0xDF6DDC05
S/N: 1E6C42F5E384FC9B8197857E
Issuer: /CN=DFN-Verein Global Issuing CA/OU=DFN-PKI/O=Verein zur Foerderung eines Deutschen Forschungsnetzes e. V./C=DE
Subject: /CN=Rolf Krahl/O=Helmholtz-Zentrum Berlin fuer Materialien und Energie GmbH/C=DE
aka: rolf.krahl@helmholtz-berlin.de
validity: 2018-01-03 11:58:30 through 2021-01-02 11:58:30
key type: 2048 bit RSA
key usage: digitalSignature nonRepudiation keyEncipherment
ext key usage: clientAuth (suggested), emailProtection (suggested)
policies: 1.3.6.1.4.1.22177.300.1.1.4:N:,1.3.6.1.4.1.22177.300.1.1.4.3.6:N:,1.3.6.1.4.1.22177.300.2.1.4.3.6:N:
fingerprint: 5D:2B:54:8C:CA:6A:43:D6:75:79:43:C2:B8:8F:11:03:DF:6D:DC:05
ID: 0xA42FC09D
S/N: 23F068F9070FCBA36AB7527B
Issuer: /CN=DFN-Verein Global Issuing CA/OU=DFN-PKI/O=Verein zur Foerderung eines Deutschen Forschungsnetzes e. V./C=DE
Subject: /CN=Rolf Krahl/OU=IT-ED/O=Helmholtz-Zentrum Berlin fuer Materialien und Energie GmbH/C=DE
aka: rolf.krahl@helmholtz-berlin.de
validity: 2020-12-09 15:21:15 through 2023-12-09 15:21:15
key type: 2048 bit RSA
key usage: digitalSignature nonRepudiation keyEncipherment
ext key usage: clientAuth (suggested), emailProtection (suggested)
policies: 1.3.6.1.4.1.22177.300.1.1.4:N:,1.3.6.1.4.1.22177.300.1.1.4.8:N:,1.3.6.1.4.1.22177.300.2.1.4.8:N:
fingerprint: 67:DF:0E:47:8B:C3:F0:FB:C6:4F:A4:00:97:86:C1:87:A4:2F:C0:9D
$ SIGNINGKEY=$( gpgsm --list-secret-keys | egrep '(key usage|ID)' | grep -B 1 digitalSignature | awk '/ID/ {print $2}' )
$ echo $SIGNINGKEY
0xDF6DDC05 0xA42FC09D
```
Note the two hashes in the output. If you set this in `user.signingkey`, signing a commit will likely use the wrong key. I'd suggest to inspect the list of keys using
```
$ gpgsm --list-secret-keys | less
```
and select the proper id manually instead.Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/201Background/jumbotron image for docker blog posts is one BIG png2021-05-07T14:36:32+02:00Uwe Jandt (DESY, HIFIS)Background/jumbotron image for docker blog posts is one BIG pngThe background image for all three docker blog posts is a BIG (14 MB) png, even for phone etc and should probably be converted to jpg+rescaled?
* https://gitlab.hzdr.de/hifis/software.hifis.net/-/blob/master/assets/img/jumbotrons/docker...The background image for all three docker blog posts is a BIG (14 MB) png, even for phone etc and should probably be converted to jpg+rescaled?
* https://gitlab.hzdr.de/hifis/software.hifis.net/-/blob/master/assets/img/jumbotrons/docker-cover.pngFrere, Jonathan (FWCC) - 142176Frere, Jonathan (FWCC) - 142176https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/175Extend Contributing.md by link procedure2020-07-13T09:55:10+02:00Erxleben, Fredof.erxleben@hzdr.deExtend Contributing.md by link procedureDocument and clarify when to use `{% link %}` and `{% post_url %}` as opposed to the `{% | relative_url %}` filter.
Put the documentation into the _Contributing.md_Document and clarify when to use `{% link %}` and `{% post_url %}` as opposed to the `{% | relative_url %}` filter.
Put the documentation into the _Contributing.md_Huste, TobiasHuste, Tobiashttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/172Unify image inclusion procedure for blog posts2020-06-22T15:37:09+02:00Erxleben, Fredof.erxleben@hzdr.deUnify image inclusion procedure for blog postsAcross blog posts there are several ways of including images:
* `Link`-filter (will fail the page build if the image is not found)
* `site.directory.images | relative_url`
* `site.directory.images | relative_url | append`
Chose one an...Across blog posts there are several ways of including images:
* `Link`-filter (will fail the page build if the image is not found)
* `site.directory.images | relative_url`
* `site.directory.images | relative_url | append`
Chose one and adapt all the blog posts.
* [ ] Adapt the documentation blog posts as well.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/169Documentation of _data/hifis-team.yml is out of date2020-06-19T13:49:21+02:00Erxleben, Fredof.erxleben@hzdr.deDocumentation of _data/hifis-team.yml is out of dateThe documentation does not provide correct information on how to provide the member location.The documentation does not provide correct information on how to provide the member location.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/157Add calendar for an improved events overview2020-04-16T08:27:04+02:00Huste, TobiasAdd calendar for an improved events overviewIn order to improve the events overview a calendar view might be useful. Such a calendar could be filled from an external `ics` or `CalDAV` resource.
This relates to #156.
One possible option could be to embed a nubes calendar in an if...In order to improve the events overview a calendar view might be useful. Such a calendar could be filled from an external `ics` or `CalDAV` resource.
This relates to #156.
One possible option could be to embed a nubes calendar in an iframe. This requires Nubes to set the `frame-ancestors` content security policy accordingly.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/156regular events2020-08-18T15:42:15+02:00mdolling-gfzregular eventsThere will be regular events at least by the community sub-team.
Currently there is possibility to create regular events and we might need a solution.
It is only needed if there is a certain demand for regular events - currently not real...There will be regular events at least by the community sub-team.
Currently there is possibility to create regular events and we might need a solution.
It is only needed if there is a certain demand for regular events - currently not really.
Current idea:
* separate regular events from single ones
* static page with a list of upcoming regular events
* link between single and regular eventsErxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/146A Template for software.hifis.net team member entry - A PROPOSAL2021-02-28T08:06:08+01:00bezayeA Template for software.hifis.net team member entry - A PROPOSAL@software-hifis-net Please add me as a member.
# Request to add Team Member
>>>
This template is a baseline to define the content of the HIFIS Software services website pages for team representation.
>>>
### Family Name(s)
>>>
...
>>>
#...@software-hifis-net Please add me as a member.
# Request to add Team Member
>>>
This template is a baseline to define the content of the HIFIS Software services website pages for team representation.
>>>
### Family Name(s)
>>>
...
>>>
### First Name(s)
>>>
...
>>>
### Organization
* [ ] AWI
* [ ] DESY
* [ ] DKFZ
* [ ] DLR
* [ ] FZJ
* [ ] GFZ
* [ ] HMGU
* [ ] HZB
* [ ] HZDR
* [ ] KIT
* [x] UFZ
### Position
>>>
Enter your current position here
>>>
### Main Entry
>>>
*This will be the body of a page presenting a team member. It contains "About" section containing brief biography of oneself, "Interests" section listing main topics of expertise and interests, and "Responsibilities within HIFIS Software Cluster" section (mandatory) containing a list of key roles each team member has.*
>>>
##### About
>>>
*Introduce yourself briefly in few sentences. This will be useful for anyone seeing your page to match it with the "Responsibilities within HIFIS Software Cluster" section which is visible within the same page.*
>>>
##### Interests
>>>
*List here your key topics of interests*
* Interest A
* Interest B
* ...
>>>
##### Responsibilities within [HIFIS Software Cluster](https://www.hifis.net/services/software/index_ger.html)
>>>
*List here your responsibilities within HIFIS*
* Responsible for this
* Responsible for that
* ...
>>>
### Contact:
>>>
*Contact for individual team member entry should be the general email address hifis-info@hzdr.de. This will maintain all requests to be sent only to the general email address and not to individuals. This way, requests can be collected and filled without missing any.*
>>>
* [e-mail](hifis-info@hzdr.de)Hueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/136Enable Accessibility Scanning after upgrade to GitLab 12.82020-03-09T09:58:13+01:00Katrin LeinweberEnable Accessibility Scanning after upgrade to GitLab 12.8[GitLab 12.8 introduces Accessibility Scanning](https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/#automated-accessibility-scanning-of-review-apps). I presume we agree that we should generally strife to make the website a...[GitLab 12.8 introduces Accessibility Scanning](https://about.gitlab.com/releases/2020/02/22/gitlab-12-8-released/#automated-accessibility-scanning-of-review-apps). I presume we agree that we should generally strife to make the website as accessible as possible, but I'm not sure about how to do it or what the Jekyll template already provides.
Shall we try it the GitLab way?https://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/119Add Template for Event Categories2020-02-11T12:23:03+01:00Erxleben, Fredof.erxleben@hzdr.deAdd Template for Event CategoriesSome event categories (e.g. carpentries workshops) occur pretty often in events, so it would be a good thing to have some templates that one can just copy/paste to not have to write it all from scratch.Some event categories (e.g. carpentries workshops) occur pretty often in events, so it would be a good thing to have some templates that one can just copy/paste to not have to write it all from scratch.Erxleben, Fredof.erxleben@hzdr.deErxleben, Fredof.erxleben@hzdr.dehttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/108Add an FAQ entry concerning event registration2020-03-11T16:52:43+01:00Huste, TobiasAdd an FAQ entry concerning event registrationI would suggest to add an FAQ entry that explains the registration process as long as we use mail. We could reference such an entry on the event page.
What do you say?I would suggest to add an FAQ entry that explains the registration process as long as we use mail. We could reference such an entry on the event page.
What do you say?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/85Font size in page titles should be scaled down according to title length2020-02-05T16:49:25+01:00Hueser, ChristianFont size in page titles should be scaled down according to title lengthSome titles for blog posts and events can be quite long and consume a lot of space in the header.
We would like to shrink/down scale the font size for titles according to the length of the title.Some titles for blog posts and events can be quite long and consume a lot of space in the header.
We would like to shrink/down scale the font size for titles according to the length of the title.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/78Pagination for content of blog post2020-06-22T16:06:26+02:00Huste, TobiasPagination for content of blog postIt might be useful to use pagination also for the content of blog posts.
This issue is here to remember the idea and to discuss it.It might be useful to use pagination also for the content of blog posts.
This issue is here to remember the idea and to discuss it.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/74Brainstorming on content of Technology section on Services page2020-05-11T15:56:28+02:00Hueser, ChristianBrainstorming on content of Technology section on Services pageTechnology section on Services page need some creative input.
Please contribute with your ideas, everyone.
Some general questions are (these go beyond the content for section Technology on the Services page but pave the path for precise...Technology section on Services page need some creative input.
Please contribute with your ideas, everyone.
Some general questions are (these go beyond the content for section Technology on the Services page but pave the path for precise content for the Services page):
* What is service Technology offering to scientists doing open science?
* How does service Technology assist scientists in their work?
* How does service Technology contribute to HIFIS?
* Which tools/platforms/technology services do we want to offer?
* What is to be done, which prototypes need to be developed and when is it ready for use?
* What do we intend to have developed and finished in one years, two years, etc. time?
* How could a rough phase-oriented milestone-roadmap look like and how to subdivide it into iterations/increments adaptable in a dynamic development process?
* How do we articulate the overall system landscape and what is the big picture?
* Which systems to integrate with each other?
* Which systems need to interoperate via open standards?
* How to collect, categorize, prioritize and rank Use Cases / User Stories / requirements from end-users?
* How to get feedback on functional requirements like functionalities, features and user-interfaces and non-functional requirements like usability, scalability, interoperability/integrability, security and performance for prototypes to be developed?
* What do we need in terms of hardware and third-party software tools for our Technology services?
* What do other Software Services / Platforms / Tools offer and how to integrate / interoperate with them?
* Which already existing Open-Source Software Services / Platforms / Tools serve our purposes in HIFIS and to which shall we contribute?
* Which already existing Open-Source Software Services / Platforms / Tools can be forked and adapted to the needs of HIFIS Software?
* There is more to come ...
Provide your ideas in a list or table or put it in a diagram like UML/SysML, BPMN, mind-map, system-landscape map, etc., if it serves your purpose.PermanentHueser, ChristianHueser, Christianhttps://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/72Visualise event registration status2020-01-29T15:52:58+01:00Katrin LeinweberVisualise event registration status@mdolling-gfz's idea, see https://gitlab.hzdr.de/hifis/software.hifis.net/issues/70#note_22697
Interested learners currently need to visit the individual event's page to learn whether they can still sign up or not. We could implement so...@mdolling-gfz's idea, see https://gitlab.hzdr.de/hifis/software.hifis.net/issues/70#note_22697
Interested learners currently need to visit the individual event's page to learn whether they can still sign up or not. We could implement some kind of flag to show the event status, like "open", "wait list", "over", etc. so that they immediately where they can still register.
Alternatively, we could hide any non-open events, grey their entry out or move them to an archive area, to avoid _adding_ a visual hint, but still making it clear which events they no longer need to hope for.https://codebase.helmholtz.cloud/hifis/software.hifis.net/-/issues/66Recude quality in image variant creation2020-02-05T16:49:36+01:00Huste, TobiasRecude quality in image variant creationCurrently, we create variant image sizes with the script available in the `scripts/` directory. This works pretty fine.
I suggest to reduce the quality level, in order to further reduce the size of images that need to be loaded. I can't...Currently, we create variant image sizes with the script available in the `scripts/` directory. This works pretty fine.
I suggest to reduce the quality level, in order to further reduce the size of images that need to be loaded. I can't see a real difference, but the image size was more than halved for some examples. Something along this way:
```diff
diff --git a/scripts/create_jumbotron_variants.sh b/scripts/create_jumbotron_variants.sh
index b24b7d6..3df4855 100755
--- a/scripts/create_jumbotron_variants.sh
+++ b/scripts/create_jumbotron_variants.sh
@@ -84,12 +84,12 @@ do
else
# Create new version for this breakpoint
echo "Generating $target_file ($target_width px)"
- convert "$source_file" -resize "$target_width" "$target_file"
+ convert "$source_file" -resize "$target_width" -quality 50 "$target_file"
fi
else
- # Instead of upscaling, create a relative link to the original
- echo "Creating link $target_file (Source smaller then target)"
- ln -sr "$source_file" "$target_file"
+ # Instead of upscaling, only reduce quality
+ echo "Reducing quality of $target_file"
+ convert "$source_file" -quality 50 "$target_file"
fi
done
done
```
@hueser93 @erxleb87 What do you say?