I have a deep technical background in architecting, implementing and managing critical software solutions for the backoffice environment of financial institutions, with expertise in integration with Swift, financial messaging standards and various technologies. I'm motivated to extend my professional profile by participating at complex technological projects, having a born ambition to deliver more than against set goals. In my spare time I enjoy skiing and reading fiction novels.
You raised an excellent point! While planning the launching of FinTP project and the FINkers United, we assumed that new roles of communicating and integrating newcomers in the community would add some extra workload on the team. However, in practice we experienced a more direct approach from interested parties - rather than publicly interact through the communication channels in place - forum, github and so on. We've reached two conclusions: we need to extend the team by adding varied resources - from business analysts, to developers, testers, support and so on - dedicated to interact with interested parties in the project and community. The second one is that we need to improve the documentation provided, on all technical levels (architecture, customizing executable code for particular cases, data mappings, operational flows in the application, requirements).
Bottom line is that we indeed identified a need for human resources growth and we are actively seeking financing resources to ensure that we keep pace with the project delivery timeline.
Thanks for your input. I'm not going to argue on the technical side, as I don't have experience in programming besides what I've studied at the university. Also, I can't vouch for the accuracy of White Source's studies, but I have to admit it made me think a bit. Usually OS/infrastructure software have a different life cycle than business applications. From what I've seen application updates are not triggered by new available updates of embedded open source libraries, but mostly from new business requirements or high to critical bug fixes of the application. With this scenario in mind, a vendor might sell his latest version of application which was compiled an year ago and, as a consequence, has embedded old versions of open source libraries.
Maybe you could elaborate your idea in the second paragraph a bit more because I didn't quite get it.