Differences

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

Link to this comparison view

Next revision		Previous revision
events:workshops:esecfse2013:guidelines [2013/03/29 20:22] – created abergelevents:workshops:esecfse2013:guidelines [2013/03/29 20:25] (current) – abergel
Line 1: Line 1:
-        Guidelines for Packaging AEC Submissions+**Guidelines for Packaging AEC Submissions**
  
 Below we outline guidelines on how to package artifacts for Below we outline guidelines on how to package artifacts for
Line 57: Line 57:
  
 1. A VM (Virtualbox/VMWare) image containing software application 1. A VM (Virtualbox/VMWare) image containing software application
-   already setup in the intended run-time environment (e.g., Mobile +already setup in the intended run-time environment (e.g., Mobile 
-   phone emulator, Real time OS). This is the preferred option: It +phone emulator, Real time OS). This is the preferred option: It 
-   avoids installation and compatibility problems, and provides the +avoids installation and compatibility problems, and provides the 
-   best guarantees for reproducibility of the results by the +best guarantees for reproducibility of the results by the 
-   committee.  Authors using Linux might find the CDE tool to be +committee.  Authors using Linux might find the CDE tool to be 
-   useful for automatically creating a VM image from existing software +useful for automatically creating a VM image from existing software 
-   without needing to manually re-install all dependencies within a +without needing to manually re-install all dependencies within a 
-   VM (http://www.stanford.edu/~pgbovine/cde.html).+VM (http://www.stanford.edu/~pgbovine/cde.html).
  
 2. A binary installable package. We invite the authors to use CDE 2. A binary installable package. We invite the authors to use CDE
-   (Linux) or MSI Installer (Windows) to package the binary +(Linux) or MSI Installer (Windows) to package the binary 
-   application.+application.
  
 3. A live instance running on the Web. 3. A live instance running on the Web.
  
 4. A detailed screen-cast of the tool along with the results, 4. A detailed screen-cast of the tool along with the results,
-   especially if one of the following special cases applies:+especially if one of the following special cases applies:
  
-  - the application needs proprietary/commercial software that is not +4.a)  the application needs proprietary/commercial software that is not easily available or cannot be distributed to the committee; 
-    easily available or cannot be distributed to the committee; +4.b)  the application requires significant computation resources (e.g., > 24 hours of execution time to produce the results);
- +
-  - the application requires significant computation resources (e.g., +
-    > 24 hours of execution time to produce the results);+
  
 5. An installation or update repository for the tool. (e.g., Eclipse 5. An installation or update repository for the tool. (e.g., Eclipse
-   update site or a Debian APT repository). However, we urge the +update site or a Debian APT repository). However, we urge the 
-   authors to test their repository on standard environments to avoid +authors to test their repository on standard environments to avoid 
-   installation problems by the committee members.+installation problems by the committee members.
  
 IN ALL CASES, authors should make a genuine effort to not learn the IN ALL CASES, authors should make a genuine effort to not learn the