Plan ahead finoslabs + DCO (for AIR TechSprint)

[mindthegab]

Per discussions on Monday, the following activities can start already:

• [x] creation of the finos-labs org
• [x] add FINOS branding to organisation
• [x] publishing dco text
• [x] configure automation to enforce DCO (on cla=bot or similar)
• [x] Document developer requirements

Please start on this ASAP.

[mcleo-d]

Please find the FINOS Labs implementation document on Google Drive below ....

https://docs.google.com/document/d/1ZbPt7gvNXPMfCW0Tkfbd7Tq_KSfhh5VJCujas5b73dY/edit?usp=sharing

[mcleo-d]

@mindthegab, @maoo and @toshaellison - The FINOS Labs organisation has been created at https://github.com/finos-labs and configured with the information in the screenshot below ...

[mcleo-d]

Probot DCO has been configured on FINOS Labs as per the configuration demonstrated on Hyperledger Labs - https://github.com/hyperledger-labs/

Probot DCO

Probot DCO on Hyperledger Labs in Practice

Next Steps ...

This FINOS Labs DCO configuration will need further 'real world' testing by @mcleo-d and @maoo.

[mcleo-d]

Project Blueprint mirrored as a private template repo on FINOS Labs as initial placeholder for developer documentation https://github.com/finos-labs/project-blueprint

[mcleo-d]

Initial DCO test on GitHub Labs Project Blueprint done, but it was realised all previous commits from the mirrored FINOS Project Blueprint need to be retrospectively signed with DCO too ...

https://github.com/finos-labs/project-blueprint/pull/1

DCO Failed

DCO Retrospectively Signed with Rebase

DCO Passed