Wiki » History » Version 4
Nico Schottelius, 10/17/2018 02:20 PM
1 | 1 | Nico Schottelius | h1. Wiki |
---|---|---|---|
2 | |||
3 | 3 | Nico Schottelius | {{toc}} |
4 | |||
5 | 2 | Nico Schottelius | h2. Status |
6 | |||
7 | This site is **being built** (aka 90's "under construction" style). We are about to move internal documentation to the public and create new services/infrastructure building blocks so that users can easily access them. |
||
8 | |||
9 | h2. Introduction |
||
10 | |||
11 | 1 | Nico Schottelius | Have you ever wanted a feature in a software, product or infrastructure and were angry that the vendor would just not support it? |
12 | |||
13 | We certainly were and for that reason we decided to open up our infrastructure. |
||
14 | |||
15 | 4 | Nico Schottelius | h2. Full disclosure. |
16 | 1 | Nico Schottelius | |
17 | 4 | Nico Schottelius | Our objective is to open up 100% of our infrastructure definition. This includes processes, architecture, technologies, etc. The only missing parts are our secrets, passwords, hashes, etc. |
18 | 1 | Nico Schottelius | |
19 | 4 | Nico Schottelius | |
20 | h2. How do I profit from it? |
||
21 | |||
22 | First of all, if something does not work as expected, you can debug the issue with the existing information. But even better: if you would like to see a feature that combines parts of our infrastructure, you are free to do so! And even better: if you create a clean solution, we might even merge it into our official infrastructure. |
||
23 | |||
24 | h2. How to extend the ungleich infrastructure? |
||
25 | |||
26 | * Create your solution |
||
27 | * Create a ticket with a proposal |
||
28 | * Somebody in our team will review it and |
||
29 | ** if it fits: merge it |
||
30 | ** if it does not fit: discuss with you how to proceed |
||
31 | |||
32 | Easy, isn't it? |