Page Comparison

Requests from Tick42, etc → they want to have FDC3 branding on their website … some forms of FDC3 certifications.

Nick: Tricky question as standards are evolving

Not that different than PWA

Nick: Focus will be app certification, but anticipate platforms too

Outstanding question: what would be the process for certification; basically it would be self-declared

Question: would we make people certify after a period of time

Nick: I think we would do continuous

Question: What does the branding look like?

Task: Determine certification criteria (Nick and Neil)

Task: Certification badge/logo

• Needs to be editable
• Need to live somewhere where we can get access
• Do a PPT that can be exported as a PDF?
• Link to it from the overview page?

Review good things / bad

• introduction to FDC3
• FDC3 session

• Ask for FINOS was to do a meeting akin to a standard session
• Nick: that was a tricky ask; didn’t know who would be in the session
• Good session but I would do it differently than next time
• Tim: It was good to put faces to the name … was good to see what other folks; opportunities
• Nick: Learning about other programs is also important
  • These two programs are going to pivotal
  • Set some templates for how these work together more closely
    
    
• E.g., Nick’s convo wtih Hammad -- connecting on how to get things done, process
• Nick: There is a board meeting July 11 that I (Nick) will be putting together a presentation together
  • Nick: I think there is 0 overlap. Folks doing Plexus are participating in FDC3. Been suggested that Plexus code should live in FDC3. I (Nick) don’t think it should -- FDC3 could contain reference implementations but not live implementations.
  • Need to address it at the board meeting
    
    
  • RPC alignment -- still getting worked through.
  • How technology projects get housed is an important consideration
    
    
• One thing that came up was overlap between Plexus and FDC3
• Nick: It’s great to get together in person. Could we do an FDC3 meetup?
• Set up a meetup as tentative … set a schedule

should we host quarterly live meetups for FDC3 participants?

Yes, first one to target NYC in Sep/Oct

• Saori: Do we have an opinion on how FDC3 working groups speak with each other?
  • Espen: It could/should happen more
  • Tim: I think monthly meeting are enough. I thought that was what that forum was for
  • Nick: I would think it would be the use case group that is keeping us honest
  • Tim: yes, everyone can participate on the list?
  • Nick: Confluence as well as git(hub) are also places to give input
    
    
  • Saori: Leslie did miss the webex (Leslie did not know about the meeting / web ex issues)? -- Leslie did say he was going to write some up about the “lawnchair (laundry list?) of apps”
  • What are the guidelines?
    • Raise it and get fixed if missing
  • Things need to be on the agenda for the monthly meeting, or distributed via announcements and/or mailing lists
  • Nick: Do we do 5 minutes to do an update for people who are not involved in the working group regularly?
  • Saori: Do each one of the working groups having a mailing list? And are they on the homepage
• Nick: That happens once a month in the general meeting
• Saori: It is happening implicitly … maybe that’s the solution. Specifically this came up with the use case working group.
• Saori: Is the best way really to communicate vs.
• Nick: Example of overlap could be Leslie (Tick)
  
  
• Johan: It would be good if Leslie could jot down what he was discussing so that other folks could review it