Differences

This shows you the differences between two versions of the page.

--- meeting-2013 [2013/04/23 20:21] – mikael.ohman
+++ meeting-2013 [2014/08/04 19:06] (current) – mikael.ohman
@@ Line 1: / Line 1: @@
 === Maintenance ===
   - Avoiding duplicated information (impossible to keep things up-to-date in the manuals). Good would be to store everything in-code (perhaps with some script scavengers all information from the headers automatically)
-  - Modularity: Having each REGISTER_CLASS() in the respective source file. Code for registering components exists for string-only versions (I'm hoping that classtype versions should rather be removed). Currently works for dynamic linking, but static linking is a problem (static symbols are optimized away). Solution could be to push for dynamic linking.
+  - <del>Modularity: Having each REGISTER_CLASS() in the respective source file. Code for registering components exists for string-only versions (I'm hoping that classtype versions should rather be removed). Currently works for dynamic linking, but static linking is a problem (static symbols are optimized away). Solution could be to push for dynamic linking.</del>
-  - ''classType'' has to go. Replace with strings (Note: ''int DataStream::write(const std::string &data); + read'' already exists!). This effects context files and load balancing.
+  - <del>''classType'' has to go. Replace with strings (Note: ''int DataStream::write(const std::string &data); + read'' already exists!). This effects context files and load balancing.</del>
   - Reduce numbering of engineering models
     - SM-module: Replace ''DEIDynamic'', ''DIIDynamic'', ''NLDEIDynamic'', ''NonLinearDynamic'' with ''Dynamic''
@@ Line 8: / Line 8: @@
   - Automatic tools:
     - More tests (at least 1 for each element type, at least 1 for each material, and 1 for each engineering model).
-    - Coverage testing (static analyzers could help, gcov + ctest is an option but it will miss tons of unstestable, optional but used, code).
+    - <del>Coverage testing (static analyzers could help, gcov + ctest is an option but it will miss tons of unstestable, optional but used, code).</del> Possible to run with ctest now
     - Aiming at zero-warning policy, even with MSVC (some thing that MSVC warns about could be fixed, some could be turned off). Usage of ''-DCMAKE_CXX_COMPILER_FLAG=-Werror'' is recommended. We still produce quite a lot of warnings in Clang and Intels compilers.
@@ Line 26: / Line 26: @@
 === Sets ===
-  - Mikael will be adding sets (boundary/edge/surface sets and bulk sets to start with)
+  - <del>Mikael will be adding sets (boundary/edge/surface sets and bulk sets to start with)</del>
-  - Active boundary conditions will use sets instead of storing their own list of elements.
+  - <del>Active boundary conditions will use sets instead of storing their own list of elements.</del>
-  - See where to go from there (perhaps it's possible to keep backwards compability)
+  - <del>See where to go from there (perhaps it's possible to keep backwards compability)</del>
 === License ===
-  - Keep GPL - Might cut of commercial interest that could be benefitial
+  - <del>Keep GPL - Might cut of commercial interest that could be benefitial</del>
-  - Switch to LGPL - Commercial might pay developers to extend OOFEM to include new elements, materials, contact models, etc.
+  - <del>Switch to LGPL - Commercial might pay developers to extend OOFEM to include new elements, materials, contact models, etc.</del> This option has been applied
-  - Offer separate commercial license - We would probably require a copyright assignment agreement for contributions to work with this. Seems unlikely to happen.
+  - <del>Offer separate commercial license - We would probably require a copyright assignment agreement for contributions to work with this. Seems unlikely to happen.</del>