-
Notifications
You must be signed in to change notification settings - Fork 2
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FundOSS Round Deux: Features, Failures and Fixes #42
Comments
Great list @BenJam! If I could add a couple other ideas
Many of these ideas are relevant to the Open Collective product and are similar to what I previously logged here opencollective/opencollective#2232 (comment) |
This will probably increase donations from the Gitcoin/Bitcoin/Web 3.0. communities for subsequent FundOSS campaigns https://blog.opencollective.com/support-open-source-software-using-crypto/ |
The following site provides some really nice inspiration for both the FundOSS and Open Collective platforms - here is some functionality 'not' yet listed above.
|
Circling back to this issue as I mentioned FundOSS as a potential project for the OSC Working Group that's taking shape in #opensource (Open Collective Slack). @BenJam mentioned the following when it came up as a potential program -
This was my response from the same Slack discussion
To me (especially when considering all the success OSC's partner has had with Gitcoin Grants, we could solve problems with the funding model and contribute to platform improvements by 1) looping in some of the original partners at Gitcoin and 2) engaging community contributors/partners/funders via the working group we're now in the process of forming. 🎉 |
Okay, I thought a bit about the good parts and bad parts after talking with and reading the comments from @gusaus and @BenJam. Things that would be really nice to retain:
Things that were problematic to avoid:
My proposal/suggestion: Establish a permanent program for distributing funding to OSC collectives via quadratic funding. Rather than operate a separate platform, base the weighting on monthly recurring donors and donations to a project, and set some basic minimum standards of inclusion: Presumably collectives should be pushing code within some threshold of recent activity, maybe set expectations of participating in OSC communications actively or something too. Then, instead of setting up for a particular donation drive, folks can encourage funding their own collectives and communicating through those collectives, but programs like Gitcoin Grants can occasionally roll through and disburse some amount of funding to support open source software and it gets distributed to active OSC collectives. Basing the weighting on donors with recurring subscriptions will incentivize stable funding, and help drive funding that happens persistently as opposed to just during specific rounds of activity. Regarding project exposure, I think OSC could/should expand highlighting projects which are participating and in need of support. |
Piggybacking on @ocdtrekkie's great suggestions with some of mine from previous discussions in #opensource and #fundoss.
A separate platform seems expensive/inefficient, but would it be feasible to incorporate all the features into https://github.com/opencollective/opencollective? What if the functionality discussed in this issue was built into the new site for https://www.oscollective.org/? Apparently, a new site is in the works, but I'm not sure how OSC collects and incorporates feedback from their collectives.
Centralizing activity in #opensource, while at the same time leveraging other Slack (#general, #fundraising, #sustainoss, etc.) and marketing channels (Sustain, Gitcoin, etc.) would help solve this problem. We could work with Gitcoin to incorporate additional knowledge and processes (wherever relevant and appropriate) they've accumulated from running successful rounds over time.
Those problems would be addressed by a well-defined process + more engaged community (the latter could be accomplished by enabling a #community-working-group member to complete opencollective/opencollective#1996 with a bounty) Personally, I'd like to see a combination of official rounds (again, I think we could look at Gitcoin for structure and selection criteria (I 'believe' anyone can opt-in - which seems preferable) + community-organized fundraisers. Again, I think OSC specific fundraisers via https://www.oscollective.org/ would be advantageous - especially if other functionality (like a marketplace/job board and partner program) that helps connect projects to resources were also available. It seems like FundOSS (as a Fund) could be better utilized by creating 'projects' for rounds or campaigns around specific interest areas, categories, or software types. That may encourage large companies in specific interest areas or foundations with industry-specific grants to fund. Finally - IF cost and team resources (developer, organizer, marketing, etc) were indeed blockers, could we create a 'project' specifically for platform improvements and other resources we'd need? With a budget, the OSC working group could help the OSC team wherever there's a need. Would be good to have input from other pilot participants and OSC collectives. Would getting this program back on track be beneficial? |
Maybe there was some discussion on one of the monthly OSC calls, but it doesn't seem like there's been any input from OSC about the future of this program (even though folks occasionally inquire in Slack). Now it looks like https://fundoss.org/ is down. Does that mean OSC has officially shelved the program? If yes, could the community help bring it back as suggested in the past couple comments? #42 (comment) #42 (comment) |
Circling back here after coming across what might be a more advanced platform we could leverage for a revival? Not sure if anyone from OSC has talked with @owocki about gitcoinco/skunkworks#284 Would love to touch base and see if there's something we could leverage and contribute to. |
Following up on my last comment, I finally was able to connect with @owocki after leaving this followup in https://community.supermodular.xyz/ about the platform they've been developing.
To which I asked some followup questions:
After mentioning they'd love to support, I sent a follow up email (as requested) to get his recommendations on next steps. Haven't heard back so I thought I'd just direct everybody back here since we'll need input from @BenJam @zherring and the other original organizers/partners to gauge interest and potential involvement in a FundOSS revival. If for whatever reason they're not interested/able, would it be possible to for new partners and organizers to take over this Github org and https://opencollective.com/fundoss? |
@gusaus appreciate the tag! I'm currently COO/CPO of a startup and a new dad, so my time is pretty restricted at the moment. Cannot contribute many hours but happy to provide input where it makes sense! Excited to hear folks are wanting to contribute to push this work forward! |
As most folks looped into this issue are aware we're in the process of drafting a proposal for the Drupal Association to leverage Open Collective and Quadratic Funding as a way to reach/surpass their fundraising goals (see this comment for context). Since we're essentially proposing to create a flavor of FundOSS (Fund + Quadratic Funding platform) with most of the key FundOSS people/partners already involved (or showing interest), I'd like to suggest (again) that we revisit #42 (comment) and other comments and cobble together a plan to revive FundOSS by forking/extending/contributing to https://github.com/supermodularxyz/simplegrants (as opposed to fixing https://github.com/FUNDOSS/fundoss). As @owocki noted in the Drupal proposal comments...
Why not gather together all the interested contributors/partners, plan, and pool resources to finish/test a forkable/skinnable MVP? |
Had a short Slack convo with @BenJam after sending out the following update about the Drupal proposal and another potential opportunity for a FundOSS round.
Ben mentioned they 'would' support a fundraising effort through the platform after making some of the improvements mentioned in this issue. To which I mentioned @owocki's offer of platform support (see #42 (comment) and the related comment thread in the Drupal proposal). @BenJam Considering we've essentially accepted that offer and have been planning on bringing on new partners to provide support (as mentioned in my email update), would it make sense to unify our collaboration/partnership around funding experiments as FundOSS but use the new Simplegrants platform? |
Chiming in here, as @gusaus has mentinoed me a few times as the CTO over at the Drupal Association. Certainly I'm interested in finding a way to enable the Drupal project to participate in future ventures here, and to cross promote the idea. IMO - defining the minimum viable product to launch the next experiment is always the best way forward, and then continuing to iterate. There are a lot of possible avenues as described extensively by @gusaus, and even if we can't achieve all aspects, wherever there is consensus and capacity I'm happy to participate. |
@hestenet Unless I'm misunderstanding @BenJam's email and Slack comments, I think we have the green light to revive and extend FundOSS by building features/improvements into the https://github.com/supermodularxyz/simplegrants MVP that @owocki @easonchai are supporting. Community Contributor Group (which includes members connected with larger orgs/communities with capacity) can fill contributor and support needs assuming the new product owners can join us to lead and advise. |
Unfortunately we got word from @owocki that @easonchai is no longer available to support simplegrants and we're not in a position to take over w/out any funding/direction/involvement from the product owners or original partners. With at least two of the largest open source projects/communities/economies/digital public goods (and Open Collective users/investors) showing interest in participating and a larger role in the ecosystem, I'm hoping the partners and providers see the value of playing some sort of realistic/mutually beneficial role in enabling Quadratic/Democratic Funding (with some of the above fixes/improvements in place) and other funding experiments under the FundOSS umbrella. With the product owner and a skilled PM onboard we could probably updating our needs/requirements in supermodularxyz/supermodules#1 and post a RFP or bounty (using the format similar to Mautic) as a project on our Funding Tools collective. |
Quick update on the last comment to say that we've picked the discussion with @owocki (primarily in this Twitter thread) about leveraging/extending the Simple Grants platform he helped get close to MVP supermodularxyz/simplegrants#1 while at https://supermodular.xyz/ for our planned FundOSS comeback (and expansion). Skim through the Twitter thread and you'll see some productive/promising input from multiple folks at https://www.gitcoin.co/ (the key partner and inspiration for the FundOSS pilot. Main reason for this is Kevin is back at the company he founded and we're talking about a variety of ways to collaborate and partner. Helping get SimpleGrants to a point where we can use for a variety of WordPress, Drupal, and Open Collective ecosystem fundraisers (all leveraging FundOSS and Open Collective) we're planning around GivingTuesday and the duration of giving season could be an entry point for a subsequent platform and program collaboration and partnership. To do this, we need to find someone with the following skills (the following is from @easonchai, the former lead dev) along with a product/product manager that could (ideally) work with Kevin to update the scope and estimate the funds needed to finish the job.
If that's you - or if you know of anyone - please comment here or join #fundoss (in Open Collective Slack) and say hello! |
Thanks for your continued work on this. FundOSS was immensely helpful to us, and we are currently trying to raise funds for an important project. |
@ocdtrekkie As the only other community/collective benefactor and advocate in this discussion, I appreciate the show of support. As I told @BenJam and other Open Collective leaders in this related Slack Canvas discussion, I think having OSC (and ideally other Open Collective entities) involved as a partner, collaborator, or just an enabler would empower orgs and individuals representing in their #opensource channel and ecosystem to support and sustain as a community driven effort. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm dropping an issue here to compile feature requests, issues that were highlighted and potential fixes. I'll probably break this issue out into other issues once we get into prioritisation:
Ideas
Issues
The text was updated successfully, but these errors were encountered: