Please note that only FINOS members can propose new projects. If you're interested in membership, see https://www.finos.org/membership-benefits#become-a-member.

Business Problem

“Our mission is to enable global recognition and trust of Distinguished Engineers as a professionally accredited role and its ability to influence digital technology and its impact on society for the better.”

Proposed Solution

To build a community of Engineering leaders who can influence digital technology to have a positive impact on society.

Current State

We have established a working group with over 30 members from tier one financial banks and other software engineering providers but now look to formalise our community and allow our members to contribute freely.

Existing Materials

Target Audience – Engineering Experts and Engineering Leaders across technology
Legal and Privacy Considerations – The community members will be representing themselves and the companies they work for and so we must ensure strict legal and privacy considerations are considered.
Platform and tools – We want our members to share documentation and ideas. Events are hosted in person at our members premisses and using Zoom.
Community Culture and Values – Our community values collaboration over competition.
Content and Knowledge Sharing – We want to share knowledge freely and enable our members to contribute to articles, white papers and other live events so that common challenges can be addressed.
Member Engagement – we see new members coming to the community from all areas of engineering not just financial services.
Member responsibilities – We expect our members to be active e.g. 1 contribution per annum
Moderation and Management – We see the community becoming self-managed with a governance structure created by key members of the community.
Networking and Collaboration Opportunities – We see the community being broken down into sub teams to be able to work on initiatives.
Sustainability – We see the community as not for profit and we hope to scale across engineering industry.
Feedback and Continuous Improvement – We will gather feedback from members and build backlog of work to help improve the community and deliver our mission.

SIG Maintainers

Who will be the SIG maintainer(s)? Provide full name, affiliation, work email address, and GitHub.com username.

Mark Brotherwood, Davies Group, mark.brotherwood@davies-group.com, marksandsparks1
Peter Thomas, deutsche bank, peter.thomas@db.com

SIG Contribution and Onboarding process (v. 1.0, last updated on October 27, 2020)

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

Voting (SIG Lead and FINOS ED)

• Contribution author triggers community socialization to gauge interest - recommended emailing issue link to community@finos.org
• If there's positive response from the Community, prepare short SIG proposal deck for the FINOS Governing Board. You can start by downloading and using this template. See a previous SIG example.
• Assign issue to Executive Director (@mindthegab) to trigger vote
• Executive Director brings SIG to the Board for additional socialization and approval
• FINOS board accepts the SIG (and the onboarding process can move forward)

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

• Identify and Assign FINOS SIG POC
• Link to SIG approval resolution - // public link to board resolution
• SIG Name
  • Assess current trademark status
• Category and sub-category (for FINOS Landscape)
• Existing content/assets or new Github repository
• Team composition: lead maintainer and other maintainers
• Meetings? (existing/yes/no)
• Meeting minutes, agenda, attendance tracking (existing/yes/no)
• Documentation website (existing/yes/no)
• Define SIG slug : Dependant on Define new SIG name

Project Communication Channel(s)

• Ask maintainers which communications channels they'd like to use and if more than one are needed. These may include
  • Creation of one or more project mailing lists (e.g. general@, or dev@ and users@)
• Create the identified communication channels during infra set up
• Link communication channels linked front and center in the project README.md.

Repository transfer (Lead: FINOS Infra)

• Check GitHub repository transfer requirements:
  • finos-admin has Admin to all repositories to transfer
  • finos-admin is 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
• Transfer all assets as GitHub repositories under github.com/finos
• Invite GitHub usernames to GitHub FINOS Org
• Create <sig-name>-maintainers GitHub team and invite users
• Configure finos-admins and finos-staff team permissions

Infra setup (Lead: FINOS Infra)

• Update SIG README

Metadata update (Lead: FINOS Infra)

• Add logo to FINOS landscape
• Add SIG Leads emails to finos-project-maintainers@finos.org list
• Add SIG Leads GitHub usernames to the project-maintainers Team

Update FINOS SIG Roster

• FINOS Governance

Announcement (Lead: FINOS POC)

• Work with FINOS marketing to send out announcement to announce@finos.org , checkout announcement template at the Contribution page.
• Notify FINOS POC and FINOS marketing manager once the announcement has been sent out (FINOS infra)

Press Release (OPTIONAL) (Lead: FINOS POC)

• Identify quotes for press release
• Draft press release
• Send embargoed press release to reporters
• Coordinate social media promotion of the press release with FINOS marketing
  • Post on FINOS social media
  • Post on LF social media

Onboarding and training

• FINOS SIG Governance
• FINOS Project Lifecycle
• FINOS Collaboration infrastructure

Contributors Metadata (Lead: FINOS SIG POC, Support: FINOS infra)

• For each SIG material contributor 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)