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)
 
(8 intermediate revisions by 2 users not shown)
Line 61: Line 61:
 
* They have implemented REST in the proper way, including http auth.
 
* They have implemented REST in the proper way, including http auth.
 
* If you want to, build upon the example.
 
* If you want to, build upon the example.
| width="70px"  | Info
+
Questions:
| width="70px"  | All
+
* MIT Licence a problem for us?
 +
** No
 +
*** If possible: keep the modifications/additions on the yii-rest-api portion generic enough (possibly fork visibly on Github) and release additions and changes without a licence in one of our protected repositories, as we have not decided, which license we will use. Copyright is steppp stepping stone GmbH.
 +
*** In case of copying/merging portions of the code, retain the original copyright in addition to yours/ours.
 +
| width="70px"  | To Do
 +
| width="70px"  | CWI
 
| width="70px"  | 2013-11-27
 
| width="70px"  | 2013-11-27
 
|-
 
|-
Line 77: Line 82:
  
 
| width="40px"  | 3
 
| width="40px"  | 3
| width="800px"  |  
+
| width="800px"  | 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.
 +
| width="70px"  | To Do
 +
| width="70px"  | CAF/TMU/MEI
 +
| width="70px"  | 2013-12-05
 +
|-
 +
 
 +
| width="40px"  | 4
 +
| width="800px"  | 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 [[Application_Programming_Interface_(API)#Filtering.2C_sorting_and_searching |  Filtering, sorting and searching]].
 +
* Optional: In a later stage, the desired attributes can be requested via query parameter.
 
| width="70px"  | Info
 
| width="70px"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 83: Line 102:
 
|-
 
|-
  
| width="40px"  | 4
+
| width="40px"  | 5
| width="800px"  |  
+
| 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"  | Info
 
| width="70px"  | All
 
| width="70px"  | All
Line 90: Line 111:
 
|-
 
|-
  
| width="40px"  | 5
+
| width="40px"  | 6
 +
| width="800px"  | Specification:
 +
* Each form is first displayed as an empty form via JavaScript and then filled out with the next JavaScript call.
 +
Questions?
 +
* Could for certain cases PHP calls used to fill the forms directly (internally)?
 +
* Or should we phase out the PHP calls step for step?
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-11-28
 +
|-
 +
 
 +
| width="40px"  | 7
 +
| width="800px"  | Core / Modules:
 +
* The stoney core contains the base functionality.
 +
* The URL contains the module name and then the version:
 +
** http://selfcare.stepping-stone.ch/module/v1/account/list
 +
| width="70px"  | Info
 +
| width="70px"  | CWI
 +
| width="70px"  | 2013-11-28
 +
|-
 +
 
 +
| width="40px"  | 8
 
| width="800px"  |  
 
| width="800px"  |  
 
| width="70px"  | Info
 
| width="70px"  | Info
Line 98: Line 140:
  
 
|}
 
|}
 
  
 
[[Category:2013]]
 
[[Category:2013]]

Latest revision as of 11:44, 28 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.

Questions:

  • MIT Licence a problem for us?
    • No
      • If possible: keep the modifications/additions on the yii-rest-api portion generic enough (possibly fork visibly on Github) and release additions and changes without a licence in one of our protected repositories, as we have not decided, which license we will use. Copyright is steppp stepping stone GmbH.
      • In case of copying/merging portions of the code, retain the original copyright in addition to yours/ours.
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 Specification:
  • Each form is first displayed as an empty form via JavaScript and then filled out with the next JavaScript call.

Questions?

  • Could for certain cases PHP calls used to fill the forms directly (internally)?
  • Or should we phase out the PHP calls step for step?
Info CWI 2013-11-28
7 Core / Modules: Info CWI 2013-11-28
8 Info All 2013-11-27