As I mentioned at the TSC meeting yesterday, I had a discussion with the Linux Foundation CommunityBridge project manager earlier in the week and discovered that, as an LF project, OpenHPC will be accepted in CommunityBridge even if we don't strictly meet all the requirements. And we have flexibility on the management of stipends, to manage them as OpenHPC pleases.
The OpenHPC TSC sounds like it is interested in moving forward on a Code of Conduct, even if it may not be strictly required for CommunityBridge. Code of Conducts are considered best practice for open source projects and is a positive step to encourage diversity.
On Wed, Aug 5, 2020 at 1:22 PM Neal Caidin <ncaidin@...> wrote:
Dear OpenHPC Governing Board Members, and TSC,
From my investigations, I don't think we will run into any significant roadblocks in using the CommunityBridge system for the OpenHPC Mentorship Program. CommunityBridge has a couple of pre-requisites, such as having a Code of Conduct and getting certified by the Core Infrastructure Initiative. Even if we don't already have these things, they should also be easy to manage (and both are worthwhile having and considered best practices). If OpenHPC does not have a Code of Conduct already, we can use the Contributor Covenant . CommunityBridge provides this as a default choice (and it is a very popular choice among open source projects). And OHC has 90 days to work on the CII badge , which I believe should not be too onerous. Also, CommunityBridge follows the Google SOC convention for mentee stipends , which are based on Purchasing Power Parity, which I'm not aware we have discussed, but we should be fine budget-wise with this.
I'm happy to serve as the Administrator for OpenHPC on CommunityBridge to help things go smoothly and work out any kinks. I'm optimistic, we can turn around on this quickly, and we can also link to the OpenHPC wiki for additional details.
The Linux Foundation requires all Mentorship projects to use CommunityBridge, including projects with existing Mentorship programs. As examples, the Linux Kernel and Hyperledger have migrated and are actively using the system. I believe the rationale for the requirement to use CommunityBridge, at least in part, is for LF to manage these programs at scale. Also, it is an opportunity to encourage best practices.