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

Meeting 2019 07 11

Jump to bottom
Piotr Goryl edited this page Jul 16, 2019 · 4 revisions

Agenda

  1. Review of the actions defined during the previous meeting Actions:
  • Action: Sergi Blanch-Torné will update the "How to contribute" section to give more details on the process to contribute on an RFC. This process will be tested with the command RFC, and it might evolve in the future. The How to contribute section of the wiki will evolve at the same time as we adopt this process.
  • Action: Vincent Hardion will contact Gwenaelle Abeillé to ask her to be the editor for the property RFC (RFC-5).
  • Action: There is a need to advertise the tango-rfc project on the tango-controls.org website (forum or news item) to inform the Tango users and attract potential contributors.

  1. Status of the existing RFC list

    • To add or not to add a separate RFC for datatypes

  2. Update the responsible editor's list

    • Call for contributors

  3. To split or not to split the repo?

  4. AoB

  5. Next meeting

Minutes

Participants list

Lorenzo Pivetta, Graziano Scalamera (Elettra), David Erb (MAX-IV), Michal Liszcz, Piotr Goryl (S2Innovation), Andrew Goetz, Reynald Bourtembourg (ESRF), Sergi Blanche-Torne, Sergi Rubio (ALBA), Thomas Braun (byte physics), Igor Khokhriakov, Olga Merkulova (IK)

  1. Review of the actions defined during the previous meeting Actions:
  • Action: Sergi Blanch-Torné will update the "How to contribute" section to give more details on the process to contribute on an RFC. This process will be tested with the command RFC, and it might evolve in the future. The How to contribute section of the wiki will evolve at the same time as we adapt this process.
  • Action: Vincent Hardion will contact Gwenaelle Abeillé to ask her to be the editor for the property RFC (RFC-5).
  • Action: There is a need to advertise the tango-rfc project on the tango-controls.org website (forum or news item) to inform the Tango users and attract potential contributors. Piotr will do this.

  1. Status of the existing RFC list

    • RFC-3: Vincent and Sergi B-T almost finished command specification is almost - by the next meeting it will be merged

    • RFC-5: Reynald and Gwen Property started the work, the PR is in conflict to merge with 'draft' branch.

      • Action: Reynald will clean the conflict.

      • There is an issue with the property name. Jive can set it blank but probably this behavior is not intended. There maybe some other similar cases. So it was discussed. The recipe is:

        • Provide specification for desired/intended behavior,
        • Note that the current implementation allows for non compliant application/usage/behavior but it is not RECOMMENDED.

        It is important to document both: desired and real feature specification and mark which is which.

    • RFC-4: Michał started work on it. Sergi Blanch-Torné has agreed to be an editor.

    • Thomas will contribute to the current-in-progress RFC-s.

    • Proposition of two new RFC-s for:

      • Data types,
      • Naming convention.

      The above will be created when RFC-5 and RFC-3 are merged based on their content.

  2. Update the responsible editor's list

    • Action: Piotr will review and merge Reynald's PR

    • Call for contributors:

      • RFC-1: contributor: Andy, editor: Lorenzo
      • RFC-2: contributor Piotr, editor: David
      • RFC-12, RFC-13: contributors: Olga and Igor,

  3. To split or not to split the repo? Igor will explain the reason on the slack channel.

  4. AoB

    a) Workflow as followed by Vincent and Sergi is:

    • it is started with discussion on Slack about general ideas,

    • WIP PR has been created from the forked repository,

    • formal discussion is on a pull request comments.

    • Action: Sergi Blanch-Torné will update the "How to contribute" section with how to start when someone else has already started the work as the main contributor.

    • Action: Piotr will add and keep track of a wiki page with list of RFCs in progress, editors, contributors (making the main contributor), links to related PRs.

    b) Licensing. It is not clear who should be attributed as a copyright holder and if the license should be a GPL or a GFDL or CC. This is due to thinking about an discussed on the slack channel. Next meeting we aim to make a proposition for the Tango Controls Steering Committee. The Committee will decide.

    c) As it seems that Thursdays mornings are not an option for some Anton and Gwen, but it is easier to plan schedules with fixed meeting time, so the meetings will be scheduled as follow:

    • fixed meeting time will be kept for at least four meetings (so the next meeting will be 25.07.2019, 10:00),
    • if needed (as it is now), a doodle will be created for fixing a new day and hour for next four (at least) meetings.
      • Action: Piotr will send the doodle.

  5. Next meeting

    • The next meeting (25.07.2019) at 10 am CEST will be called by Piotr.
Clone this wiki locally