Skip to content

Collaboration with EDGI resource maintainers #22

Closed
@patcon

Description

Heyo! I'm with Environmental Data & Governance Initiative (EDGI), the new kids on the archiving block. We have two related working groups building software:

  1. Archiving working group. (aka Archiving WG) Building software like alpha.archivers.space for scraping data from gov sites, facilitating a community pipeline for metadata collection, and keeping those datasets in the hands of civil society (potentially via decentralized file systems).
  2. Website Change Monitoring working group. (aka Web Monitoring WG) For building out our system to monitor diffs in gov domains via a pipeline that vets these changes past the eyes of domain experts and into the hands of journalists.

In an effort to help orient our Archiving WG (1), one of our members (h/t @mhucka!) started a similar effort to your awesome list, but in spreadsheet form. The main difference is that we were aiming for a comprehensive survey, not just the "awesome" stuff. This comprehensive approach ensures the we and collaborators know both what we know about and what we don't.)

Related: edgi-govdata-archiving/overview#145

Inspired by that effort, Web Monitoring WG (2) started another awesome list:
https://github.com/edgi-govdata-archiving/awesome-website-change-monitoring

Questions

  1. Any thoughts on how we could integrate our efforts? If there's mutual interest:
    1. might you be amenable to making the resource explicitly collaborative, instituting clear contribution process like provided by a CONTRIBUTING.md. (We'd be happy to share our CONTRIBUTING.md!)
    2. Is our separate website change monitoring tool resource aligned? Might it be part of a collaboration? Should it remain a separate resource?

Curious to hear your thoughts! Thanks!

cc: @dcwalk

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions