The awkward stuff, before you ask.

Many contracts with foreign companies assign the intellectual property of what you make, and some forbid contributing to code under certain licenses. Before you start there is a one-page letter, in Spanish and English, for you to present at your company. It is input, not a safe-conduct; if your company has its own form for outside projects, use it.

We don't know yet. Each project picks it from a short list of open licenses, and it is written in the request before you sign up. The general rule is discussed in public, in RFC-002.

At least 4 a week for 12 weeks, by milestones, not by cadence; you set the ceiling. About 50 useful hours in total. If you can't one week, you say so and nothing happens.

There are two ways in. You bring one: a socio-environmental organization from your city or area, wherever you live, that already exists and already knows what it needs, with someone who will operate it and is willing to sign the one-page request; what's missing is for them to say, not you. Or you sign up for two of the requests already in /jects: you come in as the second on those requests and don't open new ones; if you arrive after session 0, you listen to its recording and sign the agreement before touching any data. Unsigned requests can be chosen now, but they start when the project signs.

Only stage 0, as you see it today from outside: what the organization is, what it does and for whom, where, what gets lost or is hard today, and what you think it needs to run better (the assumptions to validate). Plus your X link and how to reach you. The rest, including your hours, comes up in stage 1.

Ask around your block who keeps the books for the club, the soup kitchen, the market, the cooperative, the library. It is almost always a notebook or a WhatsApp group where things get lost. If none shows up, it's not the time yet; without a project there is no session 0.

Then this isn't for you yet. sidepro is a side project next to a job that pays, not unpaid work. When you have one again, the door is still open. Your employer's name is never asked for or published.

You leave with no penalty. What you delivered stays under an open license with a documented handover. The only thing asked is that you say so and don't vanish without a word.

The project, from the first commit; its account is the canonical one. sidepro keeps a public fork with the history intact, so your work and your name survive if the project deletes its repo. No one's data, screenshots or credentials.

It may be or it may not: it depends on each project, its funds, whether it wants or is able to pay, or whether it gets funding. By default these are spare hours. If there is pay, it is written in the request before starting: for which milestone and in what form, with an invoice or in kind with its value in pesos. No agreement sets a precedent for another. You can say no and the request goes on the same. sidepro doesn't charge, pay or intermediate. Check your contract first.

Six hours in twelve weeks, all online: a short call between the two fessionals to split roles, a two-hour session 0 with the operator (recorded with permission; whoever joins later listens to it), five fifteen-minute check-ins every two weeks, and a one-hour handover. No system sets the dates: in the form you mark your free slots, whoever convenes cross-checks them in /cruzar/ in their browser, storing nothing, and proposes a day and time in the repo's issue, with their name. The stages (description, discovery, paper, real data, solo, handover), the roles and what gets logged where are in RFC-001, which is open for comments.

Mobile apps, AI models, integrations with banks or the tax agency, logins for fifty users, real-time dashboards. Yes to forms, spreadsheets with validation, simple databases and exports; whatever someone from the project can operate and change without you.

If the operator doesn't show up, the request is paused after ten days and renegotiated after thirty; never 'the pair runs it in the meantime'. If someone leaves you hanging, we say so in the postmortem, which is published anyway.

The form stores nothing on any website: when you send it, your email program opens and you send it yourself to the project inbox. A named person reads it, it is not shared with anyone, and it is deleted when you ask, or after 90 days if no request has started with you. The controller is sidepro, a decentralized organization; for access, correction or deletion, write to the project email.

In the project's repo, in text files: one line per step forward in CAMBIOS.md, and the commit that brings it says who, when and what. The main branch is protected and everything comes in by PR, so nobody writes over what they haven't read; mistakes are reverted, not deleted. Each fessional works from their fork, with their name in the history, and takes it with them when they leave. They are files: they get cloned and moved with a git push. How to set it up, step by step, in plantillas/REPO.md.