From b5a3d0f21d235b55be70a25fadd65dc44b17d559 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" Date: Fri, 29 Apr 2022 18:25:52 +0200 Subject: [PATCH 1/5] grants policy --- grants_policy.md | 94 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100644 grants_policy.md diff --git a/grants_policy.md b/grants_policy.md new file mode 100644 index 0000000..6a6d148 --- /dev/null +++ b/grants_policy.md @@ -0,0 +1,94 @@ +Policy: + +All applications for funding of the CWL project (grant applications, and +similar) must be submitted by Software Freedom Conservancy (SFC) unless +an agreement otherwise has been approved by both the CWL Project +Leadership Team and SFC itself. + +Submitting grants and/or getting funding to do the work of the CWL +project without approval from SFC and the CWL Leadership Team can result +in cancellation of sustaining/support member status (without refund), +censure, and/or other consequences as deemed appropriate by SFC and the +CWL Leadership Team. + +Motivation: + +CWL is a member project of Software Freedom Conservancy, Inc. As per the +[membership agreement signed by all members of the initial CWL project +leadership +team](https://github.com/common-workflow-language/governance/blob/ddb07b99ae62006f70cd43987843626ffe08c2f0/CWL-sponsorship-agreement--signed-by-all.pdf), +CWL is a [direct +project](https://en.wikipedia.org/wiki/Fiscal_sponsorship#Table_comparing_the_models) +of SFC: CWL is owned by SFC, and the project's work is implemented by +SFC employees and volunteers. + +Implementation: + +This section documents how an entity (the Properser) submitting grants +that involve Common Workflow Language standards (CWL) and the CWL +Project (which for now on will be referred to as the Project) should +seek approval for their Proposal from the CWL Leadership team and SFC. + +There are four options for getting Project approval: + +1. If a proposal indicates the use of CWL but will *not* be contributing substantially to the Project (e.g. code, + documentation, tutorials), then *no Proposal approval is needed*. + * If the proposed grant is funded, please consider adding (if allowed) your proposal [to the list of + projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) + using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). +2. For a Proposal that indicates substantial contributions to the Project, there are two paths + * The default path is to submit a Proposal via the Software Freedom Conservancy (SFC) itself. Please contact SFC & the CWL + leadership as soon as possible by emailing [commonworkflowlanguage\@sfconservancy.org](mailto:commonworkflowlanguage@sfconservancy.org) + with an initial description of the grant proposal. + * If the SFC is ineligible to apply for this opportunity, or there is another good reason why an external entity should submit + instead of SFC, then approval by the Project *is* needed **and** justification for not submitting via Software Freedom + Conservancy is required. + * The Proposer will document and explain why the Proposal can not be sent by SFC; for example due to geographic or + entity type restrictions. + * The Proposer will supply the aims of the grants, total grant budget and duration. + * The Proposer will supply a form (modeled after [this](https://upload.wikimedia.org/wikipedia/commons/6/6d/GLAM_partnership_evaluation_handout.pdf) + form by the Wikimedia Foundation) to explain the benefits and risks of the proposed contributions to the Project. + * The aims and form will be due 2 weeks before any Letter of Support (LOS) is needed and should be sent to the leadership team + . + A default LOS will be used unless otherwise requested by the Propser. + * If no members of the Project leadership team nor the SFC object to the grant proposal, the proposal will be + approved and the LOS will automatically be provided. + * The members of the CWL Leadership team will keep information about grants that are not funded under a reasonable expectation of privacy + * Note that a Memorandum of Understanding (MOU) (e.g. + ) + between SFC and the Proposers will need to be developed and signed; plan accordingly. + * If the Proposal is funded, it is required to publicly announce the funded grant on the CWL forum and link to the + proposal (if it is possible to make publicly available) + +For all these proposal options, Common Workflow Language should be cited +using the [proper up-to-date citations](https://www.commonwl.org/specification/#references). + +\-- + +Expectations for CWL Project Lead or delegate + +1. Maintain private log of notifications + +2. Check with the Mission & Vision for the CWL project + +3. Check for alignment with the community roadmap + +4. Confirm a proper statement of how the applicants and the project are or are-not related + +5. If the details can't be shared with the entire team, then extract relevant details and report to PLT + +6. Provide quarterly summary to the CWL PLT + +7. Follow-up to publicize when appropriate + +Recording: + +1. Code name to cross-reference with private notes (if needed) + +2. Day of submission + +3. Expected start & end date + +4. Work to be done; aspects of the CWL Community Roadmap that overlap/alignment + +5. Expected date of application funding decision From a43507b545d222aba6169af56eafd9f0f032f989 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" Date: Thu, 26 May 2022 18:25:25 +0200 Subject: [PATCH 2/5] clarifications from meeting with Karen Sandler, SBG, Curii. --- grants_policy.md | 109 ++++++++++++++++++++++++++++------------------- 1 file changed, 66 insertions(+), 43 deletions(-) diff --git a/grants_policy.md b/grants_policy.md index 6a6d148..7f12732 100644 --- a/grants_policy.md +++ b/grants_policy.md @@ -1,17 +1,34 @@ -Policy: +# Policty on requesting and/or acquiring grants/funding for/by the CWL Project -All applications for funding of the CWL project (grant applications, and -similar) must be submitted by Software Freedom Conservancy (SFC) unless -an agreement otherwise has been approved by both the CWL Project -Leadership Team and SFC itself. +## Policy + +It is a requirement of the CWL fiscal sponsor, Software Freedom Conservancy (SFC), +that all applications by any entity for +1) funding of the CWL project's work or +2) in the name of the CWL project +must be submitted by SFC **unless** an agreement otherwise has been approved by +both the CWL Project Leadership Team and SFC. Submitting grants and/or getting funding to do the work of the CWL -project without approval from SFC and the CWL Leadership Team can result -in cancellation of sustaining/support member status (without refund), -censure, and/or other consequences as deemed appropriate by SFC and the -CWL Leadership Team. +Project (or otherwise in the name of or on-behalf of the CWL Project) without +approval from SFC and the CWL Leadership Team can result in cancellation of +sustaining/support member status (without refund), censure, and/or other +consequences as deemed appropriate by SFC and the CWL Leadership Team. + +Proposals for implementations (or enhancements of implementations) of the CWL +Standards do not need approval, unless it is of the CWL reference implementation +(`cwltool`). + +Proposing work related to any of the CWL GitHub organizations is a sign that +approval **is needed**. +- +- +- + +If there is doubt about what constitutes "the work of the CWL project", please +ask the CWL Leadership Team directly. -Motivation: +## Motivation CWL is a member project of Software Freedom Conservancy, Inc. As per the [membership agreement signed by all members of the initial CWL project @@ -20,45 +37,51 @@ team](https://github.com/common-workflow-language/governance/blob/ddb07b99ae6200 CWL is a [direct project](https://en.wikipedia.org/wiki/Fiscal_sponsorship#Table_comparing_the_models) of SFC: CWL is owned by SFC, and the project's work is implemented by -SFC employees and volunteers. +SFC employees, volunteers, and contractors. -Implementation: +## Implementation This section documents how an entity (the Properser) submitting grants that involve Common Workflow Language standards (CWL) and the CWL -Project (which for now on will be referred to as the Project) should -seek approval for their Proposal from the CWL Leadership team and SFC. - -There are four options for getting Project approval: - -1. If a proposal indicates the use of CWL but will *not* be contributing substantially to the Project (e.g. code, - documentation, tutorials), then *no Proposal approval is needed*. - * If the proposed grant is funded, please consider adding (if allowed) your proposal [to the list of - projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) - using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). -2. For a Proposal that indicates substantial contributions to the Project, there are two paths - * The default path is to submit a Proposal via the Software Freedom Conservancy (SFC) itself. Please contact SFC & the CWL - leadership as soon as possible by emailing [commonworkflowlanguage\@sfconservancy.org](mailto:commonworkflowlanguage@sfconservancy.org) - with an initial description of the grant proposal. - * If the SFC is ineligible to apply for this opportunity, or there is another good reason why an external entity should submit - instead of SFC, then approval by the Project *is* needed **and** justification for not submitting via Software Freedom - Conservancy is required. - * The Proposer will document and explain why the Proposal can not be sent by SFC; for example due to geographic or - entity type restrictions. - * The Proposer will supply the aims of the grants, total grant budget and duration. +Project should seek approval for their proposal from the CWL Leadership team and +SFC. + +1. If a proposal indicates the use of CWL but will *not* be contributing + substantially to the CWL Project (e.g. code, documentation, tutorials), then + **n Proposal approval is needed**. + * If the proposed grant is funded, please consider adding (if allowed) + your proposal [to the list of projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) + using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). +2. For a proposal that indicates substantial contributions to the CWL Project, + and/or is in the name of the CWL Project, then there are two paths + * The recommended path is co-develop a proposal with the CWL Leadership Team + (and others); and for submission by SFC itself. Please contact SFC & the CWL + leadership as soon as possible by emailing [commonworkflowlanguage\@sfconservancy.org](mailto:commonworkflowlanguage@sfconservancy.org) + with an initial description of the grant proposal. + * If the SFC is ineligible to apply for this opportunity, or there is + another good reason why an external entity should submit instead of SFC, + then approval by the CWL Leadership Team *is* needed **and** + justification for not submitting via SFC is required. + * The Proposer will document and explain why the Proposal can not be + sent by SFC; for example due to geographic or entity type restrictions. + * The Proposer will supply the aims of the grants, total grant budget + and duration. * The Proposer will supply a form (modeled after [this](https://upload.wikimedia.org/wikipedia/commons/6/6d/GLAM_partnership_evaluation_handout.pdf) - form by the Wikimedia Foundation) to explain the benefits and risks of the proposed contributions to the Project. - * The aims and form will be due 2 weeks before any Letter of Support (LOS) is needed and should be sent to the leadership team - . - A default LOS will be used unless otherwise requested by the Propser. - * If no members of the Project leadership team nor the SFC object to the grant proposal, the proposal will be - approved and the LOS will automatically be provided. - * The members of the CWL Leadership team will keep information about grants that are not funded under a reasonable expectation of privacy + form by the Wikimedia Foundation) to explain the benefits and + risks of the proposed contributions to the CWL Project. + * The aims and form will be due 2 weeks before any Letter of Support + (LOS) is needed and should be sent to the leadership team . + A default LOS will be used unless otherwise requested by the Propser. + * The members of the CWL Leadership Team will keep information + about grants that are not funded under a reasonable + expectation of privacy * Note that a Memorandum of Understanding (MOU) (e.g. - ) - between SFC and the Proposers will need to be developed and signed; plan accordingly. - * If the Proposal is funded, it is required to publicly announce the funded grant on the CWL forum and link to the - proposal (if it is possible to make publicly available) + ) + between SFC and the Proposers will need to be developed and signed; + plan your time accordingly. + * If the Proposal is funded, it is required to publicly announce the + funded grant on the CWL forum (including the main aims) and link to + the proposal (if it is possible to make publicly available) For all these proposal options, Common Workflow Language should be cited using the [proper up-to-date citations](https://www.commonwl.org/specification/#references). From 8f36561882875b376988559b6f2bbb4143de30b2 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" <1330696+mr-c@users.noreply.github.com> Date: Wed, 8 Jun 2022 18:49:29 +0200 Subject: [PATCH 3/5] be explicit about the goal --- grants_policy.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/grants_policy.md b/grants_policy.md index 7f12732..d1255c7 100644 --- a/grants_policy.md +++ b/grants_policy.md @@ -37,7 +37,8 @@ team](https://github.com/common-workflow-language/governance/blob/ddb07b99ae6200 CWL is a [direct project](https://en.wikipedia.org/wiki/Fiscal_sponsorship#Table_comparing_the_models) of SFC: CWL is owned by SFC, and the project's work is implemented by -SFC employees, volunteers, and contractors. +SFC employees, volunteers, and contractors. Therefore this policy exists to document +that requirement and how we will manage it. ## Implementation @@ -48,7 +49,7 @@ SFC. 1. If a proposal indicates the use of CWL but will *not* be contributing substantially to the CWL Project (e.g. code, documentation, tutorials), then - **n Proposal approval is needed**. + **Proposal approval is needed**. * If the proposed grant is funded, please consider adding (if allowed) your proposal [to the list of projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). From ba42d0b68b444ac07114413ee97698488c19a9e9 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" Date: Tue, 11 Jul 2023 12:38:36 +0200 Subject: [PATCH 4/5] clarify and fix logic inversion --- grants_policy.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/grants_policy.md b/grants_policy.md index d1255c7..32ac5f9 100644 --- a/grants_policy.md +++ b/grants_policy.md @@ -1,11 +1,11 @@ -# Policty on requesting and/or acquiring grants/funding for/by the CWL Project +# Policy on requesting and/or acquiring grants/funding related to the CWL Project ## Policy It is a requirement of the CWL fiscal sponsor, Software Freedom Conservancy (SFC), that all applications by any entity for -1) funding of the CWL project's work or -2) in the name of the CWL project +1) **funding** of the CWL project's work or +2) **funding** in the name of the CWL project must be submitted by SFC **unless** an agreement otherwise has been approved by both the CWL Project Leadership Team and SFC. @@ -47,9 +47,11 @@ that involve Common Workflow Language standards (CWL) and the CWL Project should seek approval for their proposal from the CWL Leadership team and SFC. -1. If a proposal indicates the use of CWL but will *not* be contributing - substantially to the CWL Project (e.g. code, documentation, tutorials), then - **Proposal approval is needed**. +1. If a proposal + a) indicates the use of CWL + b) but will *not* be contributing substantially to the CWL Project (e.g. code, documentation, tutorials), + c) and is not submitted in the name of the CWL project. + then **Proposal approval is not needed**. * If the proposed grant is funded, please consider adding (if allowed) your proposal [to the list of projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). From bb81531b51abe5179e2f643a28dfdd52d6b0f592 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" Date: Wed, 19 Jul 2023 14:58:46 +0200 Subject: [PATCH 5/5] add examples --- grants_policy.md | 43 ++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 40 insertions(+), 3 deletions(-) diff --git a/grants_policy.md b/grants_policy.md index 32ac5f9..9522fe7 100644 --- a/grants_policy.md +++ b/grants_policy.md @@ -89,9 +89,7 @@ SFC. For all these proposal options, Common Workflow Language should be cited using the [proper up-to-date citations](https://www.commonwl.org/specification/#references). -\-- - -Expectations for CWL Project Lead or delegate +### Expectations for CWL Project Lead or delegate 1. Maintain private log of notifications @@ -118,3 +116,42 @@ Recording: 4. Work to be done; aspects of the CWL Community Roadmap that overlap/alignment 5. Expected date of application funding decision + +## Non-normative examples: + +### Example A + +Grant proposal mentions the CWL standards +("The workflows delivered will be written in the CWL standard format.") +but otherwise does not mention the CWL project. + +In this case, no coordination nor notification is required. + +If the proposed grant is funded, please consider adding (if allowed) +your proposal [to the list of projects](https://github.com/common-workflow-language/cwl-website/blob/main/content/_data/user-gallery.yml) +using CWL and publicly [announce the funded grant on the CWL forum](https://cwl.discourse.group/c/announcements/6). + +### Example B + +CWL community members identify funding opportunity to do some of the work of the CWL project. + +Then they should contact the CWL Leadership Team to confirm that the opportunity matches the +CWL Community Roadmap, and together they contact Conservancy to send in the proposal +from Conservancy. Payments of grant monies would be controlled by Conservancy +to eligible entities, which can include individuals, companies, and academic institutions. +required. + +### Example C + +CWL community members identify funding opportunity to do some of the work of the +CWL project, but Conservancy is not an eligible recipiant. Maybe USA-based entities +are not allowed; the entire scope of the funding opportunity is much bigger than the CWL project +itself; or other requirement is not met. + +Like in Example B, the CWL Leadership Team should still be contacted. The CWL Leadership Team +(or its delegate) will confirm the fit of the proposal to the CWL Community Roadmap +and will confirm with Conservancy about the eligibility issue. Will Conservancy's +approval, external entities could apply to do the work of the CWL Project with a +written Memorandum of Understanding of how the work will be coordinated. + +If sub-contracting to Conservancy is possible, then that should be pursued first.