-
Notifications
You must be signed in to change notification settings - Fork 4
Meetings 2017 2018
Peter Van den Bosch edited this page Jan 6, 2020
·
1 revision
- scope werkgroep besproken
- werkwijze vastgelegd (zie gitlab wiki)
- gitlab issues overlopen en gepriotiseerd
- issues voor volgende meeting geselecteerd
Tasks:
- prepare short demo of REST contract first with swagger and Java => @virginie.hayot
- look into building REST asciidoc with gCloud jenkins => @willem.salembier
- prepare the three high priority issues for next meeting, update gitlab issues => issue owners + others
- move confluence contents on REST design to gitlab wiki => @peter.vandenbosch
- remove low priority sections from REST guidelines => @peter.vandenbosch
- demo of REST contract first approach with swagger and Java by Virginie
- discussion and conclusion of issues #9 and #6
- there was no time to discuss #4 ; deferred to next meeting
- selected priority issues for next meeting
- next meeting 11/1 at 14h at South Center, Stephane will send invitations
Tasks:
- share artifacts/maven config to set up REST contract first with swagger and Java => @virginie.hayot
- look into building REST asciidoc with gCloud jenkins => @willem.salembier
- prepare the three high priority issues for next meeting => issue owners and others
- #4 null values vs absent properties @steve.vanreeth
- #8 usage of HAL @willem.salembier
- #2 modeling of collections @peter.vandenbosch
- update styleguide and issues with conclusions => @peter.vandenbosch
- status of tasks previous meeting
- discussion of #4, #8 and #2
- conclusions reached for #4 (null values) and #8 (usage of HAL)
- modeling of collections #2 deferred to next meeting
- new issue for embedded resources
- update of issue list, select issues for next meeting (#2, #15, #6)
- list action items, plan next meeting
Tasks:
- gitlab move to git-cicd + create example project => Willem
- commit initial version of example project to gitlab, from eHealth contract first example project => Virginie
- update sections about HAL / links in styleguide with conclusions => Willem
- look into building REST asciidoc with gCloud jenkins => Willem
- update styleguide for absent JSON properties and update issues => Peter
- status of tasks previous meeting
- discussion and conclusions reached for issues #2, #15, #6, #16
- new issues created: #17 , #18
- update of issue list, select issues for next meeting (#1, #3, #7)
Tasks:
- move issues from gitlab to git-cicd => Willem
- check if git-cicd can be made accessible from the public internet => Willem
- look into building REST asciidoc with gCloud jenkins => Willem
- determine website where we can publish styleguide (=> gcloud) => Peter (@plenaire)
- update styleguide and issues with conclusions of previous meeting => Peter
- on hold update example project with respect to new guidelines => Virginie
- status of action items previous meeting
- discussion on issues and conclusions reached for:
- #7 location of common JSON schemas (owner: Virginie)
- #1 versioning: in URL or in HTTP header (owner: Peter)
- #3 controller resources vs commands (owner: Stephane)
- update of issue list, select issues for next meeting
- list action items, plan next meeting
Tasks:
- someone to develop example mock project conform to new guidelines => BOSA (followup by Peter)
- creation of contact address for styleguide => Bob (followup by Peter)
- update issues and styleguide (#1, #3, #7) => Peter
- gitlab access for National Registry => plenaire
Agenda:
- status of tasks previous meeting
- validation of 'controller resources vs commands' conclusions
- Discuss and decide on issues:
- #18 representation of 'greater than' etc in query parameters (owner: Steve)
- #11 caching (owner: Stephane)
- #12 internationalization (owner: Peter)
- Update issue list, determine issues for next meeting
- Plan next meeting
Tasks:
- someone to develop example mock project conform to new guidelines => BOSA (followup by Peter)
- decide on mock API subject (companies?) + swagger spec development
- update styleguide: caching => Stephane; i18n + contact address => Peter; query ordering/search params => Stephane
- prepare issues selected for next meeting => issue owner + all
- gitlab access for National Registry => plenaire
- check for any oversights, new issues still to discuss => all
Agenda:
- status of tasks previous meeting
- Discussed and decided on issues:
- update on #18 representation of 'greater than' etc in query parameters (owner: Steve)
- #17 long-running tasks (owner: Stephane, Steve)
- #14 documentation of update operations (owner: Peter)
- #13 monitoring guidelines (owner: Willem) => continued next meeting
- 3 new issues opened:
- development of styleguide validation tool
- messageId/correlationId
- common gCloud schemas
- mock API development => not addressed
- 3 issues selected for next meeting (see agenda next meeting)
- plan next meeting => 28/6 AM
Tasks:
- someone to develop example mock project conform to new guidelines => BOSA (followup by Peter); still open - BOSA not at plenaire
- subject for mock API subject (companies?) + swagger spec development => all
- [-] update styleguide => #14 (Peter), #17 (Stephane), #18 (Steve) ; #18 to do
- prepare issues selected for next meeting => issue owner + all
- gitlab access for National Registry => plenaire ; no progress
Agenda:
- status of tasks previous meeting:
- gitlab NR to do
- update styleguide: #14, #17 OK and #18 todo (Steve)
- decided on approach mock API subject + swagger spec development, see #19
- Discuss and decide on issues:
- #13 monitoring guidelines (Willem) => concluded
- #20 common gcloud JSON schemas and collaboration with functional WG (Peter) => partially concluded, some open points remain
- #21 message ID / correlation ID (Peter) => postponed to next meeting (no time left)
- no new issues were opened
- plan next meeting => 9/8 at South Center; organized by Willem
Tasks:
- someone to develop example mock project conform to new guidelines => Peter checks with BOSA
- update styleguide => #18 (Steve), #13 (Willem), #20 (Peter)
- prepare issues selected for next meeting => issue owner + all
- gitlab access for National Registry => plenaire
- status of tasks previous meeting
- someone to develop example mock project conform to new guidelines => no temp available at BOSA at the moment. Look for alternatives => Peter will ask at plenaire
- style guide update: #20 done (but not yet published), others to do by next time
- discuss and decide on issues:
- #23 error handling (Willem)
- #22 development of a styleguide validation tool => all: approach?
- #20 common gcloud JSON schemas - ctd. (Peter)
- #21 message ID / correlation ID (Peter)
- new issue created: #24 notifications and REST. Willem will take a look what exists already for eBox.
- next meeting planned
Tasks:
- someone to develop example mock project conform to new guidelines => Peter checks with plenaire
- update styleguide => #18 (Steve), #13 and #23 (Willem), #20 (Peter)
- prepare issues selected for next meeting => issue owner + all
Agenda:
- status of tasks previous meeting
- example mock project conform to new guidelines => API used in Smals architect program can be reused
- styleguide: #20 and #23 incorporated, #13 and #18 remain to do
- discuss and decide on issues:
- gcloud JSON schemas based on functional work group #26 (Peter) => first version presented, to be ctd
- Swagger tooling support #25 (Willem)
- postponed to next meeting:
- #21 message ID / correlation ID (Peter)
- #24 notifications and REST (Willem)
- Any new issues?
- review pilot APIs conform to styleguide #28
- publish gCloud common JSON schemas #27
- styleguide validation tool #22: some work is already in progress by Smals
- next meeting: agenda + date
- Tasks:
- update styleguide:
- #18 search query params (Steve) => some new points were discussed
- #13 monitoring (Willem) => not yet done
- gCloud schemas for common business data #26 (Peter)
- prepare issues selected for next meeting => issue owner + all
- update styleguide:
- discuss and decide on issues:
- #21 message ID / correlation ID (Peter) => partial conclusion, header names to be decided next meeting
- #24 notifications and REST (Willem) => deferred
- review pilot APIs conform to styleguide #28
- mock companies API (Willem) => defered
- socialStatuses (Peter) => reviewed
- followup on evolution of:
- JSON schemas #26 (Peter) => updated, but issue remains WIP
- styleguide validation tool #22: implementation is in progress (Willem)
- swagger tooling #25: new experience shared on various tools
- any progress on other issues; any new issues?
- next meeting: agenda + date
- Tasks:
- update styleguide:
- #18 search query params (Steve) => WIP, almost done
- #13 monitoring (Willem) => reviewed, some modifications
- gCloud schemas for common business data #26 (Peter) => deferred
- preparation issues selected for meeting => issue owner
- update styleguide:
- discuss and decide on issues:
- #21 message ID / correlation ID (Peter) => decisions reached
- #29 organization of JSON Schema files => decisions reached
- #24 notifications and REST (Willem) => deferred to next meeting
- #28 review pilot API conformity to styleguide: mock companies API (Willem) => overview given of API, to be fully validated next meeting
- followup on evolution of:
- gcloud common data types #26 => schemas will be updated by next meeting
- styleguide validation tool #22: some progress achieved, code in gitlab
- swagger tooling #25: Swagger UI watcher, KaiZen
- publishing of JSON schemas #27 => no progress yet
- any progress on other issues; any new issues?
- next meeting: agenda + date