Versions Compared

Old Version 2

changes.mady.by.user Nicholas Kolba

Saved on

compared with

New Version Current

changes.mady.by.user Riko Eksteen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date


Attendees

PMC MembersFINOS FoundationOther Attendees
NameOrganisationNotesGitHub id (optional)Attended?
Nicholas KolbaOpenFinnkolbapresent
Riko EksteenAdaptiverikoepresent

Espen Overbye

(Espen Overbye)OpenFin

bye



present
Jonathan TeperJP MorganFormer user (Deleted)Refinitiv
present
Neil SlingerJP Morgan
present
Tim KoleckeCitadelJohan SanderssonFactSet
present
Rob Underwood (Deactivated)

FINOSbrooklynrobpresent
Tosha EllisonFINOS
present


Open Action Items

Task report
spacesFDC3
labelsFDC3_PMC

Goals

  • Final push for release

...

15 minCombining Context and Intents WG

Espen Overbye

  • We have now successfully launched v1.0 and it might be time to evaluate how we want to  organize the different workstreams going forward.
    We had a set of good discussions early when settling 1.0 for intents, but have since had less activity than the other workstreams.
    To me it makes sense to merge Intens with Context and establish a new Language group; the discussion around context type for “order” vs the intent “placeOrder/SendOrder" is a good example of where a more holistic approach could have landed the type/verb discussion more effectively.
    I propose this to be discussed on the PMC meeting this Friday.

Notes:

Motion raised passed to combine ContextData and Intents into single WG group - titled "Context Data & Intents" with Tim in lead.

10 min FINOS proposal to combine Github projects under FINOS organizationgroup

from Rob Underwood (Deactivated)'s email:

Several community members have suggested that all FINOS repos, across all our programs, should be listed under a single FINOS GitHub organization at

 

www.github.com/finos. Presently, that organization contains only internal FINOS projects, with each program having a separate Github organization, e.g.

 

github.org/finos-plexus.

The current setup was chosen in part because, at the time, it was the only way to give programs administrative rights over their own projects (and only their projects). Thanks to GitHub’s recently improved “teams” and “topics” features, we are able to delegate administration of project repos to programs regardless of which organization they reside in. That way, every FINOS project would be listed at

 

github.com/finos, while program-specific views could be created using topic tags. (Thanks Jamie Jones for all his help working through this.)

To continue this conversation, we’re going to be discussing this topic and next steps as part of a Dx working group meeting on Tuesday April 9th at 11am ET (WebEx details to follow). We’d love to hear from as many of you as possible and help us better understand your program requirements and feedback.

 



  • While there are discoverability arguments to be made in favor of having all repos under github.com/finos, there are also discoverability considerations given that there are programs like FDC3 for which their github org/URL (e.g,. https://github.com/fdc3) are an existing brand asset and so provide some discoverability on their own already. (Essentially what I heard people saying is we can't lose what we already have).
  • Somewhat related, a question arose around what would happen to the "legacy" github orgs after a move/consolidation. A concern was raised around squatters; action item was for Rob to connect with Jamie re the idea in development to consider what would happen with these "old" repos.

Notes:

More discussion will happen at the Dx meeting and the cross-PMC meeting

15 minAOBgroup

FDC3 Release

  • Riko would like to continue branding work ++ from group

Members meeting

  • NIck will be in London
  • Tosha handling scheduling

Action items