Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / traitecoevo/data_versioning issues and pull requests

#36 - reproducibility update

Pull Request - State: open - Opened by smwindecker about 5 years ago - 1 comment

#34 - note on discussion

Issue - State: closed - Opened by mwpennell almost 7 years ago

#33 - Dataset or database

Issue - State: closed - Opened by dfalster almost 7 years ago - 1 comment

#32 - Update reademe for datastorr

Issue - State: closed - Opened by dfalster almost 7 years ago

#31 - Update readme for this repo

Issue - State: closed - Opened by dfalster almost 7 years ago

#30 - Table 4 is currently not cited

Issue - State: closed - Opened by wcornwell about 7 years ago - 1 comment

#29 - missing references

Issue - State: closed - Opened by mwpennell about 7 years ago - 1 comment

#28 - Reorder authors

Pull Request - State: closed - Opened by richfitz about 7 years ago

#27 - future directions section at the end of discussion?

Issue - State: closed - Opened by wcornwell about 7 years ago

#26 - authorship reorder

Issue - State: closed - Opened by richfitz about 7 years ago - 3 comments

#25 - Discussion of the discussion...

Issue - State: closed - Opened by wcornwell about 7 years ago

#24 - make sure description of git is technically correct

Issue - State: closed - Opened by wcornwell about 7 years ago

#23 - Distinguish between data archiving for a paper, versus "living" dataset

Issue - State: closed - Opened by wcornwell about 7 years ago - 2 comments

#22 - Re-write introduction with the goal to frame data versioning better

Issue - State: closed - Opened by wcornwell about 7 years ago - 1 comment

#21 - Re-write abstract to focus on data versioning

Issue - State: closed - Opened by wcornwell about 7 years ago - 2 comments

#20 - Comments from RGF

Pull Request - State: closed - Opened by richfitz about 7 years ago

#19 - incorporate comments from dan noble

Issue - State: closed - Opened by wcornwell about 7 years ago - 2 comments

#18 - The table of examples needs more examples

Issue - State: closed - Opened by dfalster about 7 years ago

#17 - Datastorr needs a icon or hex sticker

Issue - State: closed - Opened by dfalster about 7 years ago - 1 comment

#16 - Paragraph on DOIs

Issue - State: closed - Opened by wcornwell about 7 years ago

#15 - Paragraph on allowing for one or more data contributers

Issue - State: closed - Opened by wcornwell about 7 years ago

#14 - Minor things needed for submission

Issue - State: closed - Opened by dfalster about 7 years ago - 1 comment

#13 - a better title

Issue - State: closed - Opened by wcornwell about 7 years ago - 1 comment

#12 - concept needs a proper name

Issue - State: closed - Opened by mwpennell over 7 years ago - 3 comments

#11 - Figure: illustrates technology stack

Issue - State: closed - Opened by dfalster over 7 years ago - 7 comments

#10 - Figure: illustrates semantic versioning

Issue - State: closed - Opened by dfalster over 7 years ago - 14 comments

#9 - Licenses

Issue - State: closed - Opened by dfalster over 7 years ago - 1 comment

#8 - Possible journals

Issue - State: closed - Opened by dfalster over 7 years ago - 2 comments

#7 - datastorr tutorial

Issue - State: closed - Opened by wcornwell over 7 years ago - 1 comment

#6 - Create table matching users to tools

Issue - State: closed - Opened by wcornwell over 7 years ago - 1 comment

#5 - Prior work

Issue - State: closed - Opened by richfitz over 9 years ago - 3 comments

#4 - Forks

Issue - State: closed - Opened by richfitz over 9 years ago - 1 comment

#3 - Minimal set of information required

Issue - State: closed - Opened by richfitz over 9 years ago - 1 comment

#2 - need to write a nice short statement defining the problem

Issue - State: closed - Opened by wcornwell over 9 years ago

#1 - Will this be a paper or a blog post?

Issue - State: closed - Opened by wcornwell over 9 years ago - 4 comments