This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
Meeting 2020 02 10
Piotr Goryl edited this page Feb 11, 2020
·
2 revisions
-
Review of the actions defined during the previous meeting Actions:
- From the previous meeting:
- (2020-01-27) ACTION: Michal to ask Piotr about status of the "Mission Statement" issue.
- (2020-01-27) ACTION: Sergi to review RFC-14 as an editor.
- (2020-01-27)ACTION: Michal to check with Piotr why this PR is WIP and what is the current status of RFC-10 PR.
- Older:
- (2019-11-18): ACTION: Vincent: to review RFC-14 (Logging service) as well.
- (2019-11-18): ACTION: All working on RFCs: check YAML header in your PR if
editor
is specified - Sergi will review Michals's PR.
- (2020-01-13): A reminder was sent on slack.
- (2019-12-16) ACTION: Piotr will send a message about proposed new file naming schemas asking for comments/voting, to be able to take a decision in January.
- (2020-01-13): Reynald suggested to include this information also in the invitation for the next RFC team meeting so that votes from more people can be collected and the decision can be made during the next meeting.
- From the previous meeting:
-
Status of the existing RFC list
-
The current goal:
- Data Types RFC in draft.
-
update on current WIP
- RFC-4 Attributes
- RFC-12 Publisher-Subscriber protocol
- RFC-13 Publisher-Subscriber protocol implementation with ZMQ
- RFC-8 Device server
- RFC-1 Tango Controls
- RFC-14 Logging Service
- RFC-9 Data types
- RFC-10 Request-Reply
- RFC-7 Pipe
- RFC-15 Dynamic Attribute and Command
-
new RFC-s proposition
-
-
AoB:
- File naming
-
Next meeting:
Participants: Vincent Hardion (MAX-IV), Sergi Blanch-Torné (ALBA), Reynald Bourtembourg (ESRF), Lorenzo Pivetta (Elettra), Piotr Goryl (S2Innovation)
-
Review of the actions defined during the previous meeting Actions:
- From the previous meeting:
- (2020-01-27) ACTION: Michal to ask Piotr about status of the "Mission Statement" issue.
- (2020-02-10) ACTION: Piotr will create a PR and wait one week for comments, then merge
- (2020-01-27) ACTION: Sergi to review RFC-14 as an editor.
- The RFC is merged. Gratulations!
- The RFC needs some improvements and (2020-02-10) ACTION: Sergi will create an issue.
- Vincent will talk to David
- (2020-01-27)ACTION: Michal to check with Piotr why this PR is WIP and what is the current status of RFC-10 PR.
- (2020-01-27) ACTION: Michal to ask Piotr about status of the "Mission Statement" issue.
- Older:
- (2019-11-18): ACTION: Piotr will review check YAML header in your PR if
editor
is specified. - (2019-12-16) ACTION: Piotr will send a message about proposed new file naming schemas asking for comments/voting, to be able to take a decision in January.
- (2020-01-13): Reynald suggested to include this information also in the invitation for the next RFC team meeting so that votes from more people can be collected and the decision can be made during the next meeting.
- (2019-11-18): ACTION: Piotr will review check YAML header in your PR if
- From the previous meeting:
-
Status of the existing RFC list
-
The current goal:
- Data Types RFC in draft.
-
update on current WIP
- RFC-12 Publisher-Subscriber protocol - Vincent did the review. It needs definitions to be synchronised with ones in other RFCs. Vincent is thinking about accepting the RFC then create issue/PRs for improvements,
- RFC-13 Publisher-Subscriber protocol implementation with ZMQ - no news,
- RFC-8 Device server - (2020-02-10) ACTION: Vincent and Lorenzo will merge two existing PRs into one,
- RFC-1 Tango Controls - no news,
- RFC-14 Logging Service - It is already merged into 'draft. Please refer to comment in the actions list,
- RFC-9 Data types - Reynald made a review. (2020-02-10) ACTION: Piotr will implement Reynalds comments.
- RFC-10 Request-Reply - (2020-02-10) ACTION: Piotr will rebase the branch (accept the PR by Vincent). Vincent will start work on details for commands handling.
- RFC-7 Pipe - Reynald made a review, waiting for feedback.
- RFC-15 Dynamic Attribute and Command - Reynald did a review and volunteered to be the editor.
-
new RFC-s proposition
- The DevFailed 'reason' key-words will be provided by specific RFCs. The separate RFC may be added in future but now it is not needed.
-
-
AoB:
- File naming - the schema with file named according to the short name of the RFC is accepted. (2020-02-10) ACTION: Piotr will apply the naming schema.
-
Next meeting: 24.02.2020