Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[sparkplug-dev] Eclipse Sparkplug Specification Project - Meeting Notes - 03 November 2020

Hi all,

 

Please find the Eclipse Sparkplug Specification Project meeting notes from today’s meeting below. Please let me know if I missed anything.

 

Eclipse Sparkplug Specification Project - Meeting Notes - 03 November 2020

  • Attendees: 
    • Chad Kienle
    • Dominik Obermaier
    • Frederic Desbiens
    • Ilya Binshtok
    • Josh Wolf
    • Nathan Davenport
    • Travis Cox
    • Wes Johnson

 

  • Reviewed the latest version of the Sparkplug specification containing Dominiks’s and Wes’s recent changes.
    • Spec work can now be better divided up per chapter.
    • First step is to simply copy the original content over to the new chapter. Improvements/amendments should be made *after* we get the original content ported over.
      • Review the chapter in the original spec, before picking up the porting task.
      • First 80% should be easy.. how to deal with the last 20%?
        • Last 20% can likely be completed with the assistance of the working group. Reach out over Slack for help/guidance.
        • Any remaining work that cannot be completed with the help of the working group should be tracked in a new GitHub issue/task so the original “porting” task can be resolved.
      • Normative and Non-normative statements should not be addressed until all of the content has been ported over to the new specification. These statements will be easier to flush out once content is ported.
    • ADoc Eclipse plugin is useful for Ascii doc work.
    • Formatting guidelines should be established and followed... We will use Wes’s first draft as a template and discussion point.
    • Review all existing GitHub issues before creating any new ones to ensure you’re not creating a duplicate.
    • Post to the Slack channel if you need any help / guidance

  • We need to define the specification to annotations to tests flow. Wes to take a stab at a first draft of this flow. Review the video with Ivar from our last meeting to see an example of this flow.

  • How do we submit a PR? Who should be on it?
    • At least two Approvers (one should probably be CirrusLink developer for now).
    • The PR author should merge after at least two Approvers have signed off.
    • Where should we be discussing PR feedback?
      • On the PR if short.
      • Over Slack if a longer discussion is expected.
    • PRs should be opened against the develop branch only (GitFlow process)

  • Next Steps
    • [Action Item] Working Group, please pick up one or more tasks for the specification content port with the goal of completing it before our next meeting.

 

Thanks,

Nathan

Back to the top