Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

02 MAR 2022 - Open Source Readiness Meeting Agenda #24

Closed
10 tasks done
psmulovics opened this issue Feb 6, 2022 · 13 comments
Closed
10 tasks done

02 MAR 2022 - Open Source Readiness Meeting Agenda #24

psmulovics opened this issue Feb 6, 2022 · 13 comments
Assignees
Labels
approved Approved meeting minutes meeting GitHub action meeting label

Comments

@psmulovics
Copy link
Contributor

psmulovics commented Feb 6, 2022

Date

2022 Mar 02 - 10 am ET / 3 pm GMT

Untracked attendees

  • Fullname, Affiliation, (optional) GitHub username
  • ...

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 legal@finos.org 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

WebEx info

Join by phone

  • +1-415-655-0003 US Toll
  • +44-20319-88141 UK Toll
  • Access code: 664 434 054
@psmulovics psmulovics added the meeting GitHub action meeting label label Feb 6, 2022
@mcleo-d mcleo-d added this to To do in Open Source Readiness SIG via automation Feb 28, 2022
@mcleo-d mcleo-d moved this from To do to Prioritised in Open Source Readiness SIG Feb 28, 2022
@mcleo-d mcleo-d pinned this issue Feb 28, 2022
@psmulovics
Copy link
Contributor Author

I am here :)

@mcleo-d
Copy link
Member

mcleo-d commented Mar 2, 2022

Hello 🧇

@alstratigos
Copy link

Hi!

@vmbrasseur
Copy link
Contributor

🍜

@bingenito
Copy link
Member

Brian Ingenito @ Morgan Stanley

@agitana
Copy link
Member

agitana commented Mar 2, 2022

Hi! Aitana Myohl / FINOS

@gyehuda
Copy link
Contributor

gyehuda commented Mar 2, 2022

Hello from Gil, open source person at U.S. Bank

@pholleran
Copy link
Contributor

hello-wave

Phil from GitHub

@troups
Copy link

troups commented Mar 2, 2022

simon @ Southampton business school

@jgavronsky
Copy link

Jane @ FINOS here

@psmulovics psmulovics unpinned this issue Mar 3, 2022
@psmulovics psmulovics moved this from Prioritised to In progress in Open Source Readiness SIG Mar 3, 2022
@mcleo-d
Copy link
Member

mcleo-d commented Mar 22, 2022

@psmulovics and @vmbrasseur - Please find the OSR notes and minutes below.

Open Source Readiness Minutes

  • OSR Awesome Lists suggested as starters for 10 categorise against the OSMM dimensions and elements as listed in the GitHub Discussion below - 2022 Community Roadmap #23 (comment)
    • Suggested a top down and bottoms up approach is used to communicate via the OSR Microsite - https://osr.finos.org/
    • It was suggested the OSR SIG is split into work streams to collect and publish OSR materials for others to consume.
    • Open Source Readiness FINOS website initiative page explained to the SIG as a mechanism for managing OSR related materials https://www.finos.org/open-source-readiness
  • Draft roadmap suggested as way to move forward and share to the SIG.
  • What is the minimal viable product needed for a financial services firm to move forward into open source?
    • Suggested priority is defining the OSR MVP thread for FS firms to become open source ready.
  • Codifying contribution rules for License and Compliance was suggested
  • How can we collect questions from FS firms that need to be answered for policy and compliance teams?

@vmbrasseur
Copy link
Contributor

@mcleo-d For the sake of accessibility, could we please get the first two of those images converted to text and add alt text to the other two?

@mcleo-d
Copy link
Member

mcleo-d commented Mar 23, 2022

@mcleo-d For the sake of accessibility, could we please get the first two of those images converted to text and add alt text to the other two?

Hi @vmbrasseur - Thanks for your feedback. I have added links to the original GitHub Discussions and added alt attributes so they are accessible.

I did not create the images as text, as the text already exists in the original GitHub Discussions that are now being linked to.

I hope this works?

@mcleo-d mcleo-d added the pending approval Meeting minutes pending approval label Mar 23, 2022
@psmulovics psmulovics moved this from In progress to Ready for Review in Open Source Readiness SIG Apr 7, 2022
@vmbrasseur vmbrasseur added approved Approved meeting minutes and removed pending approval Meeting minutes pending approval labels May 4, 2022
Open Source Readiness SIG automation moved this from Ready for Review to Done May 4, 2022
biswa-gs added a commit to goldmansachs/open-source-readiness that referenced this issue Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Approved meeting minutes meeting GitHub action meeting label
Projects
Archived in project
Development

No branches or pull requests

10 participants