Hi Tom! Sorry, this was buried in the IRC log but everyone who would
like to comment on the Google Doc is welcome to send me their Gmail
address so I can give them permission to comment.
Of course, it's also fine to discuss right here on this mailing list.
That's what it's for. :)
You're absolutely right that an issue tracker per repo is an excellent
way capture notes and comments. Unlike git itself, issue tracking is
not standardized. Every issue tracker works a little differently, and
it makes sense for dataset owners to chose their favorite. Or they can
have a mailing list or receive personal email or whatever.
I used GitHub as a point of comparison throughout the document because
it's well known.
Oh, I just read this paper and it's good and on topic for this thread:
Git can facilitate greater reproducibility and increased transparency
in science - http://bitss.org/2014/03/12/git-reproducibility-transparency/
The author even talks about using git for datasets.
p.s. Some more chatter today about datasets as git repos:
> You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com
> To post to this group, send email to dataverse...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/874n31sr6g.fsf%40pobox.com
> For more options, visit https://groups.google.com/d/optout