Difference between revisions of "2013-11-27 Telephone Conference DEVROOM / stepping stone GmbH"

From stoney cloud
Jump to: navigation, search
[unchecked revision][unchecked revision]
(Transcript)
(Transcript)
Line 98: Line 98:
  
 
| width="40px"  | 5
 
| width="40px"  | 5
 +
| width="800px"  | Development:
 +
* Please check in all code daily (more often is allowed).
 +
* The code does not need to function, it is important, that it is there and can be reviewed.
 +
| width="70px"  | Info
 +
| width="70px"  | All
 +
| width="70px"  | 2013-11-27
 +
|-
 +
 +
| width="40px"  | 6
 
| width="800px"  |  
 
| width="800px"  |  
 
| width="70px"  | Info
 
| width="70px"  | Info
Line 103: Line 112:
 
| width="70px"  | 2013-11-27
 
| width="70px"  | 2013-11-27
 
|-
 
|-
 +
  
 
|}
 
|}
  
 
[[Category:2013]]
 
[[Category:2013]]

Revision as of 15:07, 27 November 2013

Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH

Location Skype
Date Wednesday, the 27th of November 2013
Time 14:00 until 15:00
Participants
  • Christian Wittkowski <christian.wittkowski@devroom.de>: CWI
  • Christian Affolter <christian.affolter@stepping-stone.ch>: CAF
  • Tiziano Müller <tiziano.mueller@stepping-stone.ch>: TMU
  • Michael Eichenberger <michael.eichenberger@stepping-stone.ch>: MEI (Transcript)
Non participants
  • Pat Kläy <pat.klaey@stepping-stone.ch>: PKL
  • Christoph Scheurer <christoph.scheurer@stepping-stone.ch>: CSC
  • David Vollmer <david.vollmer@stepping-stone.ch>: DVO
  • Pascal Jufer <pascal.jufer@stepping-stone.ch>: PJU
Agenda

Transcript

No. Text What? Who? When?
1 We have decided on our own development. To Do CWI 2013-11-27
2 We'll update the Application Programming Interface (API) and mark the mandatory requirements.
  • The documentation will be split into multiple documents.
  • We'll finalize the specification until Wednesday evening, the 4th of December 2013.
  • We should have a conference call on Thursday afternoon, the 5th of December 2013.
To Do CAF/TMU/MEI 2013-12-05
3 Mapping of attributes:
  • The API objects will be defined manually for each resource type.
  • The mapping will be human readable.
  • The mapping will be finalized together with the Application Programming Interface (API) specification.
  • We want to encapsulate the LDAP and want to be able to collect multiple leafs into one object.
To Do CAF/TMU/MEI 2013-12-05
4 Collections (lists):
  • A default set of return values is defined by the specification.
  • Per collection resource a default collation is defined by the specification, see Filtering, sorting and searching
  • Optional: In a later stage, the desired attributes can be requested via query parameter.
Info All 2013-11-27
5 Development:
  • Please check in all code daily (more often is allowed).
  • The code does not need to function, it is important, that it is there and can be reviewed.
Info All 2013-11-27
6 Info All 2013-11-27