1. Core team changes

    1. mutual expectations and commitments

      Initial motivations to join

      • Meet and connect with people who are (or becoming) experts in web3
      • Peer group that learns and grows together, works on different projects but on a similar stage
      • Active interactions and support like provide advice on finance on/off chain, join hackathons, build products together

      Current status

      • Disappointment with lack of member activity
      • Advanced members miss quality discussions and mutual support
      • Active members feel vulnerable by having to ask their questions to more than 60 people

      Need for change in community management and structure

      • Decision to separate into
        • one general channel for every member who’s intro got accepted
        • all other current channels will become private channels for active members who agreed on living up to the requirements mentioned below.

    b. define requirements for a core team member

    Active member (Pretzle activists) requirements

    c. make a proposal of new core team members

    Approach to implement change

  2. Proposal for short-term vision: we get our hands dirty as core team and join as many hackathon as possibly. Sooner or later we’ll come up with a project that we would like to do long-term

    1. Also what Vici said: We literally should just build something. As long as we can pitch it, we’ll be able to get funding for it.
  3. Clearly define the focus of the weekly call.

    1. what’s the target group

      Only the active members will have access. There will be no weekly call for standard members anymore

    2. who organizes it and what would we like to get out of it The active members organize it and share their latest learnings, experiences, etc. in a trusted environment