PubMan Meeting Open Source Strategy

MPDL

=Installer=
 * Keep old installers or create new zip packages?


 * ZIP package includes
 * WildFly 8.1
 * Pre-configured standalone.xml
 * module with required property files (pubman.properties, cone.properties etc) for localhost access
 * pubman.ear
 * JBoss 4.2.3
 * Pre-configured for eSciDoc and fedora
 * required properties (escidoc-core.properties etc.)
 * escidoc-core.ear, fedora.war, AdminTool.war
 * Scripts/Java JAR
 * eSciDoc DB
 * fedora DB
 * CoNE DB
 * Initial Dataset (Organizational Units, Content Model, Contexts, Users, example items)
 * do they have to be created via REST API or can they be part of the ZIP-Package & DB-Script?
 * If not, id values might have to be added to property files
 * Start script for both servers?


 * Better documentation of property files

=Code versioning/Code repository?=
 * SVN vs GIT/GitHub


 * Github preferred, start after PubMan Release beginning 2015

=Code Structure=
 * One additional super POM for pubman & common_services?
 * ... or all submodules of pubman & common_services under one super POM?
 * Both require changes of code directory structure / SVN
 * Add libraries to super pom dependencies (e.g. log4j) or to super pom dependency management (e.g. javaee-api)

=Development Environment=
 * Virtual Machine including an Eclipse IDE with pubman / common services / escidoc