... | ... | @@ -2,15 +2,15 @@ This wiki page contains coding guidelines that all developers must follow as sta |
|
|
|
|
|
# Objectives
|
|
|
## ```Collaboration```
|
|
|
- Make your work easy to understand and share among members of the ADIOS2 community
|
|
|
- Allocate more time for path-finding new functionality and performance improvements rather than understanding developers' coding styles
|
|
|
- Expand developers and users base by building a standardized and attractive infrastructure
|
|
|
- Make your work easy to understand and share among members of the ADIOS2 community
|
|
|
- Allocate more time for path-finding new functionality and performance improvements rather than understanding developers' coding styles
|
|
|
- Expand developers and users base by building a standardized and attractive infrastructure
|
|
|
|
|
|
## ```Execution```
|
|
|
- Translate new research ideas into production by reusing features already in the C++11 standard or in the ADIOS2 infrastructure
|
|
|
- Translate new research ideas into production by reusing features already in the C++11 standard or in the ADIOS2 infrastructure
|
|
|
|
|
|
## ```Quality```
|
|
|
- Improve the quality of the final software product: reduce potential security risks (segmentation faults, memory leaks and overflows)
|
|
|
- Improve the quality of the final software product: reduce potential security risks (segmentation faults, memory leaks and overflows)
|
|
|
|
|
|
|
|
|
# Contents
|
... | ... | |