You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we could lure other FOSS projects into collaborating on this with us on this :)
One way to do this might be to write some boilerplate copy for how this would fit into a README (perhaps copying that into the research README), and then open issues (or even pull requests?) in the various projects, asking how they'd feel about linking to it.
We'd also probably want to immediately give that maintainer access to work on that research repo, so that they don't suffer inconvenience beyond what they'd have maintaining their own. We might need a new GitHub team for this, so if you go that route, you might need to collaborate with @patcon@dcwalk@b5 or @lizbarryor others on this page to ensure they're added to an appropriate team :)
That awesome list seems to have been started on June 16. Was it literally the result of a discussion during IIPC? If so, were you there by any chance, and do you know more background?
Yeah it was @mhucka, tho to my understanding there was a previous list hosted on the IIPC site. I think the context was just that there is a lack of current resources to let new people to web archiving, and also people in specific areas, to understand the breadth of web archiving tools.
Hey -- I feel like you are getting this ball rolling @patcon :)
It seems to me like maybe this could be closed when you feel ready? As it is sort of moving out of a first-timer task?
@mhucka has gone to great efforts to create an comparison resource:
https://github.com/archivers-space/research/tree/master/web_archiving
It would be great if we could lure other FOSS projects into collaborating on this with us on this :)
One way to do this might be to write some boilerplate copy for how this would fit into a README (perhaps copying that into the research README), and then open issues (or even pull requests?) in the various projects, asking how they'd feel about linking to it.
We'd also probably want to immediately give that maintainer access to work on that research repo, so that they don't suffer inconvenience beyond what they'd have maintaining their own. We might need a new GitHub team for this, so if you go that route, you might need to collaborate with @patcon @dcwalk @b5 or @lizbarry or others on this page to ensure they're added to an appropriate team :)
Something like this, but please improve lingo!
datatogether/sentry#6
The text was updated successfully, but these errors were encountered: