Streamlined Onboarding Template

[robmoffat]

As discussed in the meeting last week, I've re-arranged the onboarding template to reduce the number of hand-offs. There are four stages (described at the top), each with a different owner. I've preserved everything from the original template, but tried to put the contributor in the driving seat for answering as many of the questions as possible.

Hopefully, this should mean that the FINOS Point-Of-Contact only needs to get involved for a short period of time in step 2, to get the project through the technical steering committee, and that FINOS Infra only needs to get involved at the very end, and can complete the onboarding without involving the original contributor at all, since they've already provided all the information required to complete the onboarding.

Hopefully this makes sense, happy to do a walkthrough if that helps.

[netlify[bot]]

✅ Deploy Preview for eager-borg-83c1a5 canceled.

Name	Link
🔨 Latest commit	f83daa7c503bdc2487a3990caf6638b1ce1e8746
🔍 Latest deploy log	https://app.netlify.com/sites/eager-borg-83c1a5/deploys/635267e5f1d36d0008f6167a

[maoo]

I'd like to request a small enhancement; from now on, we need to communicate to the LF when there are changes to our list of ongoing project contributions:

• Any incoming contribution is recorded as "Exploratory"
• When TSC approves the contribution it moves to "Engaged"
• When contribution is completed, it moves to "Active"

Actions to take:

• Subscribe to the GitHub community repository
• Email LF when:
  • A new contribution issue is submitted , under the exploratory stage
  • A new contribution gets approved by TSC, under the engaged stage
  • A new contribution is completed, under the active