traderX
traderX copied to clipboard
finos
8 April 2024 - TraderX Meeting Agenda
Date
8 April 2024 - 8 am EST / 1 pm GMT
Previous Meeting
22 March 2024 - TraderX Meeting Agenda
Untracked attendees
Meeting notices
-
FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
-
All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
-
FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.
-
FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.
Agenda
- [x] Convene & roll call (5mins)
- [x] Display FINOS Antitrust Policy summary slide
- [x] Review Meeting Notices (see above)
- [x] Approve past meeting minutes ( #141 )
- [x] Introductions
- New issues
- [ ] #142
- [ ] FDC3 Hackathon end of Q2 (@maoo )
- [ ] Milestones review (add issues to milestones)
- [ ] AOB, Q&A & Adjourn (5mins)
Discussed Points
- @psmulovics - raised opportunity to create a cross-project milestone (E.g. for OSSF June/LN, or OSSF Nov /NY) for tracking things we want to get done by the events.
- Reviewed #133 - Agreed it's not top priority but good opportunity for outside contribution.
- Discussed http://app.moderne.io - and updating FINOS (not just TraderX) code using OpenRewrite recipes. NOTE: I had Moderne add the whole FINOS org to their list of open source orgs they keep ready for analysis and modification.
- Discussed CDM/TraderX - integration / experiments.
Next Steps:
- Add C4 Diagram thumbnail and other architecture/flow links to main README as an interim step for enhanced documentation (Open a new issue)
- @tomhealey-icma and @maoo to explore integrating CDM/TraderX in a branch environment - for #140
- @rocketstack-matt - in Architecture as Code SIG - What are the next steps?
- Solicit volunteers to build the website/Documentation / #133
- @psmulovics discovered that the .NET code for People Service is not up to date. Will create an issue to update it.
Zoom Details
- https://zoom.us/j/96264933811?pwd=d2VmSkdudDRXZytPclBRblc4eUlEZz09
- Meeting ID: 962 6493 3811
- Passcode: 532953
Join by Phone
- Find your local number: https://zoom.us/u/adl5rhui4P
Project roadmap example here - https://github.com/orgs/finos-labs/projects/7/views/2
@DovOps here are the minutes
Discussed Docusaurus
- Demo of localhosted Docs page by @DovOps
- next steps, looking to fully integrate the CALM CLI with @rocketstack-matt
- Docusaurus aggregating ReadMe? @maoo
Roadmap
- Getting Started with the process
- Discuss creating the roadmap on the Project Board in Public @rocketstack-matt
- Discussion around public-ness around project boards
- Need to decide on best practices for permissioning around who has access to create/delete
Introductions:
- Maria Lopatkova (SmoothStack) (Untracked)
- Prashanth Ram, SmoothStack, CTO
- Janet Fernando - SmoothStack (Untracked)
- Leandro Yabut, SmoothStack SmoothStack is interested in Issue #131 (Single Sign-On)
Single Sign-On Github as default
- Multiple Social Logins (@PR-SS)
- Simplicity as north star, every line of code should make things easier @DovOps
- Simplicity vs Security, what is needed for an application like TraderX - particularly in tracking user actions
- How much do we need to protect against exploits? @psmulovics
- Can a daily/hourly/etc restart fix any issues?
- Can a disclaimer give ample protection? Sign it on a regular basis @DovOps
- Account name is currently only place where text can be impacted
- Cookie/disclaimer: "this is a demo environment, you have to click this every time you use it"
- @tomhealey-icma - perhaps the demo itself doesn't allow any free text input
- Set a header/footer with info - @DovOps @maoo writing comment
- Guest user= limited functionality, Social login= more functionality @pr-ss
- disclaimer linked on the page
What goes in the docs
- How to keep the "underlying philosophy" of the project in the docs which gives guidance @maoo @DovOps
- Guidance around forking, hard since we don't have any now
- We don't have enough forks/branches yet in order to have a guidance flow, but this will help guide partnerships with TraderX @DovOps @PR-SS
Next Steps
- @maoo to discuss developer events
- @karlmoll to discuss one-pager/one-slide