2022 Community Roadmap #23
Replies: 6 comments 5 replies
-
|
How about:
|
Beta Was this translation helpful? Give feedback.
-
|
@mcleo-d For visibility 👍 |
Beta Was this translation helpful? Give feedback.
-
|
At high level, I think the group should be an engine to identify shared, financial services specific, challenges to open source participation from financial institutions, prioritize them and then foster the creation of projects that address them. If I think at the SIG responsibilities within the broader Open Source Readiness Initiatives (FINOS' bread and butter), here's my input (with contributor hat on, and ED hat off) - hope this helps:
|
Beta Was this translation helpful? Give feedback.
-
|
@psmulovics, @vmbrasseur, @mindthegab and OSR SIG, To help accelerate upon this idea, I have expanded the OSR labels in GitHub to include the categories listed below.
These are now available to help with the triaging of the ideas, issues and feedback that are posted by the group. During the next OSR SIG meeting on 2nd March 2022 (#24), I suggest we review the current OSR Issue backlog to see if there are open issues that can be categorised in this way. Test the water! 💧 |
Beta Was this translation helpful? Give feedback.
-
|
@psmulovics, @vmbrasseur, @mindthegab and OSR SIG, To help with the prioritisation and tracking of work, the Open Source Readiness SIG kanban board has been created ... https://github.com/orgs/finos/projects/28
I have added the issues that are currently in the OSR GitHub Issues, ready for them to be prioritised, categorised and assigned with the SIG on #24. |
Beta Was this translation helpful? Give feedback.
-
|
@psmulovics, @vmbrasseur, @mindthegab and OSR SIG, I have updated the next OSR SIG #24 meeting to cover everything outlined in this thread ... James. |
Beta Was this translation helpful? Give feedback.
-
|
In order to accelerate the collection of OSR materials, I think the OSR information architecture should be categorised to describe the WHAT and the HOW, with the WHAT following the Strategy
Management
Usage
Depending on the release schedule of the OSMM, this tool can be used to measure a FS firm's individual progression into Open Source Readiness, with the survey filled out on a regular cadence to measure progression. The OSMM can also be used to highlight and fill gaps in the knowledge base provided by the OSR SIG. The HOW is up to the OSR SIG to highlight and for materials to be added to the OSR Docs Folder as The DO'ing is then how FS firms use the OSR resources and how that shifts the needle back through the OSMM. In order to accelerate the approach, I suggest creating an initial set of Awesome Lists as demonstrated by the FINOS InnerSource SIG that point to existing TODO and Linux Foundation training materials. Let me know your thoughts, as using Awesome Lists as the initial concept, has a low barrier to entry and can point the OSR SIG to training materials and resources fast. |
Beta Was this translation helpful? Give feedback.
-
|
DLP (Data Leakage Prevention) : This is a key requirement for banks. I thiink it's something that the |
Beta Was this translation helpful? Give feedback.
-
|
Can the roadmap be more specific in the ordering of things. i.e. step 1, step 2, step 3. (with dates?) In particular, I would like to see when the Open Source Readiness survey that Wipro was working on would be ready, or adopted. I think we should be aiming (eventually) on a set of best-practices for running an OSPO, which is content that could be held somewhere on the microsite but maybe isn't totally roadmap-related |
Beta Was this translation helpful? Give feedback.
-
|
from @psmulovics - #29 (comment) I share the sentiment mentioned during the call too of not really feeling this roadmap-y, more like manifesto, goal, etc kind of document - which is fine, we need that too; but when comes to roadmap I more think of something like:
|
Beta Was this translation helpful? Give feedback.
-
|
from @robmoffat - #29 (comment) Here is my starter-for-10 as to what the roadmap might contain. Obviously, up for discussion.
... just off the top of my head. Interested to see what everyone else thinks on this |
Beta Was this translation helpful? Give feedback.
-
Continuing the discussion from today's call.
What would the community like to accomplish this year? Some of the ideas that came up during the call:
Additional ideas are in the notes from the call.
All of the ideas we come up with should take into account the unique constraints of FSIs (regulatory landscape, etc) and also security.
What resources would be useful for you and your company to have? What resources do you wish had existed when you started working with FOSS in your FSI? How can we as the SIG help other orgs improve their open source readiness?
Please share your ideas!
Beta Was this translation helpful? Give feedback.
All reactions