meeting 10 Jan 2023 - OpenDataforWeb3/Resources GitHub Wiki

Agenda:

  • good hackathon awareness
  • hackathon participation - not as strong yet
    • why? -> actually some metrics are more positive then that
  • ongoing hackathon improvements:
    • issue review

      • epowell101 need to do it -> and others of course

    • helping folks gain access to our Github as a member

      • encourage folks to join our Github

      • we could also use Orbit or something else -> or Discord BOT -> hello and have you starred & did you know you could join?

        • could point them to the ReadMe -> and the contributing doc - bullets or paragraph
        • also ask them to give us a star
        • sort of a newsletter but more directed - remind them they can get paid as well
        • hackathon tips & notes - how can we surface this - maybe tweaking the resources readme - to highlight tips & wiki more
    • web site -> encouraging more people to participate - automating the pipeline - and updating into dev -> the workflow is being built and improved - right now for some reason (bugs) adding an issue on a second blog post wasn't work -> add staging for example - we could actually SEE the staging website then -> a meeting this week to broaden the team working on it and supporting it
    • Ocean -> things are generally working - however once we made an edit it seemed to cause an issue on their end -> remember that users can just grab the data directly as well themselves - keep in mind that they won't want to just use the data we provide for them -> they can and should use data they can find!!! -> this ties to our desire of curating a stack that we want -> SHOULD we do a blog on this asap -> what is the right balance between the two - doing analysis - data cleaning & visualization
    • Lego definitions & examples -> an example & office hours & a list of examples is in flight (finally) -> python package -> to a script -> other approach - need this ASAP -> package management - could we use pypi for packaging?
    • responsiveness ftw!
    • other
  • organization work
    • medium term plan
    • Kamu as an example project that is giving feedback on what we could help
    • voting for the hackathon
  • before the end of the hackathon - we can discuss the next hackathon & other plans
    • feels important but not (yet) urgent -> we cannot drop it and yet it tends to get deprioritized for the fire of the day (epowell editorial)