Skip to content
David H. edited this page Jan 23, 2025 · 19 revisions

Welcome to the polis wiki maintained by Civic Tech Toronto Polis group!

About polis

Polis is a tool aim to connect people through the internet and encourage individual efforts that contribute to the overall well-being of our society. This is in direct contrast to the harmful and unproductive nature of some social media platforms.

Useful links:
πŸš€ Polis official website and hosting
πŸ”— Our polis repository on GitHub
🌐 Storybook to accelerate frontend development
πŸ—ƒοΈ Meeting notes of the polis group
✨ BotPolisCodeHelper - Poe an assistant with knowledge of the Polis codebase
πŸ’¬ BotPolisSeedComments - Poe an assistant simulating different souls generating extremely diverse comments on a topic to stimulate human to engage in conversation
πŸ” A demo Polis conversation (QR code) to get a hand on experience with Polis
πŸ“Ή A YouTube demo video about Polis conversation
🐳 The repositories for container images of our branches on Docker Hub

Short cut to wiki

🧭 Tutorials
πŸ“Ή Blog
πŸ‘¨β€πŸ« Blog HOW-TO
πŸ’» Deployment HOW-TO
πŸ‘¨β€πŸ’» Developer getting started
πŸ” Review PR HOW-TO

If you...

About us

We believe that facilitating collective intelligence and fostering mutual understanding within communities is essential for our community. Polis is a good engagement tool for large-scale, open-ended feedback gathering.

Communication

We host in-person meetings every Tuesday at CivicTechTO hacknights . We host hybrid in parallel to the hacknights every Tuesday. .

  • In hacknight around 8pm, we will have:
    • Short introduction of attending members
    • Stand-up meeting
      • Report progresses since last hacknight
      • Teams announce their agenda of the night
      • Request for help or propose to support
    • Teams breakout
    • Ramp-up
      • Teams exchange the summary of the night
      • Teams exchange the action items to be followed up next week

We chat between meetings on the CivicTechTO Slack

Facilitator

In case you are playing our facilitator role this month, here are a run down for your reference:

  • Monday:
    • Ask everyone about what they are doing and see if they need any resources for help on whatever they are doing.
    • Share the updates in slack channel to help each of our member to know what others have been doing.
  • Tuesday:
    • Invite people to propose agenda items for the hacknight meeting.
    • Host the meeting with the flow for your reference.
    • Help participants to write the meeting notes.
  • Wednesday:
    • Leverage AI to generate the summary of meeting notes (prompts you can copy) edit and post to slack channel #polis.
    • Based on the meeting notes, identify action items of each member and follow up on next Monday.
    • Based on the goal, GitHub issues and meeting notes to identify potential action items that has been overlooked by others and post the action items in slack (e.g. Here are some orphan tasks waiting for developer to adopt: ...).

Methodology

Agile development based weekly iterative development.

  • All action items should breakdown into small tasks that can be down within a day.
    • If breakdown cannot be done within the hacknight, breaking down will be the action item.
  • A draft of agenda should be announced before the hacknight in slack channel #polis.
  • A summary of meeting notes of the hacknight should be shared after meeting in slack channel #polis.

Knowledge management

We have knowledge base in HackMD.

We have meeting notes of hacknights in Google Document.

We organize helpful information in the Wiki here for our developer and new members as their reference.

⚠️ We may still miss something important, you can help us to find them and add them as a contributor in documentation!