I'm looking to build out the Free Fridge & Community Pantries in my town.
I'll continue to update this thread with my progress.
So, the idea is to have nodes throughout town that allow folks to "Give a Food, Take a Food". Similar to "Little Free Libraries" are to books. Folks who have extra food can drop it off there, folks who need food can grab it there.
The focus here is mutual aid, not charity. So, absolutely, if you are food insecure or hungry, utilize it, right. Beyond that though, this is a great piece of infrastructure to share extra food with your neighbors. I will go down to the free fridge we have in town, drop off some of my extra produce that I have grown, and then pick up a can of black beans if I need it for dinner that night. We're meant to contribute AND utilize the free fridge.
There are many ways to create and maintain free fridges, from something as simple as a small box or outdoor cabinet on up to full stand up refrigerators and freezers with an outdoor pantry.
In general, you want it to be a couple of things:
- Accessible to the public
- 24 hours a day, 7 days a week
- Unmanned
- No restrictions on who can utilize it or take food from it - it should NOT employ any means-testing
- Receive shelf stable food and/or refrigerated food and/or frozen food
Further, you can break up the different groups that are involved in the free fridge:
- The Host
- The Maintainers
- The Community
The Host - provides a location for the fridge and pantry to be installed and accessed. They also provide electricity to power the fridge/freezer
The Maintainers - this would be my group. We source, install, maintain, repair, and clean the fridge, freezer, and pantry.
The Community - contributes food to and utilizes food from the fridge and pantry. This is important. While the host provides the site and the Maintainers keep it operational, neither one has to stock food or coordinate utilization. The community does it themselves.
Having it split up like this is nice. Can folks from the Host group maintain it? Certainly. But extrapolating it allows for ease of use.
So. Keeping it stocked is up to the community. I've seen it stocked by gardeners who have extra produce (Zucchini turns folks into socialists is the joke! You just grow sooooo much you end up LOSING FRIENDS when you try to push it off on others!). I've seen it stocked through Food Rescue efforts. Some families buy extra from the grocery store and this is a great place to drop it off. I've even seen the local Food Bank drop off extra food when they had left overs from a food distribution.
Keeping it utilized is also easy. You don't want the fridge to stay stocked, right. You want it to stay in the fridge for as short a period of time as possible before someone comes and grabs it. Heck! I've seen a food rescue of fresh produce from a farmer's market vendor be dropped off at a free fridge and then claimed by several families even before it had a chance to be placed physically into the fridge! This is ideal. One fridge and pantry needs to serve the local neighborhood. That's many many families. It can only do so if its filled up and then utilized multiple times a day.
Next post, I'll put some resources on starting your own in your town.
#freeFridge #foodScarcity #foodSecurity #postScarcity #solarPunk #mutualAid
@tito_swineflu There are a lot of companies in similar spaces where the challenges of the underlying software are amenable to having a good UI sitting on top to make it easier to use.
So you separate the service out as its own entity where you can hire and house the expertise for running such a system effectively, and you can provide that service for a lower cost than most companies would pay to staff their own internal version of it.
I think in the past this sort of thing was done via bundling, e.g. how Microsoft and Google provide email with other services. These days it's more à la carte, though with the risk of data exposure since these companies need to staff their own security engineering.
Examples I can think of: Slack (technically a Salesforce bundle I suppose), Snowflake, Fastly, Honeycomb, Rippling, Airbyte
I often think of it as a company version of Service-Oriented Architecture, though I guess the metaphor probably comes from the business practice rather than the other way around
@silverpill
> But first, an automated implementation counting will be added
That sounds useful for sure. But note I specified 3 *unrelated* implementations. If 3 soft forks of a popular codebase (eg 3 *keys), that doesn't tell us nearly as much about whether this FEP is suitable for general use.
So either that needs to be factored in to automated counts, or we'd still need a human admin marking an FEP as IMPLEMENTED, based on their assessment of the independence of those counted.
As I'm nearing the release of @TangerineUI 2.0 (which will come out soon after Mastodon 4.3 is released), I feel it's a good time to remind everyone that I’ve invested an insane amount of time in creating this theme over the past year.
Sure, it is “just a CSS file,” but it's also the result of hundreds of hours spent carefully crafting a nicer visual experience, free for all to use.
So, if you love this theme and actively use it every day, I would be super grateful if you would consider leaving a tip on my Ko-fi page 💛 https://ko-fi.com/nileane
Hey everyone!
I'm working on a video to see what the Linux community (or at least people who follow me) actually use.
So, I created a little form, hosted on my Nextcloud (hopefully it's up to the task...)
It's only up for 2 days, so don't hesitate to share it around, it will help me "touch grass" and see if my preconceived notions are confirmed, or invalidated!
https://nextcloud.thelinuxexp.com/index.php/apps/forms/s/XQRzMrs8QTtCjDfSyP4koA9o
Of course, it's all anonymous, no personal data, it's just for the purposes of creating the video.
... But 99.9% of software companies don't have this quality of tooling. They don't have this confidence in deploys. They don't have the resources to "internal fork" every dependency they need and they're not paying most of these public projects they use.
So they need to make some concessions.
The first concession is typically "shrink wrapping" of dependencies. You declare the version of your dependencies and the build system pulls in a consistent version of those /2
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.