Difference between revisions of "2013-10-18 Meeting DEVROOM / stepping stone GmbH"

From stoney cloud
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH)
(Transcript)
 
(26 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH =
+
= Transcript of the meeting between DEVROOM / stepping stone GmbH =
  
 
{| border="0" style="border-collapse: collapse;"
 
{| border="0" style="border-collapse: collapse;"
Line 12: Line 12:
  
 
| width="80px"  | '''Time'''
 
| width="80px"  | '''Time'''
| width="800px"  | 10:00 until 15:00
+
| width="800px"  | 10:00 until 18:00
 
|- valign="top"
 
|- valign="top"
  
Line 19: Line 19:
 
| width="800px"  |  
 
| width="800px"  |  
 
* Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
 
* Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
 +
* Tatiana Durisova Eichenberger <tatiana.durisova@stepping-stone.ch>: TEI
 
* Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
 
* Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
  
Line 32: Line 33:
 
| width="80px"  | '''Agenda'''
 
| width="80px"  | '''Agenda'''
 
| width="800px"  |  
 
| width="800px"  |  
 
+
* [[Release Management]]:
# Architecture
+
** We need to define the [[Release_Management#Versioning | versioning]].
## Application Programming Interface (API)
+
** URL in web browser (for the web client) will be defined through stepping stone GmbH, Feedback through CWI, what is easily implemented.
## [[Modularisation]]
+
* Architecture
## [[Testing]]
+
** [[Modularisation]]: How do we want to modularise?
## Documentation
+
** [[Application Programming Interface (API)]]: Review through stepping stone GmbH
# Roadmap in general
+
** [[Testing]]: What and how?
# Roadmap concrete
+
** [[Documentation]]: What and how?
## stoney core (self-care) with provider extension
+
* [[:Category:Roadmap|Roadmap]] in general
## stoney safe (on-line backup) module with customer extension
+
* Next steps:
## next module(s)
+
** [[stoney core: Requirements| stoney core: Requirements]] (self-care) with provider enhancement
 +
** [[stoney backup: Requirements| stoney backup: Requirements]] (on-line backup) module with customer enhancement
 +
** New [[stoney mail: Requirements| stoney mail: Requirements]] (mail with or without group-ware) module
 +
* Possible future roadmap
 +
** New [[stoney vm: Requirements| stoney vm: Requirements]] (subset of stoney conductor) module?
 +
* Surrogate?
 
|-  
 
|-  
  
Line 58: Line 64:
  
 
| width="40px"  | 1
 
| width="40px"  | 1
| width="800px"  |  
+
| width="800px"  | Patches:
| width="70px"  | Info
+
* Source-Code has patches. These are then needed, when we also change object classes, update or modify data.
| width="70px"  | All
+
* Check the optimal solution to roll out these patches between CWI and TMU
| width="70px"  | 2013-10-18
+
* Question: How shall we handle necessary roll-backs (for example if data modifications went wrong).
 +
| width="70px"  | To Do
 +
| width="70px"  | MEI
 +
| width="70px"  | 2013-10-23
 
|-
 
|-
  
 
| width="40px"  | 2
 
| width="40px"  | 2
| width="800px"  |  
+
| width="800px"  | Modularisation:
 +
* Separate Modules into Web and Service
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 72: Line 82:
  
 
| width="40px"  | 3
 
| width="40px"  | 3
| width="800px"  |  
+
| width="800px"  | Release Management
 +
* Is ok, but the difference between stable and unstable must be explained better (Major can be unstable too? No).
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 79: Line 90:
  
 
| width="40px"  | 4
 
| width="40px"  | 4
| width="800px"  |  
+
| 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 stoney backup (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"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 86: Line 103:
  
 
| width="40px"  | 5
 
| width="40px"  | 5
| width="800px"  |  
+
| width="800px"  | Testing
 +
* Will be done as described under [[Testing]].
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 93: Line 111:
  
 
| width="40px"  | 6
 
| width="40px"  | 6
| width="800px"  |  
+
| width="800px"  | Super User
 +
* <code>sstBelongsToUID: 1</code>
 +
Reseller Person (can only belong to one reseller, but to multiple customers and can be employee of the reseller and the customers)
 +
* <code>sstBelongsToResellerUID: 1234567</code>
 +
Customer Person (can only belong to one reseller but to multiple customers and can be employee of these customers)
 +
* <code>sstBelongsToCustomerUID: 1234567</code>
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 100: Line 123:
  
 
| width="40px"  | 7
 
| width="40px"  | 7
| width="800px"  |  
+
| width="800px"  | Person
 +
* Three separate forms
 +
** Super User (can add new Resellers, Modules, make People to Reseller People)
 +
** Reseller (
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 107: Line 133:
  
 
| width="40px"  | 8
 
| width="40px"  | 8
| width="800px"  |  
+
| width="800px"  | Suche
 +
* The results need more information, depending on the level you have logged in. For example
 +
** Provider: Needs the information to which reseller and which customer the person belongs to.
 +
** Reseller: Needs the information to which reseller customer the person belongs to.
 +
** Customer: Knows, the person belongs to the customer.
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 114: Line 144:
  
 
| width="40px"  | 9
 
| width="40px"  | 9
| width="800px"  |  
+
| width="800px"  | Default views after login:
 +
* Provider Person: Product overview page of the provider, where they can also change the settings and defaults of a service/product (global activate/deactivate modules).
 +
* Reseller Person: Product overview page of the reseller, where they can also change the settings and defaults of a service/product (activate/deactivate modules for themselves and therefore for their customers).
 +
* Customer Person: Product overview page of their own services/products.
 +
These views need to be defined.
 +
| width="70px"  | To Do.
 +
| width="70px"  | TEI/MEI
 +
| width="70px"  | 2013-10-25
 +
|-
 +
 
 +
| width="40px"  | 10
 +
| width="800px"  | PDF Creation
 +
* Will ODT work with current offer?
 +
* A possibility would be to exchange PDF creation with the screen redesign.
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 120: Line 163:
 
|-
 
|-
  
| width="40px"  | 10
+
| width="40px"  | 11
| width="800px"  |  
+
| width="800px"  | Roles and rights
 +
* See [[stoney core: Requirements]] brainstorming.
 +
| width="70px"  | Info
 +
| width="70px"  | All
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 12
 +
| width="800px"  | Next steps
 +
* Prioritise the next functionality
 +
* Create Mockups and documentation, including LDIFs
 +
* Create Enhancements in the issue tracker and add to desired version
 +
* Ask for quotation
 +
** Clarify any questions and update Enhancements/Documentation
 +
| width="70px"  | To Do
 +
| width="70px"  | MEI/CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 13
 +
| width="800px"  | Split current selfcare into
 +
* core
 +
* services
 +
| width="70px"  | To Do
 +
| width="70px"  | MEI/CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 14
 +
| width="800px"  | REST API
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 15
 +
| width="800px"  | Different Forms for different users
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 16
 +
| width="800px"  | Line length (table field) restriction via CSS
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 17
 +
| width="800px"  | VM-Manager
 +
* Change Reseller and Customer by adding Person
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 18
 +
| width="800px"  | Priorities
 +
* Core
 +
** Provider View
 +
** API
 +
** Roles?
 +
* VM
 +
* Mail
 +
* Backup Customer View
 +
| width="70px"  | Info
 +
| width="70px"  | All
 +
| width="70px"  | 2013-10-18
 +
|-
 +
 
 +
| width="40px"  | 19
 +
| width="800px"  | Lizenz Abklärungen
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All

Latest revision as of 13:13, 5 May 2014

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 18:00
Participants
  • Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
  • Tatiana Durisova Eichenberger <tatiana.durisova@stepping-stone.ch>: TEI
  • 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

Transcript

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 stoney backup (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 Super User
  • sstBelongsToUID: 1

Reseller Person (can only belong to one reseller, but to multiple customers and can be employee of the reseller and the customers)

  • sstBelongsToResellerUID: 1234567

Customer Person (can only belong to one reseller but to multiple customers and can be employee of these customers)

  • sstBelongsToCustomerUID: 1234567
Info All 2013-10-18
7 Person
  • Three separate forms
    • Super User (can add new Resellers, Modules, make People to Reseller People)
    • Reseller (
Info All 2013-10-18
8 Suche
  • The results need more information, depending on the level you have logged in. For example
    • Provider: Needs the information to which reseller and which customer the person belongs to.
    • Reseller: Needs the information to which reseller customer the person belongs to.
    • Customer: Knows, the person belongs to the customer.
Info All 2013-10-18
9 Default views after login:
  • Provider Person: Product overview page of the provider, where they can also change the settings and defaults of a service/product (global activate/deactivate modules).
  • Reseller Person: Product overview page of the reseller, where they can also change the settings and defaults of a service/product (activate/deactivate modules for themselves and therefore for their customers).
  • Customer Person: Product overview page of their own services/products.

These views need to be defined.

To Do. TEI/MEI 2013-10-25
10 PDF Creation
  • Will ODT work with current offer?
  • A possibility would be to exchange PDF creation with the screen redesign.
Info All 2013-10-18
11 Roles and rights Info All 2013-10-18
12 Next steps
  • Prioritise the next functionality
  • Create Mockups and documentation, including LDIFs
  • Create Enhancements in the issue tracker and add to desired version
  • Ask for quotation
    • Clarify any questions and update Enhancements/Documentation
To Do MEI/CWI 2013-10-18
13 Split current selfcare into
  • core
  • services
To Do MEI/CWI 2013-10-18
14 REST API Info CWI 2013-10-18
15 Different Forms for different users Info CWI 2013-10-18
16 Line length (table field) restriction via CSS Info CWI 2013-10-18
17 VM-Manager
  • Change Reseller and Customer by adding Person
Info CWI 2013-10-18
18 Priorities
  • Core
    • Provider View
    • API
    • Roles?
  • VM
  • Mail
  • Backup Customer View
Info All 2013-10-18
19 Lizenz Abklärungen Info All 2013-10-18