[unchecked revision]

Revision as of 11:26, 18 October 2013

Transcript of the meeting between DEVROOM / stepping stone GmbH

Location	DEVROOM, Haseneystr. 16, 81377 Munich, Germany
Date	Friday, the 18th of October 2013
Time	10:00 until 15:00
Participants	Christian Wittkowski <christian.wittkowski@devroom.de>: CWI Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
Non participants	Christian Affolter <christian.affolter@stepping-stone.ch>: CAF Pat Kläy <pat.klaey@stepping-stone.ch>: PKL Tiziano Müller <tiziano.mueller@stepping-stone.ch>: TMU
Agenda	Release Management: We need to define the versioning. URL in web browser (for the web client) will be defined through stepping stone GmbH, Feedback through CWI, what is easily implemented. Architecture Modularisation: How do we want to modularise? Application Programming Interface (API): Review through stepping stone GmbH Testing: What and how? Documentation: What and how? Roadmap in general Next steps: stoney core: Requirements (self-care) with provider enhancement stoney safe: Requirements (on-line backup) module with customer enhancement New stoney mail: Requirements (mail with or without group-ware) module Possible future roadmap New stoney vm: Requirements (subset of stoney conductor) module? Surrogate?

No.	Text	What?	Who?	When?
1	Patches: Source-Code has patches. These are then needed, when we also change object classes, update or modify data. Check the optimal solution to roll out these patches between CWI and TMU Question: How shall we handle necessary roll-backs (for example if data modifications went wrong).	To Do	MEI	2013-10-23
2	Modularisation: Separate Modules into Web and Service	Info	All	2013-10-18
3	Release Management Is ok, but the difference between stable and unstable must be explained better (Major can be unstable too? No).	Info	All	2013-10-18
4	API Requires more information about the minimum amount of need calls and what is expected. First step is the API for stoney core Second step is the API for stone safe (on-line backup) Third step ist the API for stoney mail RestfullYii or on GitHub: RestfullYii makes a good impression on CWI. Communication between JavaScript (Client) and Yii-Framework (Server) need some thoughts from CWI.	Info	All	2013-10-18
5	Testing Will be done as described under Testing.	Info	All	2013-10-18
6		Info	All	2013-10-18
7		Info	All	2013-10-18
8		Info	All	2013-10-18
9		Info	All	2013-10-18
10		Info	All	2013-10-18

@@ Line 90: / Line 90: @@
 | width="40px"   | 4
 | width="800px"  | API
-*
+* Requires more information about the minimum amount of need calls and what is expected.
+* First step is the API for stoney core
+* Second step is the API for stone safe (on-line backup)
+* Third step ist the API for stoney mail
+* [http://www.yiiframework.com/extension/restfullyii/ RestfullYii] or on GitHub: [https://github.com/evan108108/RESTFullYii RestfullYii] makes a good impression on CWI.
+* Communication between JavaScript (Client) and Yii-Framework (Server) need some thoughts from CWI.
 | width="70px"   | Info
 | width="70px"   | All
@@ Line 98: / Line 103: @@
 | width="40px"   | 5
 | width="800px"  | Testing
-*
+* Will be done as described under [[Testing]].
 | width="70px"   | Info
 | width="70px"   | All