ColinEberhardt Github contribution chart
ColinEberhardt Github Stats
ColinEberhardt Most Used Languages

Activity

04 Oct 2022

ColinEberhardt

Fixed links

Pushed On 04 Oct 2022 at 09:37:13

ColinEberhardt

started

Started On 04 Oct 2022 at 06:28:36

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Merged On 03 Oct 2022 at 03:42:23

ColinEberhardt

👍👍👍

Commented On 03 Oct 2022 at 03:42:23

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Forked On 03 Oct 2022 at 02:49:33

ColinEberhardt

Unless I’m mistaken, this will still mutate ‘into.description’ - the line above just creates a new reference to the same object. JS spread operator should fix this … ‘schema._info = { …schema.info, description: /** your code here **/ }’
On 03 Oct 2022 at 02:49:33

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Merged On 03 Oct 2022 at 02:49:38

ColinEberhardt

Commented On 03 Oct 2022 at 02:49:38

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Merged On 03 Oct 2022 at 02:49:38

ColinEberhardt

Commented On 03 Oct 2022 at 02:49:38

ColinEberhardt

Compliance Horizon Scanning Ready for TSC Review

Hi @ColinEberhardt and the TSC,

@sndpkumar14 and the Synechron team is ready to present the proposed Compliance Horizon Scanning contribution (https://github.com/finos/community/issues/195) to the FINOS TSC.

Can you provide guidance and a date for when the presentation to the TSC can take place?

Kind regards,

James.

Forked On 30 Sep 2022 at 12:54:20

ColinEberhardt

HI @mcleo-d thanks for the heads-up, I'll start organising a suitable time. We have Vuu in the queue already.

Can you please apply the ready for tsc label? I'll make sure it moves to the right lane in our project board

Commented On 30 Sep 2022 at 12:54:20

ColinEberhardt

Minor tweaks

Pushed On 30 Sep 2022 at 09:08:51

ColinEberhardt

started

Started On 30 Sep 2022 at 08:50:10

ColinEberhardt

Include API metadata in output

Adds new handlebar file to include api metadata in output

Forked On 29 Sep 2022 at 03:52:18

ColinEberhardt

Does this interface have to be generated? couldn't it be static, based on the OpenAPI spec?
On 29 Sep 2022 at 03:52:18

ColinEberhardt

Include API metadata in output

Adds new handlebar file to include api metadata in output

Merged On 29 Sep 2022 at 03:53:42

ColinEberhardt

Nice idea regarding creating an 'info' object 👍

Small point, TypeScript types should be CamelCase

Also, I think the description and potentially some of this other information should be added to the API documentation here for example:

https://github.com/ScottLogic/openapi-forge-typescript/blob/main/example/api/api.ts#L16

Commented On 29 Sep 2022 at 03:53:42

ColinEberhardt

Include API metadata in output

Adds new handlebar file to include api metadata in output

Merged On 29 Sep 2022 at 03:53:42

ColinEberhardt

Nice idea regarding creating an 'info' object 👍

Small point, TypeScript types should be CamelCase

Also, I think the description and potentially some of this other information should be added to the API documentation here for example:

https://github.com/ScottLogic/openapi-forge-typescript/blob/main/example/api/api.ts#L16

Commented On 29 Sep 2022 at 03:53:42
Create Branch
ColinEberhardt In ScottLogic/openapi-forge-typescript Create Branchosouthwell-scottlogic-main

ColinEberhardt

⚒️ OpenAPI Forge generator for TypeScript clients

On 29 Sep 2022 at 03:41:26

ColinEberhardt

Fix prettier errors
Merged On 29 Sep 2022 at 01:44:51

ColinEberhardt

Commented On 29 Sep 2022 at 01:44:51

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Merged On 29 Sep 2022 at 01:37:30

ColinEberhardt

A few comments ...

Commented On 29 Sep 2022 at 01:37:30

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Forked On 29 Sep 2022 at 01:37:21

ColinEberhardt

A couple of minor points ... 1. Transformation of the schema should be handled in the `transformers.js` logic 2. Rather than mutate the schema, I'd prefer to add new properties. In other words, keep `description` intact, and add `_description` 3. Not really sure what the JSON stringify / parse is for?
On 29 Sep 2022 at 01:37:21

ColinEberhardt

Include API metadata in output

Adds two new helpers and removes new lines in info description. This is needed to add the metadata to the output #16

Merged On 29 Sep 2022 at 01:37:29

ColinEberhardt

A few comments ...

Commented On 29 Sep 2022 at 01:37:29

ColinEberhardt

test: tests now run on non-Windows platforms (#13)

Pushed On 29 Sep 2022 at 01:23:36

ColinEberhardt

test: tests now run on non-Windows platforms

Created On 29 Sep 2022 at 01:23:36
Issue Comment

ColinEberhardt

Software Project Contribution and Onboarding - Vuu

Business Problem

User interfaces for financial applications often have differing requirements to generic UI Frameworks. In general these can be summarised as:

  • The style of interface is often largely grid based
  • it can often contain large amounts of information, tens of millions of rows is common
  • the data often is dynamic, incorporating rapid updates and ticking data sources like market data
  • the data is often sourced from multiple different technologies (slow moving data sources, like databases and fast moving data sources like order management systems and market data systems) and the user wants this data to be joined at runtime

Proposed Solution

Vuu is a framework for building front end applications for trading and risk use-cases. It is split into two components, the first is a Scala based server component which acts as the server side cache of data, this provides a table model for representing and joining live tables of data from various sources, it also provides a framework for sorting, filtering and treeing on the server based on client requests. It also provides viewports onto the trees or tables for multiple users. The server also provides an ability to tick data quickly through the system for rapid updates to individual rows.

The second component is a React based UI grid and layout framework that manages the communications with the server, that renders the visible viewports for the user (whether they be tree or flat table based) and that gives the impression to the user that all of the data that a user is viewing is seamlessly available on the client.

The glue that connects these pieces is a web-worker/websocket layer that handles realtime updates from the server based on updates on the underlying datasource or based on user actions on the front end, such as scrolling or sorting.

Tentative Roadmap

The initial phase would be working towards a v1.0 release of the framework, where we can support all of the necessary use cases for building trading front ends. Its felt we are between 80% and 90% of the way there with the existing code base.

A phase 2 release would incorporate additional functionality such as real time charting, additional user widgets for specialised forms of visual filtering and the ability to support big data streaming uses cases (10bn+ rows)

Current State

The project began in 2014, it was worked on as a PoC for several years before gaining more momentum towards a functional beta release in 2020/2021. The project has now beed adopted by UBS as part of the strategic front office UI toolkit.

Existing Materials

The software is already opened source on Github under an Apache 2.0 licence.

Code: https://github.com/venuu-io/vuu/ Book: https://venuu-io.github.io/vuu/

Development Team

Maintainers

Chris Stevenson, UBS, chris-za.stevenson@ubs.com, Founding Developer, Admin Steve Heron, UBS, steve.heron@ubs.com, Founding Developer, Admin Dimitar Dimitrov, UBS, dimitar.a.dimitrov@ubs.com, Developer Michael Stonestreet, UBS, michael.stonestreet@ubs.com, Developer Michael Banham, UBS, michael.banham@ubs.com, Developer, Admin Allan Jakobsen, UBS, allan.jakobsen@ubs.com, Product Owner Marina Bambang, UBS, marina.bambang@ubs.com, Product Owner

Confirmed contributors

(as above)

Target Contributors

  • Neil Slinger, JP Morgan + Team
  • Others TBC

Infrastructure needs

Describe the FINOS infrastructure you will need for this project, in addition to a GitHub repository. The FINOS team will connect with you before setting up any of this infrastructure

What's next?

Upon submission of this project proposal, the FINOS team will get in touch with you to discuss next steps.


Contribution process (v. 1.1, last updated on December 20, 2021)

Below is the list of tasks that FINOS Team and the contribution author go through in order to complete the FINOS contribution process. Please do not edit these contents at contribution time!

Kick-off meeting

FINOS Contrib POC

  • [ ] Identify and Assign FINOS Project Coordinator
  • [ ] Identify and Assign FINOS Strategic Advisor

Proposal (Lead Maintainer)

  • [ ] Lead maintainer to send out announcement to community@finos.org using this template:

    Dear FINOS Community, 
    
    We would like to propose a new FINOS project. Please review the proposal details at (_TODO: add link to the GitHub issue proposal_).
    
    If you're interested in participating, please :+1: the GitHub issue proposal and drop a comment with your name, org and email
    
    Thanks a lot, 

Identify project meta (Lead: FINOS Contrib POC, Support: FINOS Marketing)

  • Project main coordinates
    • [ ] Project Name
    • [ ] Project Slug
    • [ ] Does the name have a registered trademark?
    • [ ] Request logo design (if needed)
  • [ ] Category and sub-category (for FINOS Landscape)
  • [ ] Is there existing code? If so, is it public? If not, can you grant read access to user github.com/finos-admin ?
  • [ ] Was the project ever released? If so, are releases public? And what's the latest released version?
  • [ ] Team composition: lead maintainer and other maintainers
  • [ ] Are meetings currently held for the project?
  • [ ] Are meeting minutes, agenda and attendance tracked?
  • [ ] Is Continuous Integration used? If so, which system is used?
  • [ ] Is there an existing Documentation website? If not, would you like to have one?

Maintainers, contributors and CLAs (Lead: FINOS Contrib POC, Support: FINOS infra)

  • [ ] For each maintainer identified in the previous step, collect: the following info:
    • Fullname
    • GitHub username
    • Corporate email address
  • [ ] Identify other existing contributors (assuming there's a contribution history (eg Git history)
  • [ ] Check if maintainers and other contributors are all covered by FINOS CLA
  • [ ] Engage with FINOS Legal team to figure out what’s needed to cover all maintainers and contributors with FINOS CLA
  • [ ] Reach out to contributors and employers to coordinate CLA signatures

Project Communication Channel(s)

  • [ ] Ask maintainers which communications channels they'd like to use
  • Asynchronous
    • [ ] GitHub Issues (public)
    • [ ] GitHub Discussions (public)
    • [ ] GitHub Team Discussions (public and private FINOS CLAs Required)
    • [ ] Mailing-list (groups.io)
  • Synchronous
    • [ ] FINOS Slack Channel (general public Slack / leadership private Slack)
  • [ ] Create the identified communication channels during infra set up
    • [ ] Create mailing-list on lists.finos.org (optional)
      • [ ] Enable Hubspot Sync for all project mailing lists created
      • [ ] Aggregate mailing lists to community@finos.org
      • [ ] Update marketing lists
        • Add new list to the included "Email List" part of the filter
        • Add new list to the excluded "Email" part of the filter
  • [ ] Link communication channels linked front and center in the project README.md

Code validation (only if code is contributed) (Lead: FINOS Infra)

  • [ ] The codebase doesn’t have HIGH or CRITICAL CVEs across direct and transitive libraries
  • [ ] The codebase doesn’t have any unfriendly licenses across direct and transitive libraries
  • [ ] (optional - if a build system is provided) The build process runs successfully
  • [ ] finos-admin is Admin of the GitHub repository to transfer
  • [ ] The codebase doesn’t include any patent or copyright that conflicts with FINOS Governance and bylaws (to be validated with FINOS Legal team)
  • [ ] Apply project blueprint contents - see ODP docs
    • [ ] Ensure that the proper project governance is in the CONTRIBUTING.md file
  • [ ] All incubating criteria are checked and documented below

Approval (Lead: FINOS Infra)

  • [ ] Assign issue to Executive Director (@mindthegab) to trigger voting
  • [ ] (optional) if additional socialization is required, the Executive Director may bring projects to the FINOS Governing Board
  • [ ] FINOS accepts the contribution (and the contribution process can move forward)

Code transfer (Lead: FINOS Infra)

  • [ ] Backup (even with screenshot) GitHub permissions of the repository to transfer
  • [ ] Check GitHub repository transfer requirements:
    • [ ] finos-admin has Admin to all repositories to transfer
    • [ ] finos-admin ia allowed to transfer repositories out of the org
    • [ ] if the repository is owned by a user (and not an org), the user must be able to transfer the repository to finos-admin
  • [ ] Review FINOS project blueprint contents
    • [ ] Project title/description in README
    • [ ] Project badge in README
    • [ ] License in README
    • [ ] Contributing in README
    • [ ] CONTRIBUTING.md
    • [ ] LICENSE (look for {} placeholders)
  • [ ] Check protection settings and disable after transfer if necessary
  • [ ] Transfer all code assets as GitHub repositories under github.com/finos
  • [ ] Invite GitHub usernames to GitHub FINOS Org
  • [ ] Create <project-name>-maintainers GitHub team and invite users
  • [ ] Configure finos-admins (Maintain role) and finos-staff (Triage role) team permissions

Infra setup (Lead: FINOS Infra)

  • [ ] Enable EasyCLA
  • [ ] Add project to metadata
  • [ ] Add identities, orgs and affiliations to metadata (deprecated by EasyCLA)
  • [ ] Add logo to FINOS landscape
    • [ ] Create staging branch on finos/finos-landscape
    • [ ] Merge finos/metadata changes on master (will udpdate landscape.yml in finos/finos-landscape)
    • [ ] Create PR from staging branch on finos/finos-landscape
    • [ ] Review Netlify preview
    • [ ] Merge PR
  • [ ] Add project maintainers emails to finos-project-maintainers@finos.org list
  • [ ] Add project maintainers GitHub usernames to the project-maintainers Team
  • [ ] Onboard project on LF systems (SFDC, Insights, EasyCLA, Groups.io)
  • [ ] (best effort) Update release coordinates and code namespace to include finos
  • [ ] Enable security vulnerabilities scanning
  • [ ] (optional) Enable meeting attendance tracking
  • [ ] (optional) Onboard into legend.finos.org/studio

Announcement (Lead: FINOS Contrib POC)

  • [ ] Lead maintainer works with FINOS marketing to send out announcement to announce@finos.org , checkout announcement template at the Contribution page
  • [ ] Notify FINOS Contrib POC and FINOS marketing (@grizzwolf + finos-marketing internal Slack channel)

Forked On 29 Sep 2022 at 12:27:43

ColinEberhardt

Hi @chrisjstevo - we didn't really have time to slot you in for the meeting yesterday, lots of other house-keeping!

However, the TSC are very keen to hear more about this project. Are you happy for us to arrange a demo to the group? If it helps, please contact me via email to arrange.

Commented On 29 Sep 2022 at 12:27:43

ColinEberhardt

Generated files are formatted using prettier (which is JS/TS specific)

Current formatting of generated files is hard coded for typescript. Ideally this would be based on the generator used.

Forked On 29 Sep 2022 at 09:22:41

ColinEberhardt

There is a slightly immature looking CSharp formatter for Prettier (https://github.com/warrenseine/prettier-plugin-csharp), however, it might make sense to delegate formatting to the generators themselves, allowing them to use language-appropriate tooling.

Commented On 29 Sep 2022 at 09:22:41

ColinEberhardt

Fix testing when using custom file paths

Fix for https://github.com/ScottLogic/openapi-forge/issues/79

Removed logic that determines if the default value for featurePath and generatePath should be used. Instead two scripts are now exposed.

test : This needs a featurePath & generatePath given test:defaultPath : This uses the default values for featurePath & generatePath

I opted for this convention over 'test' & 'test:customPath' because the addition of writing ':defaultPath' prevents the need for you to write the two paths so it still produces a optimised route.

If you used ':customPath' the user needs to write additional word in the test script name and also the two custom paths and therefore the command is even longer. Also test-generators uses 'test' so it reduces the code changes needed for this new script configuration to work.

Merged On 29 Sep 2022 at 08:44:01

ColinEberhardt

Commented On 29 Sep 2022 at 08:44:01

ColinEberhardt

updated blog link

Pushed On 28 Sep 2022 at 01:58:26

ColinEberhardt

Implement a release process

Potentially using semantic release

Forked On 28 Sep 2022 at 08:37:33

ColinEberhardt

As an aside, when implementing, can we also add commitlint (or similar), to ensure that commit messages follow the correct convention. We also need to check the default branch settings are appropriate.

Commented On 28 Sep 2022 at 08:37:33
Issue Comment

ColinEberhardt

Software Project Contribution and Onboarding - Vuu

Business Problem

User interfaces for financial applications often have differing requirements to generic UI Frameworks. In general these can be summarised as:

  • The style of interface is often largely grid based
  • it can often contain large amounts of information, tens of millions of rows is common
  • the data often is dynamic, incorporating rapid updates and ticking data sources like market data
  • the data is often sourced from multiple different technologies (slow moving data sources, like databases and fast moving data sources like order management systems and market data systems) and the user wants this data to be joined at runtime

Proposed Solution

Vuu is a framework for building front end applications for trading and risk use-cases. It is split into two components, the first is a Scala based server component which acts as the server side cache of data, this provides a table model for representing and joining live tables of data from various sources, it also provides a framework for sorting, filtering and treeing on the server based on client requests. It also provides viewports onto the trees or tables for multiple users. The server also provides an ability to tick data quickly through the system for rapid updates to individual rows.

The second component is a React based UI grid and layout framework that manages the communications with the server, that renders the visible viewports for the user (whether they be tree or flat table based) and that gives the impression to the user that all of the data that a user is viewing is seamlessly available on the client.

The glue that connects these pieces is a web-worker/websocket layer that handles realtime updates from the server based on updates on the underlying datasource or based on user actions on the front end, such as scrolling or sorting.

Tentative Roadmap

The initial phase would be working towards a v1.0 release of the framework, where we can support all of the necessary use cases for building trading front ends. Its felt we are between 80% and 90% of the way there with the existing code base.

A phase 2 release would incorporate additional functionality such as real time charting, additional user widgets for specialised forms of visual filtering and the ability to support big data streaming uses cases (10bn+ rows)

Current State

The project began in 2014, it was worked on as a PoC for several years before gaining more momentum towards a functional beta release in 2020/2021. The project has now beed adopted by UBS as part of the strategic front office UI toolkit.

Existing Materials

The software is already opened source on Github under an Apache 2.0 licence.

Code: https://github.com/venuu-io/vuu/ Book: https://venuu-io.github.io/vuu/

Development Team

Maintainers

Chris Stevenson, UBS, chris-za.stevenson@ubs.com, Founding Developer, Admin Steve Heron, UBS, steve.heron@ubs.com, Founding Developer, Admin Dimitar Dimitrov, UBS, dimitar.a.dimitrov@ubs.com, Developer Michael Stonestreet, UBS, michael.stonestreet@ubs.com, Developer Michael Banham, UBS, michael.banham@ubs.com, Developer, Admin Allan Jakobsen, UBS, allan.jakobsen@ubs.com, Product Owner Marina Bambang, UBS, marina.bambang@ubs.com, Product Owner

Confirmed contributors

(as above)

Target Contributors

  • Neil Slinger, JP Morgan + Team
  • Others TBC

Infrastructure needs

Describe the FINOS infrastructure you will need for this project, in addition to a GitHub repository. The FINOS team will connect with you before setting up any of this infrastructure

What's next?

Upon submission of this project proposal, the FINOS team will get in touch with you to discuss next steps.


Contribution process (v. 1.1, last updated on December 20, 2021)

Below is the list of tasks that FINOS Team and the contribution author go through in order to complete the FINOS contribution process. Please do not edit these contents at contribution time!

Kick-off meeting

FINOS Contrib POC

  • [ ] Identify and Assign FINOS Project Coordinator
  • [ ] Identify and Assign FINOS Strategic Advisor

Proposal (Lead Maintainer)

  • [ ] Lead maintainer to send out announcement to community@finos.org using this template:

    Dear FINOS Community, 
    
    We would like to propose a new FINOS project. Please review the proposal details at (_TODO: add link to the GitHub issue proposal_).
    
    If you're interested in participating, please :+1: the GitHub issue proposal and drop a comment with your name, org and email
    
    Thanks a lot, 

Identify project meta (Lead: FINOS Contrib POC, Support: FINOS Marketing)

  • Project main coordinates
    • [ ] Project Name
    • [ ] Project Slug
    • [ ] Does the name have a registered trademark?
    • [ ] Request logo design (if needed)
  • [ ] Category and sub-category (for FINOS Landscape)
  • [ ] Is there existing code? If so, is it public? If not, can you grant read access to user github.com/finos-admin ?
  • [ ] Was the project ever released? If so, are releases public? And what's the latest released version?
  • [ ] Team composition: lead maintainer and other maintainers
  • [ ] Are meetings currently held for the project?
  • [ ] Are meeting minutes, agenda and attendance tracked?
  • [ ] Is Continuous Integration used? If so, which system is used?
  • [ ] Is there an existing Documentation website? If not, would you like to have one?

Maintainers, contributors and CLAs (Lead: FINOS Contrib POC, Support: FINOS infra)

  • [ ] For each maintainer identified in the previous step, collect: the following info:
    • Fullname
    • GitHub username
    • Corporate email address
  • [ ] Identify other existing contributors (assuming there's a contribution history (eg Git history)
  • [ ] Check if maintainers and other contributors are all covered by FINOS CLA
  • [ ] Engage with FINOS Legal team to figure out what’s needed to cover all maintainers and contributors with FINOS CLA
  • [ ] Reach out to contributors and employers to coordinate CLA signatures

Project Communication Channel(s)

  • [ ] Ask maintainers which communications channels they'd like to use
  • Asynchronous
    • [ ] GitHub Issues (public)
    • [ ] GitHub Discussions (public)
    • [ ] GitHub Team Discussions (public and private FINOS CLAs Required)
    • [ ] Mailing-list (groups.io)
  • Synchronous
    • [ ] FINOS Slack Channel (general public Slack / leadership private Slack)
  • [ ] Create the identified communication channels during infra set up
    • [ ] Create mailing-list on lists.finos.org (optional)
      • [ ] Enable Hubspot Sync for all project mailing lists created
      • [ ] Aggregate mailing lists to community@finos.org
      • [ ] Update marketing lists
        • Add new list to the included "Email List" part of the filter
        • Add new list to the excluded "Email" part of the filter
  • [ ] Link communication channels linked front and center in the project README.md

Code validation (only if code is contributed) (Lead: FINOS Infra)

  • [ ] The codebase doesn’t have HIGH or CRITICAL CVEs across direct and transitive libraries
  • [ ] The codebase doesn’t have any unfriendly licenses across direct and transitive libraries
  • [ ] (optional - if a build system is provided) The build process runs successfully
  • [ ] finos-admin is Admin of the GitHub repository to transfer
  • [ ] The codebase doesn’t include any patent or copyright that conflicts with FINOS Governance and bylaws (to be validated with FINOS Legal team)
  • [ ] Apply project blueprint contents - see ODP docs
    • [ ] Ensure that the proper project governance is in the CONTRIBUTING.md file
  • [ ] All incubating criteria are checked and documented below

Approval (Lead: FINOS Infra)

  • [ ] Assign issue to Executive Director (@mindthegab) to trigger voting
  • [ ] (optional) if additional socialization is required, the Executive Director may bring projects to the FINOS Governing Board
  • [ ] FINOS accepts the contribution (and the contribution process can move forward)

Code transfer (Lead: FINOS Infra)

  • [ ] Backup (even with screenshot) GitHub permissions of the repository to transfer
  • [ ] Check GitHub repository transfer requirements:
    • [ ] finos-admin has Admin to all repositories to transfer
    • [ ] finos-admin ia allowed to transfer repositories out of the org
    • [ ] if the repository is owned by a user (and not an org), the user must be able to transfer the repository to finos-admin
  • [ ] Review FINOS project blueprint contents
    • [ ] Project title/description in README
    • [ ] Project badge in README
    • [ ] License in README
    • [ ] Contributing in README
    • [ ] CONTRIBUTING.md
    • [ ] LICENSE (look for {} placeholders)
  • [ ] Check protection settings and disable after transfer if necessary
  • [ ] Transfer all code assets as GitHub repositories under github.com/finos
  • [ ] Invite GitHub usernames to GitHub FINOS Org
  • [ ] Create <project-name>-maintainers GitHub team and invite users
  • [ ] Configure finos-admins (Maintain role) and finos-staff (Triage role) team permissions

Infra setup (Lead: FINOS Infra)

  • [ ] Enable EasyCLA
  • [ ] Add project to metadata
  • [ ] Add identities, orgs and affiliations to metadata (deprecated by EasyCLA)
  • [ ] Add logo to FINOS landscape
    • [ ] Create staging branch on finos/finos-landscape
    • [ ] Merge finos/metadata changes on master (will udpdate landscape.yml in finos/finos-landscape)
    • [ ] Create PR from staging branch on finos/finos-landscape
    • [ ] Review Netlify preview
    • [ ] Merge PR
  • [ ] Add project maintainers emails to finos-project-maintainers@finos.org list
  • [ ] Add project maintainers GitHub usernames to the project-maintainers Team
  • [ ] Onboard project on LF systems (SFDC, Insights, EasyCLA, Groups.io)
  • [ ] (best effort) Update release coordinates and code namespace to include finos
  • [ ] Enable security vulnerabilities scanning
  • [ ] (optional) Enable meeting attendance tracking
  • [ ] (optional) Onboard into legend.finos.org/studio

Announcement (Lead: FINOS Contrib POC)

  • [ ] Lead maintainer works with FINOS marketing to send out announcement to announce@finos.org , checkout announcement template at the Contribution page
  • [ ] Notify FINOS Contrib POC and FINOS marketing (@grizzwolf + finos-marketing internal Slack channel)

Forked On 27 Sep 2022 at 02:18:32

ColinEberhardt

HI @mindthegab - it is on our agenda for tomorrow https://github.com/finos/technical-steering-committee/discussions/37, although this will just be a high-level introduction. If the FINOS team have specific priorities / deadlines regarding Vuu / ISDA / Desktop Agent Bridge, it would be good to understand this.

Commented On 27 Sep 2022 at 02:18:32

ColinEberhardt

Fix prettier errors
Forked On 27 Sep 2022 at 02:02:29

ColinEberhardt

yes i missed that, i have added it now

thanks @jhowlett-scottlogic - feel free to merge when you've resolved conflicts

Commented On 27 Sep 2022 at 02:02:29