side·pro

$ git log --oneline jects/

  1. pedido-0012026-10-27in progressstage 4/5 · solo A logistics and sales system for a network of agroecological producers and consumers not signed yet
  2. pedido-0032026-10-26candidatestage 0/5 A management system for a community football school and soup kitchen not talked to yet
  3. pedido-0022026-10-26openstage 1/5 · discovery A system for buying and selling yerba mate and honey that funds a self-managed school not signed yet
every stage closed is a line in CAMBIOS.mdsee all requests →

sidepro

side·pro brings together /fessionals, digital-tech professionals who work remotely, with /jects, requests from small socio-environmental organizations that need new technology to run better.

/jects The projects you can sign up for: one page per request, with who operates it and what has to keep running. /fessionals Who is part of it, what they are on, and what they left running, with the work in plain sight. And the two things it takes to be a fessional.

How to take part

  1. Sign up. Say what you do in IT and your real spare hours, and choose how you come in: you bring a socio-environmental organization from where you live, or you sign up for two of the requests in /jects. If you bring one, you describe in a few lines the organization and the need as you see it, including what you haven't confirmed yet (stage 0). A person replies, with their name.
  2. Discovery and paper. If you brought a project, you meet the organization with a checklist and come back with each assumption confirmed or corrected and the need described in their words; with that, the organization writes and signs its request (stage 1). Then, before writing any code, there is an online meeting with whoever will use the system every day: with the notebook or spreadsheet on screen, we sketch how a record is entered, found and corrected. If the operator doesn't get it, nothing gets coded. It is recorded with permission, and whoever joins later listens to it before touching any data.
  3. Date. In the form you mark your free time slots in the week. Whoever convenes cross-checks them in /cruzar/, storing nothing, and proposes a day and time in the issue of the project's repo, with their name. From there the request runs through its five stages.

The sign-up form is in /fessionals. What happens next, from the request to the postmortem, is five stages, and it is in RFC-001.

The rules are written in public

How a request works, what license the code carries, what happens when someone leaves: each rule is a one-page RFC in the repo, with who objected and how it was settled. Those who come in first will discuss them and change them. That is what being at the start means.

What you won't find here

  • Volunteering.
  • Briefs that change every two weeks.
  • Meetings other than these three: session 0, a fifteen-minute check-in every two weeks, and the handover.
  • Counters. Photos of smiling people. Promises of impact.