11ty / 11ty-community

A database of #BuiltWithEleventy web sites.
https://github.com/11ty/11ty-community/issues/new/choose
41 stars 25 forks source link

What should happen to the budget available in the Open-Collective 11ty account? #78

Closed johanbove closed 2 months ago

johanbove commented 2 years ago

Was wondering about the open-collective account for 11ty. I've been personally contributing for a while, amongst other people; but haven't seen any re-use of the cash in the account. Why hasn't there been?

cf. https://opencollective.com/11ty

πŸ’‘11ty has a neat bunch of dependencies that could use some support.

pdehaan commented 2 years ago

I vote for spending it on custom possum themed adidas track suits for @zachleat. Possibly a matching casual Kangol Furgora, budget permitting. I think he could pull it off as his new "signature look". 🀷

johanbove commented 2 years ago

Will do a "npm fund" on a clean install - previously this contained my own site's list of projects I should support. Sorry for that.

Here's the "npm fund" output for "version": "2.0.0-canary.4",

eleventy (master) πŸ––  $ npm fund
https://opencollective.com/11ty
β”‚ └── @11ty/eleventy@2.0.0-canary.4, @11ty/eleventy-dev-server@1.0.0-canary.7, @11ty/eleventy-utils@1.0.1, @11ty/eleventy-plugin-syntaxhighlight@4.0.0, @11ty/eleventy-plugin-vue@1.0.0-canary.8, @11ty/eleventy-assets@1.0.6
β”œβ”€β”€ https://github.com/sponsors/sindresorhus
β”‚   └── @sindresorhus/slugify@1.1.2, @sindresorhus/transliterate@0.1.2, escape-string-regexp@4.0.0, multimatch@5.0.0, get-stream@6.0.1, is-stream@2.0.1, onetime@5.1.2, cli-truncate@2.1.0, log-update@4.0.0, ansi-escapes@4.3.2, type-fest@0.21.3, arrify@3.0.0, callsites@4.0.0, cli-truncate@3.1.0, is-fullwidth-code-point@4.0.0, string-width@5.1.2, del@6.0.0, globby@11.1.0, p-map@4.0.0, figures@4.0.1, escape-string-regexp@5.0.0, is-unicode-supported@1.2.0, globby@13.1.1, slash@4.0.0, indent-string@5.0.0, matcher@5.0.0, mimic-fn@4.0.0, p-event@5.0.1, p-timeout@5.0.2, p-map@5.3.0, aggregate-error@4.0.0, clean-stack@4.1.0, pkg-conf@4.0.0, find-up@6.3.0, locate-path@7.1.0, p-locate@6.0.0, p-limit@4.0.0, yocto-queue@1.0.0, load-json-file@7.0.1, plur@5.1.0, pretty-ms@7.0.1, serialize-error@7.0.1, type-fest@0.13.1, make-dir@3.1.0, hasha@5.2.2, p-limit@2.3.0
β”œβ”€β”¬ https://paulmillr.com/funding/
β”‚ β”‚ └── chokidar@3.5.3
β”‚ └── https://github.com/sponsors/jonschlinkert
β”‚     └── picomatch@2.3.1
β”œβ”€β”€ https://opencollective.com/liquidjs
β”‚   └── liquidjs@9.36.0
β”œβ”€β”€ https://github.com/sponsors/typicode
β”‚   └── husky@7.0.4
β”œβ”€β”¬ https://opencollective.com/lint-staged
β”‚ β”‚ └── lint-staged@12.3.7
β”‚ β”œβ”€β”€ https://github.com/sindresorhus/execa?sponsor=1
β”‚ β”‚   └── execa@5.1.1
β”‚ β”œβ”€β”€ https://github.com/sponsors/ljharb
β”‚ β”‚   └── object-inspect@1.12.0, resolve@1.22.0, is-core-module@2.8.1, supports-preserve-symlinks-flag@1.0.0, is-regex@1.1.4, call-bind@1.0.2, get-intrinsic@1.1.1, has-symbols@1.0.3, has-tostringtag@1.0.0
β”‚ └── https://github.com/chalk/supports-color?sponsor=1
β”‚     └── supports-color@9.2.2
β”œβ”€β”€ https://github.com/prettier/prettier?sponsor=1
β”‚   └── prettier@2.6.1
β”œβ”€β”€ https://github.com/sponsors/isaacs
β”‚   └── rimraf@3.0.2, glob@7.2.0
β”œβ”€β”€ https://github.com/chalk/chalk?sponsor=1
β”‚   └── chalk@5.0.1
β”œβ”€β”€ https://github.com/sponsors/feross
β”‚   └── run-parallel@1.2.0, queue-microtask@1.2.3, fromentries@1.3.2
β”œβ”€β”€ https://github.com/chalk/ansi-styles?sponsor=1
β”‚   └── ansi-styles@6.1.0
β”œβ”€β”€ https://github.com/sindresorhus/emittery?sponsor=1
β”‚   └── emittery@0.10.2
β”œβ”€β”€ https://github.com/sindresorhus/mem?sponsor=1
β”‚   └── mem@9.0.2
β”œβ”€β”¬ https://github.com/chalk/strip-ansi?sponsor=1
β”‚ β”‚ └── strip-ansi@7.0.1
β”‚ └── https://github.com/chalk/ansi-regex?sponsor=1
β”‚     └── ansi-regex@6.0.1
β”œβ”€β”€ https://github.com/chalk/wrap-ansi?sponsor=1
β”‚   └── wrap-ansi@7.0.0
β”œβ”€β”€ https://github.com/avajs/find-cache-dir?sponsor=1
β”‚   └── find-cache-dir@3.3.2
└─┬ https://opencollective.com/babel
  β”‚ └── @babel/core@7.17.8
  └── https://opencollective.com/browserslist
      └── browserslist@4.20.2, caniuse-lite@1.0.30001323
