24 January 2023 meeting - OpenDataforWeb3/Resources GitHub Wiki

Agenda:

Hackathon:

  • Metrics:
    • interest
  • Smoothing the contributor experience:

    • pretty well discussed on Discord but still....

    • The first Github page should link to a contribution

    • Updating the contributor wiki with screenshots to explain the fork/PR process

    • Discussion on current user flow to contribution docs

    • Contributing section to the README - fewer steps for the user

    • Curious rabbit: Write up directing people to contributor wiki; also working on website page formatting

    • Sarob: Update the main website page

    • Sarob and Curious rabbit: Work on local dev testing fork - will record for future resource

  • Loom recording for the workflow process

  • Any way to know what people are working on?

  • No set up in the current hackathon but something to consider for next one

  • Could we potentially set up office hours and giving bonuses for those who participate

  • Getting sponsor feedback to better tailor results from participants

  • We will need to schedule a retro once the hackathon is complete

    • What needs improvement?
    • What went well?
  • **Dework **

    • Anything Sarob or others want to discuss here

    • What sort of POC should we do?

    • Organise tasks by specific working groups?

    • Maybe with tags on the issues?

    • There is a sync between github and dework

  • Promotion for the last week:

    • One more epic tweet thread w/ content contestants can use

    • other ideas?

    • Baoki: Reaching out to participants and checking in

    • Office hours from FDD team members this week?

    • Name/role/time availability

      • Baoki: Get list of FDD office hours for later this week
    • Exploratory and Legos bounties

Discussion on Wednesday providing feedback to deck and plan that epowell101 is putting together hopefully gathering thoughts

Let's plan to schedule retro as well as ODC planning for 2023 meeting

  • Set up discussions for proposals on what we should do
  • Build agenda for retro and review meeting