Repository navigation
Polybazaar
Welcome to the PolyBazaar wiki!
Figma UI/UX mockups, with navigation.
M1 Figma Link
Check the Excalidraw Link for clearer view.
APK: https://github.com/polybazaar-project/polybazaar/actions/runs/43383325715/artifacts/14018011078
Figma UI/UX mockups, with navigation.
M2 Figma Link
Check the Excalidraw Link for clearer view.
Team checklist for reviewing a pull request in PolyBazaar, whether written by a teammate or an AI agent
Read the whole diff and the surrounding code, then review against AGENTS.md and these points. Report each as OK or ISSUE, and do not approve what you cannot review.
- Scope: the PR does one task; unrelated changes are split out.
- Tests: new behavior has tests that assert behavior (not just that code runs), including edge cases and failures; CI is green.
- Architecture: MVVM holds; ViewModels do not import Firebase or repository implementations.
- Offline: the feature still works, or degrades cleanly, without a connection.
- Security: no secrets or
google-services.json; Firestore/Storage rules cover new data. - Clarity: names and commit messages explain the change; no dead code or over-engineering.
- AI acknowledgement: files an agent wrote carry the header note, commits have
Co-Authored-By, and the PR names the agent.
Open a PolyBazaar pull request with the team's conventions, as a draft, with a filled-in description
- Check
git statusand read the full diff againstmain. Stop if unrelated changes are mixed in. - Run
./gradlew ktfmtCheckand./gradlew check. Record what passed and what could not run. - Check that no PR already exists for the branch:
gh pr list --head <branch>. - Open a draft PR with
gh pr create --draft. The title is a Conventional Commit, such asfeat(listings): add item form. Fill in.github/pull_request_template.md. - Never claim a check passed unless it ran. Never force-push or merge.
The structure is: lowercase category prefix (like feature/ or fix/), followed by a short, hyphen-separated description.
Both share the same naming conventions:
lowercase type (like feat or fix), an optional scope, and a short imperative description of the change. (Example: feat(auth): add email login)
For PR Description :
- What : What changed.
- Why : The task or issue this solves (Closes #n).
- Validation : Checks you ran and their result, and any you could not run.
- AI use : Which agent or tool helped and what it did, or "None".
How we collect and use feedback from early users of PolyBazaar.
For now no feedback could be collected, some features still needed wiring, will start collecting in S6 !
- Survey: link, 5–10 min, covers first impressions, ease of use, bugs, and value
- Results: Collected into the Google sheet
- Follow-up: The most relevant issues will become GitHub issues at the end of the sprint
We want to try to use blockchain for payments, which will come later in the developpment. Else we might use Stripe API.
Manage Google Services credit, agent tokens.
Using LLMs to analyse broken item, so the reporting system does not need human review.
Monday 1pm Wednesday 3:30pm
| Sprint | Start Date | SM | PO |
|---|---|---|---|
| 1 | 02.10 | Antoine | Alex |
| 2 | 09.10 | Tarek | Adri |
| 3 | 16.10 | Joshua | Lucas |
| 4 | 30.10 | Jules | Antoine |
| 5 | 06.11 | Alex | Joshua |
| 6 | 13.11 | Lucas | Tarek |
| 7 | 20.11 | Adri | Jules |
| 8 | 27.11 | Tarek | Lucas |
| 9 | 04.12 | Antoine | Adri |
| 10 | 11.12 | Joshua | Alex |