https://dokuwiki.hampel-soft.com/ 2026-10-11T16:37:21+00:00 https://dokuwiki.hampel-soft.com/ https://dokuwiki.hampel-soft.com/lib/tpl/dokuwiki/images/favicon.ico text/html 2025-05-23T08:46:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/contributing?rev=1747989961&do=diff 23 Contributing File Further information can be found on the Open Source Guides website. Contributing to HSE's OS Projects Each of our open-source project repositories will contain a CONTRIBUTING.md file detailing our contribution guides and rules: Example CONTRIBUTING.md text/html 2024-08-19T22:52:49+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/dependency-structure?rev=1724107969&do=diff 12 Dependency Structure How do we maintain dependencies in general? We like having our dependencies living inside the project directory. As much as possible. First reason is to be able to have different versions “installed” for different projects on one machine. text/html 2026-09-01T08:43:43+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/deployment-structure?rev=1788252223&do=diff 16 Deployment Structure This page uses the following examples/placeholders: <myApp>: Name of the application, eg “TEMPLATE”<Company>: Name of company as used in the file system (ie folder names), eg “HSE”<repoRoot>: Path of the repository root. text/html 2023-08-18T11:15:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/documentation-structure?rev=1692357312&do=diff 14 Documentation Structure Tbd. See also Documentation. Inside the repository README file/documentation folder Outside the repository Releases page (contains PDF of generated documentation)Dokuwiki text/html 2024-05-23T15:35:09+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/dqmh?rev=1716478509&do=diff 32 DQMH More information on DQMH can be found in our knowledge base: Delacor Queued Message Handler Over the last few years, we not only used DQMH very heavily, we also started building additional features around the DQMH core: General HSE Flavour: Description of HSE-specific modifications and additions to the DQMH Framework. text/html 2025-09-04T17:09:16+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/hse-reuse?rev=1757005756&do=diff 31 HSE Reuse Collection The HSE Way of Working includes, among many other things, a collection of reuse code that we base most of our projects on. That ecosystem of tools and libraries allows us to streamline development and adhere to a high quality standard. text/html 2025-07-10T12:18:15+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/license?rev=1752149895&do=diff 22 License File If applicable, defines the legal usecase of the code in any given repository. Further information can be found on the Open Source Guides website. Open-Source Projects For our libraries, an example file would look like this: " Copyright © 2017-2025, Hampel Software Engineering All rights reserved. text/html 2025-08-06T15:24:32+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/project-structure?rev=1754493872&do=diff 11 Project Structure This page defines the default project structure used by most of our projects. We have also information on our default repo structure and our overall software structure. Screenshots are included from an example repository for demonstrative purposes. Throughout this page, we will use text/html 2026-08-17T07:37:37+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/readme?rev=1786952257&do=diff 21 README File Proper documentation is vital for open-source projects, and in addition is also useful for virtually any commercial project too. A README file constitutes a big part of documentation, as this is the first file an end-user sees and should be clear, concise, comprehensive and maybe also a bit fun. text/html 2026-06-08T12:29:07+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/repository-structure?rev=1780921747&do=diff 10 Repo Structure Our projects are hosted on the HSE GitLab Server. This page defines the default repository structure used by these projects. Repository names are always lower-case! /Documentation /DocGen // RAT-generated documentation requirements.xlsx // requirements document /PPL // PPLs the project code depends on /Resources // Various stuff, like icons /<%project_directory%> //… text/html 2026-06-08T13:45:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/resources-structure?rev=1780926313&do=diff 15 Resources The /Resources folder contains data that is relevant for the project or repository but does not fit into any other categories (ie no source code, tests, documentation...). Graphics The following image files are expected in the /Resources folder: text/html 2026-05-08T20:16:44+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/support?rev=1778271404&do=diff 02 Support GitLab For any of our projects, the repository will be hosted on HSE's GitLab server at <https://code.hampel-soft.com>. You can browse existing or create new issues right in the corresponding project's Issue Tracker. Discord If you want to lead a more immediate, synchronous discussion, feel free to join our Discord server at text/html 2023-05-12T06:59:01+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/unittest-structure?rev=1683874741&do=diff 13 Unit Test Structure In general, we strive to make unit tests and work in a test driven way. But dependent on the project, the customer and the circumstances we don't force unit testing, we force the pragmatic approach. Find out more, how we test at HSE. From all the unit testing frameworks, we decided to use text/html 2026-08-26T12:06:12+00:00 Anonymous (anonymous@undisclosed.example.com) https://dokuwiki.hampel-soft.com/code/common/vulnerability-tracking?rev=1787745972&do=diff 01 Vulnerability Tracking Before submitting vulnerability information here, please read our vulnerability disclosure policy (VDP) below. We accept emails at <security@hampel-soft.com> and can engage in back-and-forth conversation there. When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.