The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI DMSU"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
{{TOC_right}} | {{TOC_right}} | ||
The DMSU | The purpose of DMSU work is twofold: to find solution to middleware-related problems | ||
problems which ''do not'' require changes | |||
in code, documentation, ... (whatever is released by the TP), | |||
and to provide thorough analysis, yielding well-specified bug report | |||
otherwise. | |||
DMSU also carries sufficient expertise to provide emergency fixes to middleware | |||
problems in the unlikely case the TP fails to deliver, for whatever reason. | |||
<!-- | <!-- | ||
NOTE: Categorisation of pages is done automatically by including the menubars, so no categorisation necessary here! | NOTE: Categorisation of pages is done automatically by including the menubars, so no categorisation necessary here! | ||
--> | --> | ||
Revision as of 16:26, 19 March 2012
| Technology | Software Component Delivery | Software Provisioning | UMD Middleware | Cloud Middleware Distribution | Containers Distribution | Technology Glossary |
| DMSU | | Interactions | | Ticket priorities | | Ticked followup | | Documentation | | Internals | | Glossary |
The purpose of DMSU work is twofold: to find solution to middleware-related problems
problems which do not require changes
in code, documentation, ... (whatever is released by the TP),
and to provide thorough analysis, yielding well-specified bug report
otherwise.
DMSU also carries sufficient expertise to provide emergency fixes to middleware problems in the unlikely case the TP fails to deliver, for whatever reason.