Page Comparison

• 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.

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.