johanbove commented 2 years ago

Idea would be to find that one person in Nebraska who could use some support: cf. https://xkcd.com/2347/

pdehaan commented 2 years ago

Idea would be to find that one person in Nebraska who could use some support: cf. xkcd.com/2347

Wait, isn't @zachleat in Nebraska? /quickly checks how long he has been maintaining 11ty!

npm info @11ty/eleventy time.created # 2018-01-09T14:36:27.855Z

johanbove commented 2 years ago

Case settled then.

zachleat commented 2 years ago

Just as disclosure this question was discussed on JSParty!

Quoting from the transcript:

Yeah, that’s valid criticism. I don’t really feel like I have a great story for that. I feel like the other side of the coin is that some of these projects are better about maintainers removing the funds and not really telling a good story about what the funds are being used for. There’s a lot of trust that goes into donating to an open source project, and I would say that I haven’t seen too many folks cancel their Open Collective contributions… Because I do really want folks to understand that it is an investment in the longevity of the project. So I don’t consider this Netlify arrangement to be something that will probably exist for ten years. I mean, if it did, that would be awesome, but I think if we’re all honest, I don’t think that that will be a thing that will exist in ten years.

That is kind of a fallback strategy for me at this point, and I’m open to discussing it with folks if they have concerns about that. But I do feel that my mindset is changing a little bit with this new arrangement at Netlify, and I’ll probably start to use the money in a more community-organized way moving forward, as I feel more comfortable with the arrangement moving forward.

All that said, I absolutely would upvote some funding to liquidjs and sindresorhus.

zachleat commented 2 years ago

11ty is now a backer of liquidjs https://opencollective.com/liquidjs

pdehaan commented 2 years ago

Fun idea... Here's a snippet from Sara Soueidan's Practical Accessibility latest newsletter update:

Over this past year, my progress on the course was a bit slower than I wanted it to be. I'm a freelancer, and since this course is not currently sponsored, the time I spend working on it takes away from my time working on client projects. …

As some of you may know, I am using Eleventy to create the course Web site. I chose not to use a course platform because of accessibility as well as flexibility and customizability limitations. There were also limitations related to things like payment portals, most of which don’t work for someone living in Lebanon.

With the custom site I built, I have full control over everything β€” content, layout, design, and everything in between. (I am considering releasing the site as an 11ty template after the course is finished!)

11ty could become a/the official sponsor for the Practical Accessibility premium course.

Free tagline: 11ty :heart: a11y

zachleat commented 2 years ago

cc @SaraSoueidan can you send over options for that? is sponsorship still available?

Zearin commented 1 year ago

Love @SaraSoueidan’s work. Before #a11y her articles taught me so much about #SVG. She’s a fantastic teacher. And she’s very indie-webβ€”very aligned with 11ty.

Great choice.

rdela commented 3 months ago

This could probably be closed now between https://www.11ty.dev/blog/sustainability-fundraising/ + https://conf.11ty.dev

As foretold by Johan, Zach’s 11ty Conf talk appropriately contained the XKCD 2347 reference. (Someday Eleventy will finally break for good and we'll have a long period of scrambling as we try to reassemble civilization from the rubble.)

rdela commented 3 months ago

There was also some funny discussion of XKCD 2347 at the end of https://changelog.com/jsparty/325 πŸ‘ @nicknisi + @jerodsanto

zachleat commented 2 months ago

Thank you @rdela!