/jects

The projects you can sign up for.

Each request is written by the project in its own words and signed by whoever will operate the system. If a request says "urgent", "etc." or "a platform", it is badly written and doesn't go up.

Requests come through two doors: a fessional brings a socio-environmental organization from their city, or the project writes in below, in "What it takes". Once here, anyone can sign up for any of them. Pay depends on each project; if there is any, it is written in the request before starting.

No request is signed yet. The fields in brackets are filled in by each project. Meanwhile, what there is is signing up in /fessionals.

pedido-001

not signed yet in progress

A logistics and sales system for a network of agroecological producers and consumers

Who is asking: A network of agroecological producers and consumers.
Who brought it: A fessional who has been building it since before sidepro existed.
The problem: Every two weeks, orders have to be coordinated between a network of producers from Córdoba and other provinces and the families who buy. Loading products, putting the order form together, collecting orders, sending pick lists, receiving at the warehouse, adjusting shortages, delivering and settling were manual steps, spread across spreadsheets, WhatsApp and email.
What exists today: Each round depended on a single person, who handled all the information between more than 50 producers and 80 to 100 families. Before, a Google form took the orders and the rest was done by hand, between WhatsApp, Gmail and typing into spreadsheets. Today, custom forms in plain HTML and JavaScript, served by GitHub Pages, have fully replaced the Google form. Google Sheets works as the database of an automated system, not as a record edited by hand: more than thirty sheets (producers, products, consumers, rounds, orders, items, pick lists, receipts, adjustments, settlement, leftovers, stock, payments, change log). Around twenty Make scenarios, triggered by webhook, move data between forms and sheets; email and a WhatsApp group send the notices.
What has to keep running: That the network's team can open and close a full round, from loading products to settling with producers, guided step by step by the system and operable by whoever is in charge, with no bottlenecks or long manual data entry. That the system covers every operational case that can come up (shortages, adjustments, uncollected orders, leftovers, corrections) so the record is consistent and reliable end to end.
Who operates it: A person on the network's team, who already runs rounds on her own. Alternate: anyone else on the team; the system is simple and guides itself.
Built with: Plain HTML and JS forms on GitHub Pages · Google Sheets as database · Make (webhook scenarios, paid plan) · Google Drive for backups · email and WhatsApp for notices. The network pays for Make and its accounts. Next step: moving the database from Google Sheets to Supabase or similar. Plan B, if Make changes its price, goes in MANTENIMIENTO.md.
Hours: 4 a week, 12 weeks, as a pair. It was already under way when sidepro was born; it joined the method at stage 4.
License: The form code is already MIT, chosen by the network. The spreadsheet and the scenarios are documented in the network's repo.
Funding: Yes, in kind. An hourly value in pesos was agreed according to the network's real possibilities, and it was paid in agroecological food managed by the network. No invoice, since it was an exchange. Milestone: the system launched and used for a full round, replacing the previous one. It is not a precedent: it is one possible kind of agreement.
Stage: 4 Solo · of five, per RFC-001

The site's first real request. The operator already runs rounds; what's left is the handover. Sign up for this request

pedido-003 · candidate

not signed yet candidate

A management system for a community football school and soup kitchen

Who is asking: A community football school and soup kitchen.
Who brought it: A fessional from the core, who knows them. They haven't talked about the system yet: this is a candidate, not a request.
The problem: [The project says it when we talk to them; nobody writes it for them.]
What exists today: [The project says it.]
What has to keep running: [The project says it.]
Who operates it: [No operator named yet. Without an operator with agreed hours, the request doesn't open.]
Hours: 4 a week, 12 weeks, as a pair, once it opens.
License: Chosen by the project. We don't know yet.
Funding: Depends on the project. If there is pay, it is written here before starting.
Stage: 0 Description · of five, per RFC-001

Candidate. It becomes a request when the school says what it needs and someone from it will operate it. Sign up for this request

pedido-002

not signed yet open

A system for buying and selling yerba mate and honey that funds a self-managed school

Who is asking: A self-managed school that funds itself by buying and selling yerba mate and honey.
Who brought it: A fessional from the core. Already talked to whoever would operate it, and they are willing to sign the request.
The problem: [The project fills this in, in one sentence: what happens to them today with purchases, sales and the money coming in and out.]
What exists today: [The project fills this in: where they record purchases, sales and debts today.]
What has to keep running: [The project fills this in: the one thing that has to keep running.]
Who operates it: [Role of the operator on the school's side, with their agreed weekly hours.]
Hours: 4 a week, 12 weeks, as a pair.
License: Chosen by the project. We don't know yet.
Funding: Depends on the project. If there is pay, it is written here before starting.
Stage: 1 Discovery · of five, per RFC-001

Opens as soon as the school reads the request and signs it. Sign up for this request

For projects

What it takes

Tell us what you're missing, who will use it and who will look after it once it's done. Writing works, or a two-minute WhatsApp audio: someone turns it into a one-page request and sends it back so you can say "yes, that's it". Nothing goes up without that review. If you know someone in IT who lives nearby, have them bring you: it's the shortest door.

A person replies, with their name, within 72 business hours. For now the contact is the project email: sidepro.org@gmail.com.