Difference between revisions of "2013-12-05 Telephone Conference DEVROOM / stepping stone GmbH"
From stoney cloud
[unchecked revision] | [unchecked revision] |
(→Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH) |
(→Transcript) |
||
(23 intermediate revisions by the same user not shown) | |||
Line 12: | Line 12: | ||
| width="80px" | '''Time''' | | width="80px" | '''Time''' | ||
− | | width="800px" | 13:30 until | + | | width="800px" | 13:30 until 15:00 |
|- valign="top" | |- valign="top" | ||
Line 39: | Line 39: | ||
** isActive is missing in the current examples. | ** isActive is missing in the current examples. | ||
** The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies. | ** The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies. | ||
− | ** We'll define a search REST API, so that we can return results according to the [[:Image:Search.png | mockup]]. | + | ** We'll define a search REST API, so that we can return results according to the [[:Image:Search.png | mockup]]. The return values should be a collection containing type, uid, overview information and a REST url. With this information, the application should be able to build a new page with the proper url and retrieve the data with the help of the REST url. |
+ | ** The [[Application_Programming_Interface_(API)#REST_API_documentation | REST API documentation]] will be split into multiple documents, corresponding with the module names (core, ...). | ||
* Decision JavaScript Framework | * Decision JavaScript Framework | ||
* What is missing for the tender? | * What is missing for the tender? | ||
Line 58: | Line 59: | ||
| width="40px" | 1 | | width="40px" | 1 | ||
− | | width="800px" | | + | | width="800px" | Each resource collection: |
− | | width="70px" | | + | * Will be updated. |
− | | width="70px" | | + | | width="70px" | To Do |
+ | | width="70px" | TMU/MEI | ||
| width="70px" | 2013-12-05 | | width="70px" | 2013-12-05 | ||
|- | |- | ||
| width="40px" | 2 | | width="40px" | 2 | ||
− | | width="800px" | | + | | width="800px" | Do we return empty values (like shippingAddress) or not? |
− | | width="70px" | | + | * Empty values are not displayed (all possible vaules must appear in the documentation). |
+ | | width="70px" | Decision | ||
| width="70px" | All | | width="70px" | All | ||
| width="70px" | 2013-12-05 | | width="70px" | 2013-12-05 | ||
Line 72: | Line 75: | ||
| width="40px" | 3 | | width="40px" | 3 | ||
− | | width="800px" | | + | | width="800px" | isActive is missing in the current examples. |
− | | width="70px" | | + | * Will be updated. |
− | | width="70px" | | + | | width="70px" | To Do |
+ | | width="70px" | TMU/MEI | ||
| width="70px" | 2013-12-05 | | width="70px" | 2013-12-05 | ||
|- | |- | ||
| width="40px" | 4 | | width="40px" | 4 | ||
− | | width="800px" | | + | | width="800px" | The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies. |
+ | * The application is responsible for the deletion of the dependencies. | ||
| width="70px" | Info | | width="70px" | Info | ||
| width="70px" | All | | width="70px" | All | ||
Line 86: | Line 91: | ||
| width="40px" | 5 | | width="40px" | 5 | ||
− | | width="800px" | | + | | width="800px" | New Functionality in the REST api: |
+ | * We need a call, the can return either the number of dependencies or directly a list of all the dependencies (resource url). | ||
+ | * Will we need a call, that helps the JavaScript Framework to create the breadcrumbs (people, services)? | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | TMU/MEI | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 6 | ||
+ | | width="800px" | Search REST API: | ||
+ | * Documentation will be updated to reflect the changes. | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | TMU/MEI | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 7 | ||
+ | | width="800px" | The REST API documentation will be split: | ||
+ | * Reseller and Customer and People are more or less the same. | ||
+ | * The difference is in the mapping. | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | TMU/MEI | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 8 | ||
+ | | width="800px" | The REST API documentation will be extended: | ||
+ | * Mapping table. | ||
+ | * Mandatory/optional table. | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | TMU/MEI | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 9 | ||
+ | | width="800px" | Decision JavaScript Framework: | ||
+ | * AngularJS. | ||
+ | | width="70px" | Decision | ||
+ | | width="70px" | All | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 10 | ||
+ | | width="800px" | What is missing for the tender? | ||
+ | * Extent 1: | ||
+ | ** REST api stoney core | ||
+ | ** REST api stoney core test | ||
+ | ** Frontend: Reseller | ||
+ | * Extent 2: | ||
+ | ** Frontend: Customer, People | ||
+ | * Extent 3: | ||
+ | ** REST api stoney vm | ||
+ | ** REST api stoney test | ||
+ | ** Frontend: vm's | ||
| width="70px" | Info | | width="70px" | Info | ||
| width="70px" | All | | width="70px" | All | ||
| width="70px" | 2013-12-05 | | width="70px" | 2013-12-05 | ||
|- | |- | ||
+ | |||
+ | | width="40px" | 11 | ||
+ | | width="800px" | Test Environment: | ||
+ | * Test Data will be delivered by SST | ||
+ | * SST can deliver a complete VM (including Web Server and LDAP Server) | ||
+ | | width="70px" | Info | ||
+ | | width="70px" | All | ||
+ | | width="70px" | 2013-12-05 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 12 | ||
+ | | width="800px" | Testing Tools? | ||
+ | * On multiple Levels | ||
+ | ** PHP Unit Tests (really necessary? will we gain anything?) | ||
+ | ** REST API Tests (Postman?, SoapUI?) | ||
+ | ** Web Interface Tests (Selenium?) | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | All | ||
+ | | width="70px" | 2013-12-11 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 13 | ||
+ | | width="800px" | Next steps: | ||
+ | * Finalize specification. | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | TMU/CAF/MEI | ||
+ | | width="70px" | 2013-12-11 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 14 | ||
+ | | width="800px" | Mockups: | ||
+ | * We talked about a third button in the listing views, which would give us more functionality (was discussed in Munich). | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | MEI | ||
+ | | width="70px" | 2013-12-11 | ||
+ | |- | ||
+ | |||
+ | | width="40px" | 15 | ||
+ | | width="800px" | Tender for Extent 1 | ||
+ | | width="70px" | To Do | ||
+ | | width="70px" | CWI | ||
+ | | width="70px" | 2013-12-16 | ||
+ | |- | ||
+ | |||
|} | |} | ||
[[Category:2013]] | [[Category:2013]] |
Latest revision as of 16:01, 5 December 2013
Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH
Location | Skype |
Date | Thursday, the 5th of December 2013 |
Time | 13:30 until 15:00 |
Participants |
|
Non participants |
|
Agenda |
|
Transcript
No. | Text | What? | Who? | When? |
---|---|---|---|---|
1 | Each resource collection:
|
To Do | TMU/MEI | 2013-12-05 |
2 | Do we return empty values (like shippingAddress) or not?
|
Decision | All | 2013-12-05 |
3 | isActive is missing in the current examples.
|
To Do | TMU/MEI | 2013-12-05 |
4 | The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies.
|
Info | All | 2013-12-05 |
5 | New Functionality in the REST api:
|
To Do | TMU/MEI | 2013-12-05 |
6 | Search REST API:
|
To Do | TMU/MEI | 2013-12-05 |
7 | The REST API documentation will be split:
|
To Do | TMU/MEI | 2013-12-05 |
8 | The REST API documentation will be extended:
|
To Do | TMU/MEI | 2013-12-05 |
9 | Decision JavaScript Framework:
|
Decision | All | 2013-12-05 |
10 | What is missing for the tender?
|
Info | All | 2013-12-05 |
11 | Test Environment:
|
Info | All | 2013-12-05 |
12 | Testing Tools?
|
To Do | All | 2013-12-11 |
13 | Next steps:
|
To Do | TMU/CAF/MEI | 2013-12-11 |
14 | Mockups:
|
To Do | MEI | 2013-12-11 |
15 | Tender for Extent 1 | To Do | CWI | 2013-12-16 |