Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

Meeting 2019 08 22

Jump to bottom
Hardion Vincent edited this page Aug 22, 2019 · 3 revisions

Agenda

  1. Review of the actions defined during the previous meeting Actions:
  • Action: Piotr will send a new doodle specifying only weekdays and hours, so there is no confusion.
  • ACTION: find editors for RFC-12. Vincent is the editor.
  • ACTION: Find an ediotor for RFC-13 (will be needed upon RFC-12 is done).
  • ACTION: Find a contributor and an editor for RFC-8. Piotr will put a call on the slack channel.

  1. Status of the existing RFC list
    Current Goal: Attribute RFC merged before the next meeting.

    • update on current WIP

    • Properties

    • Device Model

    • Publisher-Subscriber protocol

    • Publisher-Subscriber protocol implementation with ZMQ

    • Device server

    • new RFC-s proposition

  2. AoB

  3. Next meeting

Minutes

Participants: Andy Götz (ESRF), Olga Merkulova (IK), Vincent Hardion (MAX IV) (Chairman)

1) Review of the actions defined during the previous meeting

Actions:

  • Action: Piotr will send a new doodle specifying only weekdays and hours, so there is no confusion.
  • ACTION: Find an editor for RFC-13. Not that urgent yet
  • ACTION: Find a contributor and an editor for RFC-8. Piotr will put a call on the slack channel.

New actions:

  • Decide the date of the next meeting, regarding the result of the doodle.

2) Status of the existing RFC list

  • Current Goal:

    • Attribute RFC in draft.
    • Property RFC in draft.
    • Device Model RFC in draft

  • update on current WIP:

    • Attributes: Merged in draft branch. Reynald has some comments and will open a new MR.
    • Properties: Still the same state. We need more reviewers and check if it can be simplified by moving parts to others RFC like what was done for the attributes properties. This RFC should be merged (or close to) in draft for the next meeting
    • Device Model: More features need description but some of them are more related to the Server part like the blackbox. There is a good chance to merge this RFC for the next meeting.
    • Publisher-Subscriber protocol: Writing in progress. First review done by Reynald. Olga made comment about the difficulties to abstract this RFC from RFC 13. It was decided to continue writing on the RFC/13(ZeroMQ) while to identifying the abstraction.
    • Publisher-Subscriber protocol implementation with ZMQ: Igor will send a merge request with WIP for this RFC before next meeting.

  • Next RFCs in the backlog (Contributors and Editors have to be defined) :

    • Server: There is already a MR from Piotr
    • Class: (Post meeting) To check if the class need a proper RFC or is a paragraph in the Device Model.
    • Database: (Post meeting) David Erb volunteers
    • Request Reply:

  • new RFC-s proposition:

3) AoB

  • The Tango Keyword should start with an Upper case and shouldn't be defined more than once (Editor Guideline)[https://github.com/tango-controls/rfc/wiki/Editor-Guideline]. Andy suggested to use links to point to the RFCs where the keywords are defined. This should be added to the final review.
  • Andy suggested to rename the file of each RFC by there number. An issue will be open to discuss this point.
  • Recall of the first milestone deadline: Mid September the Tango RFC should specify the Request-Reply implemented with the CORBA protocol.

4) Next meeting

Waiting for the closing of the doodle sent by Piotr. It will be probably Monday the 2nd of September.

Clone this wiki locally