Also, overview and discussion at the yesterday's governance meeting: https://youtu.be/R80Rv6G-Oww?t=2806
On Thursday, June 4, 2020 at 11:59:34 AM UTC+2, Oleg Nenashev wrote: > > JEP draft is ready for review: https://github.com/jenkinsci/jep/pull/286 > > On Saturday, April 4, 2020 at 10:11:50 PM UTC+2, Oleg Nenashev wrote: >> >> Meanwhile, everybody is welcome to try out >> https://funding.communitybridge.org/projects/jenkins which is fully set >> up for evaluation/feedback purposes. >> >> On Saturday, April 4, 2020 at 10:10:13 PM UTC+2, Oleg Nenashev wrote: >>> >>> Status update here: I did not forget about this topic, and am still >>> planning to submit the JEP and new PoC for ComunityBridge, it was just >>> delayed due to other emergencies in my personal life and in the Jenkins >>> project (and overall lack of time). I plan to work on that in parallel with >>> helping the Core Release Automation project, but I cannot guarantee the >>> exact delivery date. >>> >>> BR, Oleg >>> >>> On Saturday, January 18, 2020 at 10:33:16 PM UTC+1, Marky Jackson wrote: >>>> >>>> I am interested in mentorship and will ping you offline >>>> >>>> On Jan 18, 2020, at 11:09 AM, Oleg Nenashev <[email protected]> wrote: >>>> >>>> >>>> Hi all, >>>> >>>> Just an update in this thread, I have set up the donations page >>>> prototype: https://funding.communitybridge.org/projects/jenkins >>>> As discussed at the Advocacy&Outreach SIG meeting on Thursday, we will >>>> make additional review with CDF to ensure that CommunityBridge Funding is >>>> fine for the CDF projects. >>>> I am pretty sure it will be OK since many CNCF projects are already >>>> represented on this Linux Foundation portal, but let's see. >>>> >>>> So now we have two landings: >>>> >>>> - Funding <https://funding.communitybridge.org/projects/jenkins> >>>> - Mentorship >>>> >>>> <https://people.communitybridge.org/project/bce45251-1ff4-4131-9699-0a0017b31495/> >>>> >>>> To whomever interested in mentorship, right now we can run mentorship >>>> programs with stipend and without one. There were some mentee applicants >>>> since Nov whom we could review (run a project there or invite to GSoC, for >>>> example). If you are interested, ping me in >>>> https://gitter.im/jenkinsci/advocacy-and-outreach-sig >>>> >>>> Best regards, >>>> Oleg Nenashev >>>> >>>> >>>> On Thu, Jan 16, 2020 at 4:19 PM Oleg Nenashev <[email protected]> >>>> wrote: >>>> >>>>> Beta testing of the new funding page was approved at the yesterday's >>>>> Governance >>>>> Meeting <https://jenkins.io/project/governance-meeting/>, thanks to >>>>> all for the feedback! >>>>> I will get the agreements implemented and report back once the >>>>> reference implementation is ready. >>>>> >>>>> >>>>> On Friday, December 27, 2019 at 11:47:21 AM UTC+1, Ullrich Hafner >>>>> wrote: >>>>>> >>>>>> +1 >>>>>> I like the idea as well. >>>>>> >>>>>> Am 26.12.2019 um 13:35 schrieb Oleg Nenashev <[email protected]>: >>>>>> >>>>>> Hi all, >>>>>> >>>>>> I am working on the Jenkins donations page >>>>>> <https://jenkins.io/donate/> update at the moment (INFRA-2396 >>>>>> <https://issues.jenkins-ci.org/browse/INFRA-2396>), and I would like >>>>>> to propose some changes there so that we can have a funding source once >>>>>> SPI >>>>>> retires the Jenkins donations as a part of our transition to CDF. >>>>>> Jenkins >>>>>> funding helps us to run outreach programs and to cover some >>>>>> infrastructure >>>>>> costs, and as a board member I think it is really important to keep it >>>>>> running and, ideally, to facilitate funding and using the money in the >>>>>> project. >>>>>> >>>>>> *TL:DR:* Let's use CommunityBridge >>>>>> <https://funding.communitybridge.org/> as a SPI replacement to raise >>>>>> funds. It is maintained by Linux Foundation, and it is recommended for >>>>>> all >>>>>> projects within LF or sub-foundations like CDF. Examples: CHAOSS >>>>>> <https://funding.communitybridge.org/projects/chaoss>, Manjaro >>>>>> <https://funding.communitybridge.org/projects/manjaro> or KiCAD >>>>>> <https://funding.communitybridge.org/projects/06d36004-70a3-4f1f-8ae3-d0b2dd98815d> >>>>>> >>>>>> >>>>>> *Background.* Jenkins project operates thanks to contributions and >>>>>> sponsorship (infra, meetups, swag, etc, etc.). Historically we did not >>>>>> have >>>>>> high cash flows in the project, we mostly spend money on infra and on >>>>>> outreach programs (swag, travel grants, Outreachy and Community Bridge >>>>>> in >>>>>> 2019). Sponsorship covered the most of our "big" expenses (e.g. Azure, >>>>>> meetup.com, contributor summits, etc.), but there is a tendency to >>>>>> formalize such donations through CDF. Currently sponsorship through CDF >>>>>> is >>>>>> a lengthy process not suitable for small donations, and it would be >>>>>> great >>>>>> to have a simple process so that we can raise money to facilitate the >>>>>> changes in the project. >>>>>> >>>>>> *Current state* >>>>>> >>>>>> - https://jenkins.io/donate/ documents the donations policy. >>>>>> - This page has not been updated for a while, working on it >>>>>> - This page basically designates donations to be consumed for >>>>>> Jenkins Infra, >>>>>> - There is an explicit statement that "Your contribution is >>>>>> not used for paying personnel.". Arguably, this is what we do for >>>>>> Outreachy >>>>>> and CommunityBridge though stipend for outreach projects != salary >>>>>> - Jenkins uses SPI to accept donations. Soon SPI will no longer >>>>>> accept donations to Jenkins due as a part of the transition to CDF. >>>>>> The >>>>>> exact date is TBD, but the decision has been already made in Spring >>>>>> 2019 as >>>>>> communicated by Tracy Miranda >>>>>> - We also accept donations through ffis.de, but the status is >>>>>> unknown (WEBSITE-703 >>>>>> <https://issues.jenkins-ci.org/browse/WEBSITE-703> tracks the >>>>>> investigation). It is also not clear whether they have Jenkins money >>>>>> on >>>>>> their accounts and how to access them >>>>>> - CommunityBridge Funding site >>>>>> <https://funding.communitybridge.org/projects/jenkins> is enabled >>>>>> for mentorship donations only as a part of Governance Meeting >>>>>> decisions in >>>>>> July 2019). We used it to dry-run the JCasC Dev Tools project >>>>>> <https://jenkins.io/projects/jcasc/dev-tools/> this year, and it >>>>>> works pretty well (except the SPI => LF transfer part which was the >>>>>> major >>>>>> obstacle for the mentee payments). >>>>>> >>>>>> >>>>>> *Suggested changes* >>>>>> >>>>>> - Update "Your contribution is not used for paying personnel " to >>>>>> be explicit that the Jenkins project might use money to sponsor >>>>>> limited-term work on the project: outreach initiatives, addressing >>>>>> mission-critical topics (e.g. INFRA needs) or facilitating projects >>>>>> required for the Jenkins future' (e.g. JCasC, Cloud Native Jenkins, >>>>>> etc.) >>>>>> - All such projects will need to be approved by the Governance >>>>>> meeting >>>>>> - The payments should be limited to reasonable amounts so that >>>>>> it is "facilitating contributions / mentorship" but not a >>>>>> fully-paid job. >>>>>> E.g. GSoC stipends >>>>>> >>>>>> <https://developers.google.com/open-source/gsoc/help/student-stipends> >>>>>> could >>>>>> be used as a reference >>>>>> - Enable CommunityBridge-based sponsorship for all available >>>>>> categories: Development, Marketing, Meetups, Bug Bounty, Travel and >>>>>> Documentation. We update documentation to mark it as a default >>>>>> donations >>>>>> way. >>>>>> - It will enable organization payments and also small monthly >>>>>> donations by individuals in the Patreon style. E.g. see CHAOSS >>>>>> <https://funding.communitybridge.org/projects/chaoss>, Manjaro >>>>>> <https://funding.communitybridge.org/projects/manjaro> or KiCAD >>>>>> >>>>>> <https://funding.communitybridge.org/projects/06d36004-70a3-4f1f-8ae3-d0b2dd98815d> >>>>>> - As a risk for this plan, Core Infrastructure Initiative >>>>>> <https://www.coreinfrastructure.org/> certification is >>>>>> expected for projects on Community Bridge in long term. I got >>>>>> clarification >>>>>> from Linux Foundation that it is not a blocker at the moment. See >>>>>> INFRA-2396 <https://issues.jenkins-ci.org/browse/INFRA-2396> for >>>>>> the context >>>>>> - CommunityBridge allows donations to be designated to >>>>>> particular areas so that donors can decide what they sponsor >>>>>> - In the future I would suggest to allow targeted sponsoring >>>>>> of big changes as outreach projects. It is way of the scope for >>>>>> this >>>>>> thread, so I will create a follow-up once I am ready >>>>>> - Mark SPI-based donations as deprecated. Even if they continue >>>>>> to work, reimbursements from SPI and transferring money from SPI to >>>>>> Linux >>>>>> Foundation is a lengthy process due to the SPI activist-driven model. >>>>>> SPI >>>>>> helped the project A LOT, but the payments experience should improve >>>>>> since >>>>>> Linux Foundation has full-time employees responsible for payments >>>>>> - Investigate the status of ffis.de and update the documentation >>>>>> accordingly. Mark as deprecated in the case of doubt >>>>>> >>>>>> This proposal does not include raising visibility of the donations >>>>>> page. But we can definitely do it once the new flow is set up and >>>>>> battle-tested. >>>>>> >>>>>> If there is a consensus and approval at the next governance meeting, >>>>>> I will proceed by setting up a PoC and creating a JEP draft for funding. >>>>>> >>>>>> Thanks for your time, >>>>>> Oleg Nenashev >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Jenkins Developers" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDPkPHSCPao3Nw1SqtykPhTKpaqMnA8ryT31VZVUziXzw%40mail.gmail.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDPkPHSCPao3Nw1SqtykPhTKpaqMnA8ryT31VZVUziXzw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "Jenkins Developers" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/jenkinsci-dev/iLutO2X0bdg/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/6d970ba6-501a-46fe-93cd-47b44b33f50a%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/6d970ba6-501a-46fe-93cd-47b44b33f50a%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Advocacy and Outreach SIG" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAPfivLAwSEd%2BSVa%3DvaC_i4hGWLm-meDfaV41Q2nW-ZaNg8-4GA%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAPfivLAwSEd%2BSVa%3DvaC_i4hGWLm-meDfaV41Q2nW-ZaNg8-4GA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/080ad64e-c90c-4955-8f68-4ffb27cd83c0%40googlegroups.com.
