Isegoria Notes

• Wall Feature Updates
  • Initially, only ISE content can be shared. Shares will be disabled unless content is originally from the ISE users
  • 2 Types of shares. Internal (retweet), and external
    • Internal Share - "Retweet"
      • A user can choose to repost a ISE post to their own wall
      • When reposted, the post will show the original poster's username and post content in a post style embed
      • Post will show some indicator to show that it is a repost
    • External shares:
      • Parler
      • Mewi
      • Minds
      • Facebook
      • Twitter
      • Linkedin
      • Copy Embed URL to clipboard
• Ad server to host preroll and banner ads - openx modern equivalent

Meetings

2020-11-7

• MouseBelt will oversee developers of the original application performing modifications to the project

• Team

  • QA - Isegoria has a QA tester (formerly Tmobile) putting in 10h/wk on QA. Timezone: USA?
  • Product - Sam with Isegoria is lead on product guidance/questions. Timezone USA (Eastern)
  • Design - Isegoria has a designer (Conan O'brien's design team) creating all assets/designs. Timezone Eastern?
  • Web Frontend/Backend Development - Developer of the original tool is updating it for all new requirements. Konrad is the point of contact, Timezone is poland
  • PM - MouseBelt
  • Blockchain Development - MouseBelt (starting after web phase completed)

• Commmunication

  • We will create a shared channel between mousebelt.slack.com and isemedia.slack.com to be the main channel of communication

• Timelines

  • Dev timeline for new features - 8 weeks (ending december)
  • Testing - january
  • Launch of web product at the end of the testing phase

• Next Steps

  • Setup shared slack channel (markus to create invite, sam to accept)
  • Kickoff call with dev team - tuesday (adam to create invite)
  • Setup code version control (we recommend github, will discuss in dev kickoff meeting) - galen
  • Setup issue tracking tool (we recommend zenhub, will discuss in dev kickoff meeting) - galen
  • Setup cloud provider for dev/test server - Discuss at meeting, then sam assists galen with next steps
  • MB brings lead PM onto the project
  • Share specs to MB - Sam