Changes between Version 53 and Version 54 of CodeCampIII

Timestamp:

Feb 27, 2015 5:31:11 PM (9 years ago)

Author:

butler

Comment:

—

CodeCampIII

@@ -46 +46 @@
 Besides addressing feature requests and bug fixes, the first task was to migrate the !SasView code repository from !SourceForge, which has been problematic of late, to Github. This was successfully accomplished. Migration included redirecting host names, editing trac and web pages, moving web pages hosting from UTK to github as well as updating all the developer machines.  In the process the final phase of renaming and reorganizing the folders in the !SasView tree was completed.  The official build servers and Jenkins site were moved to the DMSC servers and the development finally moved from using the old wx 2.8 to using wx 3.0.
 
-The to wx 3.0 enabled the work on documentation begun at Code Camp II, to address the first theme above, to be completed with a porting of all the non-model documentation to RST files that can be built by sphinx. The use of sphinx allows the new documentation was integrated into the GUI as well as be delivered to the web. The opportunity was take to simplify that part of the GUI code in the process. Most of the non-model documentation was also carefully edited and updated.  This restructuring means that both the user documentation, and the developer documentation, (provided in the docstrings included in the code), are automatically generated and can be pushed to the website with each build.   Further simplification is expected when the new model structure discussed below is completed. Thus the task of editing and updating user documentation is now more manageable and should allow for better and more timely upkeep as we move forward.  Meanwhile the ease of access to the developer documentation should encourage better code documentation and starts addressing the second theme of lowering the barrier to entry for new developers.
+The move to wx 3.0 enabled the work on documentation begun at Code Camp II, addressing the first theme above, to be completed with a porting of all the non-model documentation to RST files that can be built by sphinx. The use of sphinx allows the new documentation to be integrated into the GUI as well as be delivered to the web. The opportunity was take to simplify that part of the GUI code in the process. Most of the non-model documentation was also carefully edited and updated.  This restructuring means that both the user documentation, and the developer documentation, (provided in the docstrings included in the code), are automatically generated and can be pushed to the website with each build.   Further simplification is expected when the new model structure discussed below is completed. Thus the task of editing and updating user documentation is now more manageable and should allow for better and more timely upkeep as we move forward.  Meanwhile the ease of access to the developer documentation should encourage better code documentation and starts addressing the second theme of lowering the barrier to entry for new developers.
 
 With respect to that second theme, getting a developer environment properly installed has historically been a huge barrier, both for “amateur” developers lacking experience in installing the plethora of required packages and getting them running together, and for more professional programmers who may have a number of the wrong versions of required packages already installed.  To address both issues as well as others, such as ensuring that new required packages get propagated easily to developers and build machines, the Anaconda scientific python distribution was explored. This looks like a promising solution and significant progress was made in implementing it. 
@@ -63 +63 @@
 The management team is formulating a roadmap document which will be circulated for comment amongst the developers before a public version is released.
 
-The developers will continue to add models to the new sasmodels package and the necessary work to integrate it with the building of !SasView will be performed.
+The developers will continue to migrate models to the new sasmodels package and the necessary work to integrate it with the building of !SasView will be performed.