From the institutional-membership discussion in co-op/support#32. Prepared for review — this is a governance document, and §11 says material changes are announced to members and, where appropriate, decided through Loomio, so nothing here should be merged without that step.
§4 — serving others through the co-op
The prohibition on reselling or redistributing access is removed: the bullet now prohibits sharing account credentials and nothing else. §4 ends with the permission stated plainly:
You may use the service to provide a service of your own, as long as your use remains subject to these Terms, along with the acceptable-use and privacy expectations in §4 and §7.
Resale is no longer the thing we prohibit; failing to carry the Terms downstream is. This also settles — without needing a ruling — whether an at-cost hosted service backed by the co-op counts as resale. Wording is @ntnsndr's from #32; solo.ist preferred it to an "except under an institutional agreement" carve-out, and it makes bo's point structurally: serving multiple people is how you are expected to operate, not an exception you request.
Raised and set aside, for the record:@bo proposed keeping the prohibition on reselling while permitting redistribution. This PR takes the broader route deliberately.
§8 — the notice and grace we actually give
Describing current practice, confirmed against the running service today: a member whose contribution stops receives a notice email before anything changes; the grace period is seven days (PAYMENT_GRACE_DAYS), with access continuing; if no contribution arrives, the monthly allowance stops renewing and access pauses, while the account and its data stay in place.
Deliberately not written as automatic removal: the lapse path can decide to deactivate, but acting on it requires a second switch that is currently off. The reminder members already receive promises that they "lose access", not their account — the Terms now say the same thing. #32 item 5 asked for 30 days' notice of model removal "to institutional members"; @ntnsndr asked for that applied to all members instead. I have left that out of this PR rather than decide it here — comments welcome.
Left alone on purpose
The "In plain language" summary has no line about serving others. One short bullet would match the document's voice, but it is not in this diff.
docs/.site-build/ is generated output; I did not hand-edit the built HTML. If that directory is what gets served, it needs a regeneration as part of publishing.
(Inferencebot — the co-op's steward bot. Proposals and member-facing changes like this one go through the GM before they're acted on.)
From the institutional-membership discussion in co-op/support#32. Prepared for review — this is a governance document, and §11 says material changes are announced to members and, where appropriate, decided through Loomio, so **nothing here should be merged without that step**.
### §4 — serving others through the co-op
The prohibition on reselling or redistributing access is **removed**: the bullet now prohibits sharing account credentials and nothing else. §4 ends with the permission stated plainly:
> You may use the service to provide a service of your own, as long as your use remains subject to these Terms, along with the acceptable-use and privacy expectations in §4 and §7.
Resale is no longer the thing we prohibit; failing to carry the Terms downstream is. This also settles — without needing a ruling — whether an at-cost hosted service backed by the co-op counts as resale. Wording is @ntnsndr's from #32; `solo.ist` preferred it to an "except under an institutional agreement" carve-out, and it makes `bo`'s point structurally: serving multiple people is how you are expected to operate, not an exception you request.
**Raised and set aside, for the record:** @bo proposed keeping the prohibition on *reselling* while permitting redistribution. This PR takes the broader route deliberately.
### §8 — the notice and grace we actually give
Describing current practice, confirmed against the running service today: a member whose contribution stops receives a notice email before anything changes; the grace period is **seven days** (`PAYMENT_GRACE_DAYS`), with access continuing; if no contribution arrives, the monthly allowance stops renewing and access pauses, while the account and its data stay in place.
Deliberately **not** written as automatic removal: the lapse path can decide to deactivate, but acting on it requires a second switch that is currently off. The reminder members already receive promises that they "lose access", not their account — the Terms now say the same thing. #32 item 5 asked for 30 days' notice of model removal "to institutional members"; @ntnsndr asked for that applied to **all** members instead. I have left that out of this PR rather than decide it here — comments welcome.
### Left alone on purpose
- The "In plain language" summary has no line about serving others. One short bullet would match the document's voice, but it is not in this diff.
- `docs/.site-build/` is generated output; I did not hand-edit the built HTML. If that directory is what gets served, it needs a regeneration as part of publishing.
*(Inferencebot — the co-op's steward bot. Proposals and member-facing changes like this one go through the GM before they're acted on.)*
Two edits, both from the institutional-membership discussion (co-op/support#32).
**§4.** The prohibition on reselling or redistributing access is removed — the
bullet now prohibits sharing account credentials and nothing else — and §4 ends
with the permission stated plainly: you may provide a service of your own, so
long as your use remains subject to these Terms and you carry the acceptable-use
and privacy expectations to the people you serve. Resale stops being the thing we
prohibit; failing to carry the Terms downstream is the thing we prohibit. That
also settles the question raised in #32 of whether charging at-cost rates counts
as resale: it no longer has to.
**§8.** Termination now describes what the system does rather than what we might
wish it did: we write to you before anything changes, you get a seven-day grace
period with access continuing, and if no contribution arrives the monthly
allowance stops renewing and access pauses while the account and data stay in
place. Removal per the Charter is separate and unchanged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
From the institutional-membership discussion in co-op/support#32. Prepared for review — this is a governance document, and §11 says material changes are announced to members and, where appropriate, decided through Loomio, so nothing here should be merged without that step.
§4 — serving others through the co-op
The prohibition on reselling or redistributing access is removed: the bullet now prohibits sharing account credentials and nothing else. §4 ends with the permission stated plainly:
Resale is no longer the thing we prohibit; failing to carry the Terms downstream is. This also settles — without needing a ruling — whether an at-cost hosted service backed by the co-op counts as resale. Wording is @ntnsndr's from #32;
solo.istpreferred it to an "except under an institutional agreement" carve-out, and it makesbo's point structurally: serving multiple people is how you are expected to operate, not an exception you request.Raised and set aside, for the record: @bo proposed keeping the prohibition on reselling while permitting redistribution. This PR takes the broader route deliberately.
§8 — the notice and grace we actually give
Describing current practice, confirmed against the running service today: a member whose contribution stops receives a notice email before anything changes; the grace period is seven days (
PAYMENT_GRACE_DAYS), with access continuing; if no contribution arrives, the monthly allowance stops renewing and access pauses, while the account and its data stay in place.Deliberately not written as automatic removal: the lapse path can decide to deactivate, but acting on it requires a second switch that is currently off. The reminder members already receive promises that they "lose access", not their account — the Terms now say the same thing. #32 item 5 asked for 30 days' notice of model removal "to institutional members"; @ntnsndr asked for that applied to all members instead. I have left that out of this PR rather than decide it here — comments welcome.
Left alone on purpose
docs/.site-build/is generated output; I did not hand-edit the built HTML. If that directory is what gets served, it needs a regeneration as part of publishing.(Inferencebot — the co-op's steward bot. Proposals and member-facing changes like this one go through the GM before they're acted on.)
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.