I would like to post an repository on github that includes data and analysis code in R. The analysis and data forms part of a journal article submission. I'm happy for people to view the code and data prior to publication (in particular, it might be an easy way for reviewers to examine the code). However, I do not want anyone publishing analyses of the data prior to acceptance and publication of the journal article. After publication, I want to encourage people to re-analyse, re-use, re-publish (e.g., with a GPL licence with an encouragement to attribute).
Obviously, I could just keep the data and analysis code a secret until after publication, but I thought an appropriately worded licence might be more appropriate. I thought about just writing in plain English that the work is copyrighted at this time, and will be converted to GPL at a later date following publication.
- Is there a standard way of licensing data and code so that people cannot republish the data and code until the corresponding publication has been published?
- Or is it better just to keep the data and code secret until after publication?
UPDATE: I suppose there is a legal perspective to this, but I know that academia has its own norms and conventions regarding attribution and respecting the wishes of authors. So I'd be particularly interested in answers framed in that context. I.e., My broader aim is to be the first to publish my own research, generally get attribution, but also allow others to build on that work. So I'd be interested also in what is considered good practice when you are in the situation of wanting to share data and code while an article is being peer reviewed, but not wanting to lose your right of first publication.