wiki-cafe/member-console
1
1
Fork 0
Code Issues 204 Pull Requests Packages Projects 1 Releases Activity

FedWiki and Discourse are built into the console instead of connecting through the published contract #174

New Issue
Open
opened 2026-10-06 18:12:03 +00:00 by cgalo5758 · 1 comment
cgalo5758 commented 2026-10-06 18:12:03 +00:00
Owner
Copy Link
Copy Source

What a person cannot do today

Connect FedWiki or Discourse the way any other application would. FedWiki needs code on both sides, the farm plugin and internal/integrations/fedwiki, which have to agree; Discourse's code lives in the console; and each keeps its own schema in the console's database. A newcomer has no worked example of the contract and no way to test a connector of their own.

What they should be able to do

  • Test a connector with a conformance harness, start one from a quickstart, and use helpers for the parts every connector repeats.
  • Run Discourse through the contract first, as a bridge the project maintains, then FedWiki through its farm plugin. Each moves by shadow migration, with one writer at a time.
  • Read an example application that acquires usage, as a model for the classes the two first-party connectors do not use.
  • Have any application claim, place and release a domain through a names capability, with the domains registry staying in core (#44, and a path for #87).

Why it matters

The contract is only credible if the project's own applications use it. Moving both before launch means a deployment sees connectors it can copy, and the fedwiki and discourse schemas leave the console's database; stripe stays, because payments are not part of the contract (#80).

Where

internal/integrations/fedwiki, internal/integrations/discourse, the farm plugin, the specification repository from #171, a harness and an example application.

Done when

FedWiki and Discourse both run through the contract with no code under internal/integrations; the conformance harness passes for both and for the example application; the fedwiki and discourse schemas are retired; #46 is resolved with them.

Order

Comes after #173; the last of the four, after #171 and #172.

## What a person cannot do today Connect FedWiki or Discourse the way any other application would. FedWiki needs code on both sides, the farm plugin and `internal/integrations/fedwiki`, which have to agree; Discourse's code lives in the console; and each keeps its own schema in the console's database. A newcomer has no worked example of the contract and no way to test a connector of their own. ## What they should be able to do - Test a connector with a conformance harness, start one from a quickstart, and use helpers for the parts every connector repeats. - Run Discourse through the contract first, as a bridge the project maintains, then FedWiki through its farm plugin. Each moves by shadow migration, with one writer at a time. - Read an example application that acquires usage, as a model for the classes the two first-party connectors do not use. - Have any application claim, place and release a domain through a names capability, with the domains registry staying in core (#44, and a path for #87). ## Why it matters The contract is only credible if the project's own applications use it. Moving both before launch means a deployment sees connectors it can copy, and the `fedwiki` and `discourse` schemas leave the console's database; `stripe` stays, because payments are not part of the contract (#80). ## Where `internal/integrations/fedwiki`, `internal/integrations/discourse`, the farm plugin, the specification repository from #171, a harness and an example application. ## Done when FedWiki and Discourse both run through the contract with no code under `internal/integrations`; the conformance harness passes for both and for the example application; the `fedwiki` and `discourse` schemas are retired; #46 is resolved with them. ## Order Comes after #173; the last of the four, after #171 and #172.
cgalo5758 added this to the Public launch milestone 2026-10-06 18:12:03 +00:00
cgalo5758 added the
kind
enhancement
area/fedwikiarea/discoursearea/integrations labels 2026-10-06 18:12:03 +00:00
cgalo5758 commented 2026-10-06 21:26:41 +00:00
Author
Owner
Copy Link
Copy Source

The first candidate for the shared helpers is how FedWiki takes in a lifecycle request today, in internal/integrations/fedwiki/web/requests.go: parsing the instance address, building the request, starting its workflow and answering a repeated request. Only the mapping from a request's answer to what the page shows is free of FedWiki specifics; the rest has to be separated first. The conformance harness is where each operation a connector declares meets its implementation.

The first candidate for the shared helpers is how FedWiki takes in a lifecycle request today, in `internal/integrations/fedwiki/web/requests.go`: parsing the instance address, building the request, starting its workflow and answering a repeated request. Only the mapping from a request's answer to what the page shows is free of FedWiki specifics; the rest has to be separated first. The conformance harness is where each operation a connector declares meets its implementation.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
A barrier for people using assistive technology or a keyboard alone.
 area/billing
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
 area/catalog
Products, prices, plan ladders, purchasability.
 area/discourse
The Discourse integration.
 area/domains
The domains registry, claims, placements, the certificate ask.
 area/entitlements
Entitlement sets, rules, grants, pools, provisioning.
 area/fedwiki
The Federated Wiki integration and farm sync.
 area/identity
Sign-in, sessions, persons, organizations, workspaces, roles.
 area/integrations
The provider registry, outbox and webhooks in general.
 area/licensing
Licenses, the contributor agreement, SPDX headers.
 area/member-ui
Member pages.
 area/meta
The repository itself, its contributing guide, CI, the tracker and the workflow.
 area/operator-ui
Operator pages, forms, lists, the design system.
 area/ops
Deployment, configuration, migrations, workflows, instance settings.
 area/testing
The test stack, screens, lint, walkthroughs.
 duplicate
Closed because another issue already covers it.
 good-first-issue
Small, self-contained, and explained enough to be a first contribution.
 invalid
Closed because it is not a ticket for this repository.
 privacy
Touches what a person's data reveals.
 security
Touches authentication, authorization, secrets or data exposure.
 upstream
Waits on another repository or project before it can move.
 wontfix
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
No labels area/discourse area/fedwiki area/integrations
kind
enhancement
Milestone
No items
No Milestone Public launch
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant Bortseb (Robert Best) cgalo5758 (Christian Galo) renovate-bot (Comrade Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#174